Amazon DSP Ad Specs: The 2026 Performance Guide

A DSP launch gets approved in media, the audience build is clean, the budget is committed, and then creative stalls the whole thing. The culprit is usually not strategy. It's a wrong dimension, an oversized file, a blurry mobile asset, or a unit your designer didn't know was mandatory.

That's why Amazon DSP ad specs matter more than commonly realized. On a platform where entry costs are high and setup takes real planning, technical compliance isn't a production detail. It's part of performance management. If the ad loads poorly, gets rejected, or misses key placements, the campaign starts behind.

I treat specs as a profitability control. The best DSP programs don't separate creative ops from media outcomes. They connect them. File weight affects load behavior. Format coverage affects inventory access. Mobile rendering affects click quality. If you're spending at the level DSP requires, those details belong in the same conversation as ROAS, organic rank, and long-term scale.

Why Amazon DSP Ad Specs Are a Performance Lever

Most Amazon DSP mistakes happen before the first impression serves. A brand has the budget, the audience logic, and the reporting plan, but creative arrives in the wrong sizes or with assets too heavy for approval. The launch date slips. The flight starts late. Momentum gets lost.

That's avoidable.

Amazon DSP sits inside a broader programmatic environment, so creative rules aren't random. They exist because ads need to render across Amazon-owned properties and third-party inventory with predictable quality. If your team needs a useful refresher on the mechanics behind that, this guide to understanding programmatic ad ecosystem is worth reading before you build your next DSP workflow.

What technical compliance actually changes

Spec compliance affects three things that leaders care about:

• Launch speed: Approved assets get into market faster. Rejected assets create wasted cycles between design, media, and trafficking.
• Inventory access: Missing required sizes means your campaign won't cover all the placements it could.
• Ad experience: Smaller, properly built files load more cleanly, which supports viewability and user experience.

Those aren't creative department concerns only. They shape efficiency in the account.

A lot of brands still treat DSP as an extension of Sponsored Ads. It isn't. The setup, access model, and creative requirements are stricter. If you want a practical overview of how DSP fits into the wider Amazon media stack, Amazon DSP advertising is a useful starting point.

Practical rule: If a DSP campaign has premium targeting and weak asset prep, the targeting won't save it.

Specs are the first gate. Performance comes after.

The Core Five Display Ad Sizes You Must Have

If your team builds only one checklist for Amazon DSP ad specs, make it this one. Amazon DSP requires display ads in exactly five specific sizes to launch a campaign: 300x250, 728x90, 160x600, 300x600, and 320x50 for mobile; failing to prepare these exact dimensions results in incomplete campaign coverage and missed inventory opportunities across desktop and mobile environments according to NovaData's Amazon DSP guide.

What each size does in practice

300x250
This is the workhorse. If a team tells me they want to simplify production, this is the last unit I'd cut. It's flexible, widely used, and usually the first asset I want approved.

728x90
This gives you desktop header-style coverage. It's not as visually forgiving as a larger rectangle, so weak layouts break fast here. Keep copy tight and branding obvious.

160x600
A narrow vertical unit exposes weak hierarchy. Product imagery needs to read instantly, and your CTA can't fight for space. Good sidebar coverage depends on disciplined design.

300x600
This is a larger vertical canvas and often gives designers more room to make the message breathe. It's useful when your product needs a little more visual storytelling without moving into custom formats.

320x50
This is the mobile necessity. Teams that skip it usually overestimate how far desktop-first creative will carry them.

The common mistake

Brands often arrive with three sizes and assume that's enough because those assets look “close enough” to standard display inventory. DSP doesn't reward close enough. If the exact units aren't prepared, coverage suffers.

Use this as the minimum viable package before you debate more advanced formats:

• Mandatory desktop coverage: 300x250, 728x90, 160x600, 300x600
• Mandatory mobile coverage: 320x50
• Production discipline: Design each unit intentionally. Don't just auto-resize one master file and hope it holds up.

The fastest way to waste a good media plan is to send it into market with partial creative coverage.

Standard Display Ads A Detailed Breakdown

