# Chrome Web Store promo assets for feature eligibility

> Ship the small promo image early and add the marquee asset when the product is ready, because discovery surfaces in the store depend on those listing assets being present and approved.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/chrome-web-store-promo-assets-for-feature-eligibility/
- Source: [developer.chrome.com](https://developer.chrome.com/docs/webstore/images)
- GrowthDex source hub: [Chrome for Developers: Supplying Images](/sources/chrome-for-developers-supplying-images-developer-chrome-com/)
- Last checked: 2026-05-30
- Rarity: rare
- Budget: low
- Channels: Marketplaces, Brand, Discoverability
- Stages: browser extensions, promotional assets, store featuring, brand system


## Why this can grow

A lot of teams leave promotional images until after launch because the extension technically works without them. Chrome's image rules make that shortsighted. The small promo image is required, and the marquee image is what makes featured placement possible. Those assets are not decoration. They control whether the store can show the extension in its higher-visibility surfaces. If the page is good enough to be featured but the assets are missing, the team quietly caps distribution before the ranking algorithm even gets a say.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where chrome web store promo assets for feature eligibility can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Marketplaces and Brand channel.
3. Use the evidence from developer.chrome.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Chrome's image guide says every item needs a 440x280 small promotional image and cannot be featured in marquee unless the listing also includes a marquee promotional image.

## Adjacent tactics in the same lane

- [Chrome Web Store image set shows one workflow](/growth-ideas/chrome-web-store-image-set-shows-one-workflow/) - same source, 2 shared channels
- [Chrome Web Store five-screenshot install story](/growth-ideas/chrome-web-store-five-screenshot-install-story/) - same source, 1 shared channel, 1 shared stage
- [GitHub Marketplace feature card preview before brand refresh](/growth-ideas/github-marketplace-feature-card-preview-before-brand-refresh/) - 2 shared channels, 1 shared stage
- [Edge Add-ons duplicate assets across locales after primary proof](/growth-ideas/edge-add-ons-duplicate-assets-across-locales-after-primary-proof/) - 2 shared channels, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The extension listing should earn the install before the permission prompt](/blog/the-extension-listing-should-earn-the-install-before-the-permission-prompt/) - marketplaces, SEO, brand trust

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.