Brand Kit for Amazon Sellers: Storefront Banner and A+ Content Sizing

An Amazon listing lives inside someone else's design system. A seller can't build a custom homepage or decide where a logo sits on the page. What they do control is a small, fixed set of image slots: a Store logo, a Store hero image, and a handful of A+ Content modules under the product description. Get those sized wrong and Amazon either rejects the upload outright or renders it stretched and blurry next to competitors who got it right.

None of this requires a design department. It requires a few correctly sized files, built once from a master logo and a master hero image, and reused every time Amazon adds a product or a module type. This is a rundown of what those slots are, roughly how big they need to be, and the file rules that trip sellers up more often than the pixel counts do.

The short answer

• Store logo: a square file, with Amazon's Store Builder currently asking for something in the neighborhood of 400x400 pixels
• Store hero image: a wide banner at the top of the Store page, sized closer to a landscape ratio than a square
• A+ Content modules: sized per module, from small square images in grid and comparison modules up to wider images in banner-style header modules
• Format: JPEG or PNG, RGB color, no CMYK files carried over from a print job
• Content rules: no pricing, no "% off," no time-limited claims, no seller contact information inside the image itself

Amazon Store Builder and A+ Content Manager both show the current recommended and minimum dimensions for each slot at upload time. Those numbers move more often than a typical marketplace's, so use this as a planning guide and confirm the live figure before a final export.

What actually needs sizing, in priority order

Product photography carries the most weight and deserves its own separate process. This post focuses on the three assets that are specifically about brand presentation: the logo, the Store hero, and A+ Content.

The Store logo is the one non-negotiable square

Every Amazon Store requires a logo before it can go live, and the same file also shows up in the "Visit the Store" module that Amazon adds to product listings under a registered brand. It's small and square, built to hold up at icon size.

Amazon's Store Builder currently asks for a square image around 400x400 pixels. Build the master file larger, something like 1000x1000 pixels or more, and let Amazon downscale it on upload, so there's something to work with if the requirement changes rather than a file already sized to the minimum.

A few things matter more here than the exact pixel count:

• The logo needs a clean edge or a transparent background that reads correctly on Amazon's white and light-gray interface, not a logo designed against a dark or colored backdrop.
• Small text inside the mark will not survive the sizes this logo actually appears at, closer to a search-result thumbnail than a webpage header.
• The same square crop used here should be the one already built for a favicon or a social profile picture, not a new crop assembled just for Amazon. If that square variant doesn't exist yet, the social media logo sizing guide covers building it once and reusing it everywhere.

The Store hero image sets the tone

The hero image sits at the top of the Store homepage, above the product tiles. It's the first wide, photographic thing a visitor sees after clicking through from a product listing or an ad. It rarely drives a sale by itself; the product tiles below it do that work.

This slot is landscape, noticeably wider than it is tall, built for a banner position rather than a square icon. Store Builder shows the current recommended width and aspect ratio directly in the tile editor, so check that figure at build time rather than relying on a number from an older guide.

Keep the subject, and any wordmark or text that appears, away from the edges. Store Builder previews render differently on desktop and mobile, and a hero image with text pinned near the border tends to get clipped on at least one of those views. A simpler photograph with a centered subject survives that shuffling better than a busy design.

A+ Content modules are sized per module

A+ Content sits below the bullet points and product description on a listing page for brand-registered sellers. It's made of modules Amazon provides, a company logo strip, single-image and image-with-text layouts, a four-image grid, a comparison chart, and a wider banner-style header, and each module type calls for its own image shape.

That variation is the part sellers underestimate. An image sized for one module will not drop cleanly into a different module without cropping, and Amazon's A+ Content Manager will flag or auto-crop an image that doesn't match the module's expected ratio.

Treat the table as a planning reference, then pull the exact current pixel dimensions from A+ Content Manager for each module before building it. Amazon has changed individual module specs over time without renaming the module, which is how sellers end up working from a guide that's quietly out of date.

Two content rules matter as much as sizing here. Amazon's A+ Content guidelines prohibit pricing, promotional language like "% off" or "limited time," shipping claims, and seller contact information inside the image itself, and violations get modules rejected during review rather than caught after publishing. Keep that copy in the module's text fields, which Amazon can review and update independently of the image.

File format, color, and the mistakes that get content rejected

Amazon accepts JPEG and PNG for these assets. Files built for print, especially anything exported in CMYK color mode from a design tool defaulting to print settings, will render with shifted, often duller colors on Amazon's RGB-based interface. Export everything in RGB from the start.

The rejections and awkward renders that come up most often:

• A square logo stretched into a rectangular slot, or vice versa, because the source file wasn't actually square to begin with
• A file saved in CMYK that looks correct on a designer's screen and off everywhere else
• Text small enough to read in the source file but illegible once Amazon renders it at the module's actual display size
• A hero or header image with a subject or headline positioned near the edge, which then gets clipped differently on mobile
• Reusing a product photo with visible pricing, a sale sticker, or a badge baked into the image, which A+ Content guidelines treat as a policy violation regardless of how the rest of the module looks

Most of these come from treating Amazon's slots as an afterthought, resizing an existing marketing asset at the last minute instead of building a file meant for the slot from the start.

Build the set once, then just export

The practical path is one master logo file and one master hero photograph, high resolution and color-corrected, with enough surrounding space that a square crop, a wide crop, and a module-sized crop can all come from the same source. When Amazon adjusts a module's recommended size, that means re-exporting from the master file rather than rebuilding it from scratch.

That same master logo is worth keeping consistent with whatever else the brand uses elsewhere. If the brand doesn't have a clear sense yet of what belongs in that base set beyond the Amazon-specific files, the brand kit overview covers what a minimal kit needs and what can wait. Sellers running a shop on more than one marketplace can compare notes against the Etsy brand kit guide; the specific dimensions differ, but the underlying approach, one master file with sized variants built from it, doesn't change platform to platform.

Brandize can generate the logo and produce the square and wide crop variants a seller needs for Amazon's Store and A+ slots, cutting each re-export down to a couple of clicks instead of a fresh design pass.