Most display campaigns in DSP still rely on standard image assets. That makes the basics essential. Amazon DSP requires static display creatives to be delivered in standard image formats (JPG, PNG, or GIF) using RGB color mode at 72 DPI, with strict file size limits of 40KB for most standard web sizes, though HTML5 and billboard formats like 970×250 allow up to 200KB initial load, as outlined in Stellarising's creative guidelines overview.

The performance reason is straightforward. Lighter files load faster. Faster-loading ads are less likely to create friction in the page experience. In DSP, that matters because your ad doesn't live in one controlled environment. It has to behave well across Amazon pages and third-party placements.

The standard spec sheet that actually matters

Dimension (px)	Format	Max File Size (Initial)	Animation Length
300x250	JPG, PNG, GIF	40KB	Keep animation within Amazon's accepted limits
728x90	JPG, PNG, GIF	40KB	Keep animation within Amazon's accepted limits
160x600	JPG, PNG, GIF	40KB	Keep animation within Amazon's accepted limits
300x600	JPG, PNG, GIF	40KB	Keep animation within Amazon's accepted limits
320x50	JPG, PNG, GIF	40KB	Keep animation within Amazon's accepted limits
970x250	HTML5 or billboard-compatible creative	200KB initial load	Keep animation within Amazon's accepted limits

The practical takeaway is simple. If your designer hands off beautiful assets that blow past the file threshold, they aren't finished.

Why the 300x250 gets priority

The same source notes that the 300×250 medium rectangle is the essential foundation for any DSP campaign, with the highest inventory availability across Amazon search results, product pages, and third-party digital inventory. The 728×90 leaderboard should be prioritized alongside it for desktop coverage.

That matches what works in execution. If timelines are tight, start by getting those core assets right before expanding into richer or more custom units.

The mobile detail and search results exception

One detail teams miss all the time is the mobile-specific custom unit. The Mobile Detail & Search Results format must be produced at 828×250 pixels at 2x resolution to display correctly at 414×125 pixels on high-density smartphones, based on the same Stellarising reference.

That matters because “technically accepted” and “visually sharp” aren't the same thing. A mobile asset that renders soft or cramped won't help CTR even if it clears review.

Here's the standard I give creative teams:

• Build in RGB: CMYK exports create unnecessary problems.
• Respect 72 DPI: Don't overbuild files for web placements.
• Control file weight early: Compress during design review, not after final approval.
• Design by unit, not by template: A strong 300x250 rarely shrinks cleanly into a 320x50 without reworking hierarchy.

If your team needs stronger creative process discipline around these units, this resource on best practices for display ads is a practical companion.

HTML5 and Rich Media Creative Specifications

HTML5 can lift the quality of a DSP campaign when the idea needs movement or interaction. It can also create the longest approval chain in the whole build if the files are messy, bloated, or trafficked without technical QA.

The first thing to understand is initial load versus polite load. Initial load is what the placement needs upfront to begin rendering. That has to stay tight because it affects page performance immediately. Rich media can then call additional assets after the first stage, which is why polite loading exists in the first place.

What to package in the file

A clean HTML5 handoff usually includes:

• Primary HTML file: One clear entry file. No confusion about which document should launch.
• Referenced assets: Images, scripts, fonts if allowed, and any supporting files organized logically.
• Backup image: A static fallback should always be ready in case the interactive unit can't serve as intended.
• Click tracking setup: The click destination needs to be implemented in the required way so the ad can be validated and measured properly.

This isn't glamorous work, but poor packaging creates expensive delays. When rich media gets rejected, it usually isn't because the concept was bad. It's because the unit was assembled like a prototype instead of a deliverable.

Where rich media helps and where it hurts

HTML5 works best when motion clarifies the product story. Think feature reveals, product transitions, or simple interactivity that adds context without making the user work. It fails when teams use it to cram in more messaging, more frames, and more visual noise.

Rich media should improve comprehension, not show off production effort.

A few rules keep HTML5 useful:

1. Start with the static concept. If the ad doesn't work as a still, animation won't rescue it.
2. Keep the first render clean. Don't make the user wait for the “real” ad.
3. Use backup images intentionally. They shouldn't be an afterthought. They should sell the same message.
4. QA every click path. Broken click behavior is one of the easiest ways to lose time in review.

The common failure pattern

Brands often commission premium HTML5 creative before validating whether the message itself is strong. That's backwards. Good DSP operators prove the offer and the visual hierarchy first, then add complexity only when it serves a purpose.

