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.
Why this can grow a startup
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.
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.
Source-reported evidence
Source: Chrome for Developers: Supplying Images · Browse Chrome for Developers: Supplying Images tactics
Chrome requires a 440x280 small promo image and says an item cannot be featured in marquee without a marquee promotional image.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
Source discovered: May 30, 2026
When to use it
Use this when Marketplaces, Brand, Discoverability is relevant to browser extensions, promotional assets, store featuring and you can run a bounded test with a low budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Marketplaces and Brand, using evidence from Chrome for Developers: Supplying Images as context—not as a promised result.
- Record a baseline for: Target users who complete the tactic’s intended next action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.
SOURCE HUB
More tactics from Chrome for Developers: Supplying Images
Explore related GrowthDex examples and evidence connected to Chrome for Developers: Supplying Images.
Open Chrome for Developers: Supplying Images source hub