A Chrome Web Store listing is the screenshot row
Chrome listings are a row of UI stills at store sizes; Qwen holds the browser chrome and the button labels.
Extension listings are a row of UI stills, not iOS App Store frames and not a cinematic demo. Qwen holds the browser chrome and the button labels.
A Chrome Web Store listing that ships is five (or fewer) stills of this popup, this options page, this toolbar button — cropped full-bleed to the sizes Google named. It is not a 6.9-inch iPhone frame. It is not an eight-second Veo walkthrough of a cousin browser. The store reads screenshots. Do not generate a trailer and hope it counts as one.
The listing is a screenshot row
Chrome’s image spec is the brief. You must provide at least one screenshot, and the store prefers the maximum of five. Each screenshot is square-cornered, no padding, full bleed, at 1280×800 or 640×400. That is a 16:10 still, not an iPhone 9:16 marketing frame and not a 16:9 YouTube thumb.
The App Store screenshot post already owns Apple’s canvas: one to ten slots, device-class pixel sizes, up to three previews, one 1024×1024 icon. Do not reuse that playbook here. Chrome does not want a captioned iPhone bezel. It wants a row of browser UI.
The underlying screen has to be representative of the extension you ship. A generated cousin toolbar with a different menu is a listing of a product you do not have. Capture the real popup. If you generate window chrome around that capture, the button strings are the product. Misspelled “Add to Chrome” is a failed still. A cinematic demo is a later file. Google will display images.
Qwen holds the chrome
Qwen Image 3 Text to Image is the still row for readable UI: 2K ceiling, 4 credits, text rendering in Chinese and English. 1280×800 is closer to 16:10 than to 16:9 — generate at 16:9 or 4:3 and crop to the store size. Do not ship a 9:16 phone frame into a 1280×800 slot and call the letterboxing “browser chrome.”
Prompt the window, the tab title you actually use, the button labels you actually ship. Stop before a talking founder. Qwen is a still model. audio is unset. There is no hiss, no VO, no “install now” spoken into the pixels.
Generate an image from text is the agent door: you describe the frame, the agent asks style, aspect, and count, then picks a catalog image row (or the one you name). Cost is priced per model, shown before you confirm. Name Qwen when the job is chrome and labels. Do not let the agent pick a cinematic video family because the prompt said “demo.”
If the still is a marketing treatment over a real capture, keep the capture as the UI. Inventing a settings page the extension does not have is a store problem, not a model problem.
Seedream is the dense tile, not a trailer
Seedream 5.0 Pro is ByteDance’s flagship text-to-image row: 7 credits, 2K quality listed, typography, multilingual text in 14 languages, dense layouts. Use it when the frame is a packed promo tile — small promotional image, a feature grid — and the type still has to hold.
Chrome also asks for a small promotional tile at 440×280. That is a dense, tiny still. Seedream is the better default for a packed layout. Qwen is the better default for browser chrome and button labels. Neither is a video model.
Do not route Veo at the listing because “video converts.” Veo 3.1 is native audio, official 4K tier, 4 / 6 / 8 second clips. That is a scene. A promotional video, if you add one, is a different asset. This page is the screenshot row.
Text to image is the studio door when you have not named the agent. Pick Qwen or Seedream after you name the frame: chrome versus packed tile.
This is not an App Store frame
SaaS founders already have a product-marketing page. Digital product sellers own downloads and galleries. This listing is not those pages rewritten. A Chrome extension is a browser UI still at 1280×800 or 640×400.
Do not stretch an iPhone App Store frame into 1280×800, letterbox a 9:16 demo, or replace the five stills with one cinematic take. Crop real UI to full bleed. Generate chrome only when the labels are the strings you ship.
FAQ
Can I use the same frames I made for the iOS App Store?
No. Apple’s slots are device-class iPhone and iPad sizes; Chrome’s screenshots are 1280×800 or 640×400, full bleed, no padding. The App Store post is a different canvas. Rebuild the row.
Why Qwen instead of Seedream for every slot?
Qwen is 4 credits, 2K, strong on browser chrome and button labels. Seedream 5 Pro is 7 credits, dense layouts and multilingual type. Chrome frames go to Qwen. Packed promo tiles go to Seedream. Neither job is a video generate.
Does the agent pick the model if I just say “Chrome listing”?
Generate an image from text will ask aspect and style, then pick a row unless you name one. Name Qwen for chrome. Name Seedream for a packed tile. Do not accept a video model for a screenshot slot.
Can a cinematic extension demo replace the screenshot row?
Not on the listing. The store displays stills. A trailer is a different asset. Ship five (or fewer) representative UI stills at the named sizes. Generate type that holds. Leave Veo off this row.