For most brands, static display wins on efficiency until there's a clear reason to upgrade. Rich media can outperform simple units in the right context, but only when the build is disciplined and the motion is doing real work.

Amazon DSP Video Ad Specs for OTT and In-Stream

Video in Amazon DSP serves different jobs depending on where it runs. OTT and Streaming TV inventory are built for lean-back viewing and broader reach. In-stream placements usually operate closer to standard digital video environments. If you treat them as the same thing, you end up with the wrong edit, the wrong pacing, or both.

This visual gives the high-level comparison first.

OTT versus in-stream in practical terms

OTT creative usually needs to feel native to a television viewing context. That means stronger visual storytelling, cleaner branding, and less dependence on small text. In-stream can tolerate more direct-response structure, but it still has to land quickly.

A simple comparison helps:

Placement type	Best creative posture	What breaks performance
OTT and Streaming TV	Brand-forward, visually clear, easy to understand from a distance	Tiny text, cluttered overlays, overly tactical layouts
In-stream video	Tighter message, faster product communication, clearer CTA framing	Slow intros, weak branding, footage that needs sound to make sense

Creative choices that matter more than teams expect

For OTT, edit for the room, not the desktop preview. If the brand mark is too small on a laptop screen, it's almost always too small in a living-room environment. For in-stream, assume the user may be distracted, partially attentive, or moving fast. Your first frames need to communicate the category and product without explanation.

Later in planning, many teams also need to align the video choice with the rest of the Amazon stack. If you're comparing DSP video with marketplace-native streaming options, how to advertise on Prime Video is a useful reference.

Here's a walkthrough that helps frame the format discussion from a media perspective:

What I look for before approving video to traffic

I use a practical review before upload:

• Visual clarity: Can someone understand the product without audio?
• Brand recognition: Is the brand obvious early enough?
• Screen-fit logic: Does this edit belong on a TV screen, a web player, or both?
• CTA realism: Is the action implied by the creative appropriate for the placement?

A video can be beautifully produced and still be wrong for DSP if it was cut for another channel.

That's the recurring mistake. Brands repurpose social edits, retailer videos, or CTV spots without adapting them to the actual placement logic. Strong DSP video starts with the screen, the context, and the audience state.

Mobile-Specific and Custom Creative Formats

Many teams understand that mobile matters. Fewer teams build mobile DSP assets as if mobile is the primary screen. That gap shows up fast in creative quality.

The clearest example is Amazon's mobile detail and search results format. The asset has to be produced at 828×250 pixels at 2x resolution so it displays correctly at 414×125 pixels on high-density smartphones, as noted earlier in the article from the referenced creative guidelines. When brands miss this, the ad often looks soft, cramped, or amateur once live.

Why 2x production matters

Modern phone screens expose weak asset prep immediately. If a mobile unit was exported only for the displayed dimensions instead of the required production dimensions, text edges soften and product details lose definition. On a small screen, that kills confidence fast.

The fix is simple, but it needs to happen upstream:

• Design at production resolution: Don't upscale at export.
• Reduce copy aggressively: Mobile units don't forgive long headlines.
• Use one visual priority: Product, offer, or benefit. Pick one first read.
• Test on an actual device: Desktop previews hide a lot of mobile problems.

Where custom formats make sense

Custom creative formats can do real work when the media objective justifies them. Homepage takeovers, billboard-style units, and event-driven placements can help for tentpole launches, seasonal pushes, or major retail moments when broad visibility matters.

But custom doesn't automatically mean better. It means more expensive to build, more sensitive to review, and more likely to underperform if the message isn't tight.

I usually pressure-test custom requests with three questions:

1. Does this format solve a distribution problem that standard units can't?
2. Is the product launch important enough to justify the extra production overhead?
3. Does the brand have a message simple enough to deserve a premium canvas?

If the answer is no, standard units usually win on efficiency.

What works on mobile

The best mobile DSP creative behaves like good packaging on a crowded shelf. It identifies itself fast, communicates one reason to care, and doesn't force the viewer to decode the layout.

That sounds obvious, but a lot of mobile DSP inventory gets treated like a downsized desktop ad. It shouldn't. Mobile needs its own hierarchy, its own spacing, and often its own copy decisions.

