Amazon Brand Story image sizes and requirements (2026)

Your Brand Story is four modules wide, and every one of them has its own image spec — with a second guide quoting different numbers for the hero. Get them wrong and you are re-exporting banners at midnight.

I have built enough Brand Stories to know where the rework comes from. It is almost never the storytelling. It is the specs: a carousel designed at the wrong pixel size, copy baked into an image instead of entered in a field, or a beautiful desktop banner that falls apart on a phone. The canvas is small — up to 4 modules — so there is nowhere to hide a mistake.

This piece is the spec reference I wish existed when I built my first Brand Story: every module’s image size, every copy limit, the guide conflicts shown honestly, and the mobile crop handled before it handles you. Pair it with my narrative patterns from the Brand Story examples post, and you have both halves of a strong build.

What are the official Brand Story module sizes?

“Official” needs a caveat first. The builder displays the exact pixel dimensions for each module as you add it — that is the source of truth at upload time. Everything below is cross-checked from independent seller guides (Titan Network, sipranshecommgrowth, brandsbro, marissaputtagio — all checked October 2026). Use these as planning sizes and confirm each one in the builder before you finalise exports.

Here is the full module table:

Module	Image spec (guide-reported)	Copy limits (guide-reported)
Brand carousel background	1464 × 625 px (desktop); JPG or PNG; under 2 MB	No text fields — image only
Brand logo	315 × 145 px minimum; transparent background preferred	No text fields
Brand Focus Image	362 × 453 px	Headline 30 chars max; body 135 chars max
Brand Logo & Description	315 × 145 px	Body 450 chars max; no separate header field
Brand ASIN & Store Showcase	166 × 182 px product images	Header 30 chars max; no body text
Brand Q&A	No image	750 chars max combined (questions + answers)

Two things jump out. The module library is small — five module types, up to 4 per Brand Story — so this is a tighter canvas than A+ Content, and there is nowhere for a bad crop to hide. And the copy limits are strict: 30 characters is five or six words for a headline; 135 is about two short sentences.

For comparison, the A+ module set is far larger and the sizes are different — I keep a separate A+ image sizes reference if you are building both at once.

Why do two guides disagree on the carousel background size?

This is the conflict I mentioned in the intro, and I want to show it honestly rather than pick a winner silently.

Titan Network’s Brand Story guide — one of the most thorough walkthroughs available — cites 1464 × 625 px for the carousel background, JPG or PNG, under 2 MB. Meanwhile, marissaputtagio’s guide cites 1646 × 625 px for desktop and 463 × 625 px for mobile as the two carousel figures.

When I build a Brand Story, I design at the commonly cited 1464 × 625 canvas, keep every important element inside a generous center safe zone, and verify the exact requirement in the builder the moment I add the carousel module. If the builder shows a different number, I re-export at that number — which is why I keep layered source files, never flattened JPEGs, until the build is approved.

There is a practical lesson hiding in the disagreement: the carousel is the only Brand Story asset that renders at two very different widths (desktop and mobile), so a few pixels of width disagreement between guides is survivable as long as your composition is center-safe. The guides that bother to list separate mobile figures are doing you a favour — they are telling you the crop is real.

How do the Brand Story copy limits actually work?

The standard rhythm across modules is headline 30 characters, body 135 characters per card. Short. Deliberately short.

The exceptions are where sellers trip up:

• Logo & Description gives you 450 characters of body but no header field — treat it as the brand’s mission statement, not a feature list.
• Q&A allows 750 characters total for questions and answers combined. Two or three tight Q&A pairs will eat most of it.
• ASIN & Store Showcase has a 30-character header and no body text — the product images do the talking.

The rule underpinning all of it: every word goes into Amazon’s copy fields, never into the image file. Baked-in text is one of the most common rejection triggers in the guides I cross-checked. If your designer sends you a banner with the tagline burned into the pixels, send it back.

What does the Brand Story carousel look like on mobile?

Here is where most rework comes from. The carousel renders full-width on desktop, but on mobile the sides get cropped and the left portion carries the focus. A design that reads beautifully at 1464 px wide can lose its headline, product, or logo on a phone.

My rule: design for the center safe zone, decorate the edges. Anything mission-critical — brand name, core claim, hero product — sits centre or centre-left. The outer thirds get texture, blur, extended scenery: things that can be cropped without losing meaning.

The diagram below shows how I think about it. The solid outer frame is the full desktop view; the dashed red window on the left is what mobile keeps; the dashed center zone is where your key content must live to survive both.

Before you submit anything, preview the mobile render in the builder. It takes thirty seconds and it has saved more of my builds than any other single habit.

Anchor-Out: my Brand Story build sequence

Because the canvas is small (four modules, tight copy limits), I build Brand Stories in a fixed order. I call it Anchor-Out: start with the anchor module and work outward, so every later decision inherits the first one’s composition.

Step 1 — Anchor: the carousel background. Design the 1464 × 625 banner first, center-safe. This sets your palette, mood, and voice for everything below it — compose for the desktop full view and the mobile crop simultaneously.

Step 2 — Logo & Description. Place your 315 × 145 logo (transparent PNG, per the guides) and write the 450-character mission paragraph — the brand’s handshake, not a spec sheet.

Step 3 — Focus image. Build the 362 × 453 focus card: one strong image, a 30-character headline, a 135-character body. Give the whole card to your single strongest proof point — origin, ingredient, process, or founder.

Step 4 — ASIN & Store Showcase. Lay out your 166 × 182 product tiles under a 30-character header. No body copy, so the images must be clean and consistent — same backgrounds, lighting, and scale.

