Prepare listing assets by size
Turn existing screenshots, logos, and hero graphics into common Chrome Web Store dimensions: 128 x 128, 440 x 280, 1280 x 800, and 1400 x 560.
Turn product screenshots, logos, or campaign artwork into Chrome Web Store listing assets. Preview extension icons, small promo tiles, store screenshots, and marquee images before export.
Check each asset before export so the final listing stays sharp, centered, and review-ready.
Upload an image to preview the selected asset size.
Related platform sizes
Upload image
Upload an image first, then download the selected asset size.
Prepare Chrome Web Store listing assets: extension icons (128 x 128), small promo tiles (440 x 280), screenshots (1280 x 800), and marquee images (1400 x 560). Upload one image, preview each size, check framing and padding, and export assets for the developer dashboard.
Turn existing screenshots, logos, and hero graphics into common Chrome Web Store dimensions: 128 x 128, 440 x 280, 1280 x 800, and 1400 x 560.
Common Chrome Web Store asset problems include the wrong screenshot ratio, promo text too close to the edge, and icons that lose clarity when reduced. Previewing the target canvas before export helps catch crop, padding, and sharpness issues earlier.
If your screenshots include unreleased features, staging interfaces, or internal product details, local processing is a better fit. Resize, padding, crop, and export all run in the browser, so the source image does not need to be uploaded.
Chrome Web Store images appear in different contexts. Icons help recognition, screenshots explain functionality, and promo or marquee artwork supports discovery and merchandising. Getting the size right makes the listing look steadier across search, detail, and promotional surfaces.
The 128 x 128 icon is the baseline identity asset for an extension. It appears across store and extension-related surfaces, so it needs to stay recognizable at small sizes.
Open referenceThe 440 x 280 promo tile is a compact space for the extension's main value. A clear subject, logo, and short message usually work better than dense layout.
Open referenceThe 1280 x 800 screenshot shows the interface and feature outcome before installation. It should avoid stretching, blur, and cropped product details.
Open referenceThe 1400 x 560 marquee image supports wider promotional layouts and fuller brand presentation. Even when not immediately needed, preparing it keeps the asset package more complete.
Open referenceCommon questions about Chrome Web Store image sizes, upload issues, screenshot ratios, and export formats.
A common Chrome Web Store asset set includes a 128 x 128 extension icon, a 440 x 280 small promo tile, 1280 x 800 store screenshots, and a 1400 x 560 marquee image. Screenshots may also use 640 x 400, but 1280 x 800 is better when you need to show interface detail. Always confirm current requirements in the developer dashboard and official docs before final submission.
A practical way to check is: 1. Confirm the exact pixel size first, such as 128 x 128, 440 x 280, or 1280 x 800. 2. Check whether the source aspect ratio is too different from the target, which often causes stretched UI or awkward cropping. 3. Review the preview and make sure the framing, margins, title text, and logo still look clear. 4. Export only after that, so you are not troubleshooting size errors, soft text, or edge issues inside the dashboard. This is usually faster than trial and error after upload.
PNG is usually safer for UI screenshots, text, icons, and sharp graphic edges. JPG can work for more photographic promo artwork. Extension icons should follow the official PNG requirement. Whether WebP is suitable depends on the current dashboard acceptance rules and the content of your asset.
The official image specification page clearly documents required dimensions, icon format, and screenshot rules, but it does not list a single universal per-image size cap in the same place. If the developer dashboard shows a hard upload limit, you should follow the dashboard prompt. In practice, the best approach is to keep assets visually sharp while avoiding unnecessarily large files, which makes uploads smoother and helps listing pages load faster for users.
No. The resize and export process runs locally inside your browser. Your source images, extension screenshots, and promotional graphics are processed on the client side and are not sent to our server.
After preparing Chrome Web Store assets, you can compress, convert, or create other platform sizes.