Policy Compliance and Common Rejection Reasons

Specs get the files through the technical gate. Policy gets them through review. Brands that ignore this burn time, miss launch windows, and create friction between media and creative teams for no reason.

The painful part is that most rejections are predictable. They come from the same categories again and again: unclear text, broken links, low-quality assets, unsupported claims, and animation that pushes past what the platform allows.

The rejection patterns that cost teams the most time

Here's the short list I'd check before every submission:

• Unreadable text: If the headline or CTA gets tiny in the final unit, expect trouble. This gets worse on narrow and mobile formats.
• Incorrect click-through setup: A creative can look perfect and still fail because the destination link is wrong or not functioning as intended.
• Claims that overreach: Superlatives, implied guarantees, and vague “best” language create risk fast if they aren't clearly supportable.
• Weak asset quality: Compression artifacts, stretched logos, and blurry product renders signal poor execution immediately.
• Animation issues: Motion that runs too long, distracts, or feels excessive invites review problems and weakens the ad anyway.

A better do and don't list

Don't	Do
Shrink desktop copy until it “fits” mobile	Rebuild the mobile hierarchy from scratch
Assume the final URL works because it worked in another campaign	Test every click path before submission
Use hype language to force attention	Use clear product value and straightforward benefit language
Export one master image for all sizes	QA each unit at final dimensions
Add motion because the format allows it	Use motion only when it improves message clarity

Policy compliance isn't admin work. It protects launch timing and media efficiency.

What good teams do differently

Strong teams review creative in the same order the platform will. First technical integrity. Then readability. Then destination behavior. Then claim risk. That sequence catches the majority of avoidable issues before Amazon ever sees the files.

One more thing matters here. Brand leaders often push for “stronger” copy late in the process. That's where policy trouble starts. The more aggressive the language becomes, the more likely the ad drifts into unsupported territory.

The safer path is usually the better one for performance too. Clear, credible claims build trust faster than inflated ones.

From Specs to Scale Strategic Recommendations

Amazon DSP isn't a casual channel. Campaigns require a substantial minimum budget, typically exceeding $35,000 to $50,000, and that generally puts DSP in reach for brands generating roughly $1–2M+ in annual Amazon revenue with proven profitability, as summarized by Veuno's Amazon ad specs guide for 2026. That same source notes that access requires contacting Amazon Advertising directly rather than launching from a self-service portal.

That budget reality changes how you should think about creative. On lower-commitment channels, weak asset prep wastes some spend and some time. On DSP, weak asset prep can compromise a meaningful investment before optimization even starts.

The strategic takeaway for brand leaders

The right way to evaluate Amazon DSP ad specs is not as a design checklist. It's as an operational filter for scale.

If your brand is ready for DSP, these recommendations hold up:

• Fund creative production like media infrastructure: Required sizes, mobile variants, and QA time belong in planning from the start.
• Prioritize compliance before experimentation: Testing only works when the assets consistently clear review.
• Map creative to business stage: Standard units for efficient coverage, custom formats only where the launch stakes justify them.
• Tie DSP back to organic growth: Better creative improves click quality and conversion efficiency, which supports the broader flywheel across paid and organic visibility.

That last point matters most. PPC shouldn't be judged only as an isolated spend line. In a mature Amazon program, it acts as a lever for organic growth, margin protection, and sustainable scale.

When to push further

For teams comparing DSP with other display options inside Amazon's ecosystem, this perspective on mastering Amazon DSP and Sponsored Display is useful because it frames the channel choice around strategy rather than ad format alone.

My recommendation is simple. Don't enter DSP because the audience targeting sounds impressive. Enter when your business can support the investment and your creative operation is strong enough to protect it.

A brand that respects Amazon DSP ad specs launches faster, accesses more inventory, avoids costly rejection loops, and gives its media team better odds of turning spend into profitable, durable growth.

---

If your brand is ready to turn Amazon DSP into a lever for profitability, organic lift, and long-term category growth, Headline Marketing Agency helps consumer brands build and manage full-funnel Amazon media with the rigor DSP demands. From Sponsored Ads to DSP strategy, creative testing, and performance analytics, Headline brings the execution discipline needed to scale without wasting budget.