Step 5 — Q&A. Spend your 750 combined characters on the two or three questions buyers actually ask — returns, materials, compatibility, care. Answer the objection that costs you the sale.

Then submit and wait out the approval window — 3–7 business days is the guide-reported typical, not a guarantee.

Annotated example: a full module map for a fictional brand

To make the module stack concrete, here is a complete module map I mocked up for MOSSLOOM, a fictional natural soy candle brand. Every callout uses the guide-reported specs from the table above. This is illustrative only — not client work, and not a real brand.

Walk through it top to bottom and notice the Anchor-Out logic: the carousel sets the earthy, calm mood; the logo and description deliver the mission paragraph; the focus card owns a single proof point; the showcase grid is visually uniform; the Q&A spends its characters on the two questions a candle buyer actually asks — safety and care. Nothing in the images carries text that belongs in a field.

If you are deciding whether Brand Story or a full Storefront is the right investment for your brand, my Brand Story vs Storefront breakdown walks through the trade-offs.

Which file rules will get a Brand Story rejected?

Approval is not automatic, and the file rules are where rejections cluster. The guides agree on this set:

Rule (guide-reported)	Get it right	Get it wrong
Format	JPG or PNG only	Anything else bounces
File size	Under 2 MB per image	Oversized uploads fail or compress badly
Colour mode	RGB	CMYK or other modes cause colour shifts
Text placement	All copy in Amazon’s fields	Text baked into images = rejection risk
Logo background	Transparent preferred	Busy backgrounds behind the logo look amateur

Two eligibility notes the guides agree on: Brand Story is a Brand Registry benefit, like A+ Content — you need an enrolled brand to build one. And one approved Brand Story publishes catalog-wide: a single build covers every ASIN under your brand, unlike A+ Content, which is assigned per ASIN. One build, whole catalog — the highest-leverage brand asset per hour of design time on Amazon.

Mistakes I see constantly

Designing one canvas and assuming it renders the same everywhere. The carousel is two renders — desktop wide, mobile cropped. Check both.

Baking the tagline into the banner image. I say it twice because it kills that many submissions. Fields, not pixels.

Writing the 450-character description like a feature list. You get one paragraph and no header. Tell the brand story — origin, belief, promise — in that paragraph. Features belong in A+ modules.

Exporting flattened JPEGs and deleting the source files. When the builder shows a different dimension than the guide you planned from — and it happens — you need layered sources to re-export in minutes, not a rebuild from scratch.

Skipping the mobile preview. Thirty seconds in the builder. Every time. No exceptions.

Your pre-publish checklist

• Every image is JPG or PNG, RGB, under 2 MB
• Carousel designed center-safe; mobile crop checked in the builder preview
• Logo is 315 × 145 minimum, transparent background
• All copy entered in Amazon’s fields — nothing baked into images
• Headlines within 30 characters, bodies within 135, Q&A within 750 combined
• Each module’s exact pixel size verified in the builder at upload time
• Four or fewer modules; every module earns its place
• Brand Registry enrollment confirmed before submitting
• Layered source files archived for fast re-exports

A 4-week action plan

Week 1 — Spec and copy. Confirm every module size in the A+ Content Manager builder for your marketplace. Draft all copy to the character limits — headline, bodies, Q&A — in a document first, counting characters as you go.

Week 2 — Design. Build the carousel anchor first (center-safe), then logo, focus card, and showcase tiles in the Anchor-Out sequence. Export at the builder-verified sizes.

Week 3 — QA and submit. Mobile preview in the builder. Run the pre-publish checklist above line by line. Submit and note the date — guides report 3–7 business days for approval.

Week 4 — Propagate and link. Once approved, confirm the story renders across your catalog’s ASINs. Then connect it to the rest of your brand presence — the examples in my Brand Story examples post show how strong brands keep narrative consistent between Brand Story, A+, and their Storefront.

FAQ

What is the Brand Story carousel background size?

The commonly cited figure is 1464 × 625 px (JPG or PNG, under 2 MB), per Titan Network’s guide. One other guide cites 1646 × 625 for desktop and 463 × 625 for mobile. Verify the exact requirement in Seller Central’s builder when you add the module — the builder is the authoritative source.

How many modules can a Brand Story have?

Up to 4 modules, chosen from the module library: carousel background, logo & description, focus image, ASIN & store showcase, and Q&A.

Can I put text inside my Brand Story images?

Do not. All copy must be entered in Amazon’s text fields. Text baked into images is a known rejection risk.

How long does Brand Story approval take?

Seller guides report typically 3–7 business days. Treat that as typical, not guaranteed — complex builds can take longer.

Does one Brand Story cover all my products?

Yes. A single approved Brand Story publishes catalog-wide across all ASINs under your brand, unlike A+ Content, which you assign per ASIN.

What is the difference between Brand Story and A+ Content?

Brand Story is the brand-level narrative that shows across your catalog; A+ is product-level enhanced content assigned per ASIN. I compare Brand Story against the Storefront option in detail here, and keep a separate A+ sizes reference.

Brand Story is the smallest canvas Amazon gives brand owners — and that is exactly why the specs matter. Get the sizes, the copy limits, and the mobile crop right, and one build works across your whole catalog for years. Get them wrong, and you are re-exporting banners at midnight.

If you would rather hand the whole thing to someone who has built these before, get in touch — I design Brand Stories, A+ Content, and listing images for Amazon sellers every week. My services page shows the full picture.