Launch Platform Screenshot Sizes: What Is Public and What Is Not
Most launch platforms we checked do not publish screenshot sizes on a page an automated check can read; any requirement sits in the upload form. Of the sites we checked on 13 November 2026, only BetaList states its gallery guidance publicly: roughly 4:3, for example 800 x 600, with a square icon of 512 pixels or more. For the rest, prepare one master set and confirm the size on the platform’s own upload screen.
Do launch platforms publish their image sizes?
Rarely, and that is the main finding. App stores print exact pixel specs in public documentation; the launch boards we checked keep any image requirements inside the submission form. We opened each site’s public pages on 13 November 2026 and recorded what they say. The table is deliberately blunt about gaps, because an invented number on this page would cost you a rejected upload.
| Platform | What its public pages say | Size confirmed? |
|---|---|---|
| BetaList | Gallery images of roughly 4:3, such as 800 x 600, high resolution, horizontal for most products and portrait fine for mobile apps; up to five screenshots; icon square, ideally 512 px or larger, on a solid background | Yes, as guidance |
| DevHunt | Its FAQ says to submit a name, website, description, logo and screenshots | No size stated |
| Uneed, TinyLaunch, Smol Launch | Their public home and pricing pages give no image sizes; we did not open the submission forms | No |
| Fazier, Microlaunch, OpenHunts, Launching Next | No image sizes on the public pages we read | No |
| Hacker News (Show HN) | A text submission with a title and a link; no images | Not applicable |
| Product Hunt, Peerlist, Indie Hackers | Our automated requests were refused, so we read nothing | Could not read |
| Post Your Build Ideas | Form fields are name, URL, tagline, description, up to three categories, pricing model and email, plus an optional square logo of up to 1 MB and up to four images of up to 3 MB each, as PNG, JPEG or WebP | Yes, from our own form |
Read BetaList’s own wording on its submission guide and its agent submission page rather than relying on our summary. The guide’s reasons are useful beyond BetaList: it warns against extremely tall or extremely wide images, tiny low-resolution screenshots, a banner used as an icon and the full product name baked into the icon.
What master set covers most boards?
When nothing is published, build once at a generous size and crop down. The stores we read give a pattern: Chrome wants 1280 x 800 (16:10), Figma suggests 1920 x 1080 (16:9), Shopify asks for 1600 x 900 (16:9), Google Play wants 16:9 or 9:16 images of at least 1080 pixels on the short side to qualify for recommendations, and Apple’s Mac sizes are all 16:10. BetaList’s 4:3 is the outlier. The set below is our own recommendation, not any platform’s requirement.
| Asset | Suggested master | Crops down to |
|---|---|---|
| Square icon | 1024 x 1024 px PNG on a solid colour | 512, 256, 128 and favicon sizes |
| Wide screenshot | 2880 x 1800 px (16:10) of the main screen | 1280 x 800, 1440 x 900 and, with a crop, 16:9 |
| 16:9 cover | 1920 x 1080 px with the product name large | 1600 x 900 and most banner slots |
| 4:3 gallery shot | 1600 x 1200 px of a second screen | 800 x 600 |
| Mobile portrait | 1080 x 1920 px, only if the product is mobile | Store and gallery portrait slots |
| Short clip or GIF | A 10 to 20 second capture of the one core action | Platforms that take video or a YouTube link |
Which screens should the images show?
Sizes are the easy half. A visitor who lands on a listing decides in seconds, so the first image has to answer “what is this and what does it do”. Choose the single screen where the product does its job on real-looking content, not an empty state. A budgeting app shows a month with transactions in it; a design tool shows a finished layout beside the panel that made it. Then add the screens that answer the next question: how do I start, and what do I get at the end.
- Main screen with believable data, cropped to the part that matters.
- The step before it, showing how a person gets there.
- The output: the exported file, the report, the message sent.
- A settings or integration screen, only if buyers ask about it.
- One image that shows the product at a smaller viewport, if it is responsive.
Avoid mock-ups that show features you have not built. Store guidance in the pages we read is firm on this: Google Play wants screenshots of the actual in-app experience, and Shopify says images should primarily show the real interface. The same discipline helps on boards, where commenters can try the product in seconds. The how to take product screenshots answer goes through capture settings.
How do you confirm a size without wasting an upload?
- Sign in to the platform when you are ready to submit, and open the submission form without finishing it.
- Read the hint text beside each image field; most show the size or ratio they want.
- If there is none, upload your largest master. Many platforms resize on upload and show the crop in a preview, and a form that rejects a file usually names the limit.
- Check the preview in a narrow window as well, since that shows how a phone visitor will see it.
- Save the sizes you learn in a note beside your master folder, so the next launch starts from facts.
This board asks for images only if you want to add them, so the work above matters most for the stores and boards that require them. When you are ready, launch your product free first, because it needs nothing but a link and a description, and choose any images before you press Publish, since the gallery is final once live; then use the screens for the places that ask for them. The free launch platforms comparison says which ones those are, the logo and icon specs cover the square asset, and the Open Graph image specs cover the card people see when your link is shared. If the product has no pictures to show yet, the photo and video ideas list is a place to look.
Frequently asked questions
What size should launch platform screenshots be?
It depends on the platform, and most do not publish a size publicly. BetaList’s public guide asks for roughly 4:3 gallery images such as 800 x 600 and a square icon of 512 pixels or more. For other boards, confirm the size on the upload form and keep larger masters to crop from.
Can I use the same screenshots on every launch platform?
Mostly yes, if you build masters at a large size and crop. Differences are in ratio, so keep 16:10, 16:9 and 4:3 versions of your main screen, with the subject centred. Check each platform’s preview before you publish, because a crop can remove a caption.
Do I need a video for a launch listing?
Not on every board. Some take a YouTube link or short video, and some take images only. A ten to twenty second clip of the one core action is useful where allowed, since it shows the product working. Read the form’s hint text first, and never let video delay the launch.
Does this site need screenshots to launch?
Not here. The launch form takes a name, URL, tagline, description, up to three categories, a pricing model and an email, and the images are optional: a square logo and up to four screenshots. You can publish right after opening the emailed link, then prepare images for the stores and boards that require them.
Written by Post your build ideas with AI assistance and edited for this site. Where a page names another product, the facts came from that product’s own pages on the date shown above; terms change, so check them before you rely on them. About the publisher.