Product launch page screenshots: which images and demos to prepare

Last updated: 9 November 2026

Prepare five to seven visuals for your product launch page: a clear first screenshot of the result your product produces, two or three screenshots of the key workflow, one short demo clip or GIF, and a thumbnail or logo that stays legible when small. Good product launch page screenshots answer "what is this and does it work?" in the few seconds a visitor gives your listing.

This article covers what to capture, in what order, and how to check it before you publish. If you're still planning the wider launch, our guide to launching a startup product covers the bigger picture. The visuals are one part of it.

Which visuals does a launch page actually need?

A launch page needs a thumbnail, a lead screenshot, two to four supporting screenshots, and optionally one short demo. Anything beyond that tends to repeat itself. Each image should answer a different question a skeptical visitor has.

Visual	Question it answers	Required?
Logo / thumbnail	"Is this the thing I clicked?"	Yes
Lead screenshot (the result)	"What do I get?"	Yes
Workflow screenshots (2–3)	"How does it work?"	Yes
Short demo clip or GIF	"Does it really work?"	Strongly recommended
Proof screenshot (real data, integration, output)	"Is this real and used?"	If you have it
Pricing or plan image	"What will it cost me?"	Optional

Platform requirements differ, so check the submission form you're using. As one reference point, a 2026 Product Hunt checklist from LaunchList says Product Hunt recommends gallery images of 1270 by 760 pixels, that a gallery appears once it has two images, and that video links must be YouTube. It also notes the logo works best as a square, recommended at 240x240. Treat those as one platform's guidance, not a universal rule, and use the dimensions shown in whichever form you're filling out.

What should the first screenshot show?

The first screenshot should show the outcome your product creates, not your empty dashboard or login screen. Visitors judge a listing from the first image and the tagline together, so the image should prove the tagline.

Examples of a strong lead image by product type:

• Analytics tool: a finished dashboard with realistic numbers and one clearly highlighted insight.
• Developer tool: a terminal or editor showing the command and the useful output, cropped tightly.
• Design or content tool: the finished artifact, such as a generated layout, with the tool's interface only as a frame.
• Booking or finance app: the confirmation or summary screen where the user's problem is visibly solved.
• AI product: a real prompt and a real, unedited output, so it doesn't look staged.

Add a short caption on the image, ideally under ten words, that states the benefit: "Weekly revenue report in one click". Match its wording to your product tagline so the two reinforce each other rather than describe different products.

Which supporting screenshots convince people?

Supporting screenshots should walk through the product in the order a new user experiences it: set up, main action, result. Two to four is usually enough, and each should show one idea.

A simple sequence that works

• Step one, the input. Show the moment the user starts: connecting a source, pasting a URL, picking a template.
• Step two, the core action. The feature people will use most, with the interface cropped so text is readable at thumbnail size.
• Step three, the payoff. A report, export, notification or shared result.
• Optional, the differentiator. The one screen competitors don't have: a specific integration, a comparison view, a privacy setting.

Tips that improve almost every screenshot

• Use realistic data. "Test User" and "Lorem ipsum" signal an unfinished product. Fill in plausible names, figures and content. Don't use real customer data without permission.
• Crop to what matters. A full 1440-pixel browser window shrunk into a small gallery slot makes text unreadable. Zoom into the relevant area.
• Annotate sparingly. One arrow or highlight per image is enough.
• Keep style consistent. Same background, same frame, same font for captions across the set.
• Hide clutter. Close browser tabs, bookmarks bars, notification badges and personal email addresses before capturing.

Do you need a demo video or GIF?

A short demo is worth making if your product involves motion, steps or waiting, because a still image can't show speed or flow. For simple tools with a clear result, a strong screenshot can do the job and a demo is optional.

Aim for 15 to 45 seconds, and show one task from start to finish. Start with the problem on screen in the first three seconds rather than a logo animation. Most visitors will watch muted, so use on-screen captions instead of relying on narration.

Format	Best for	Watch out for
Static screenshot	Dashboards, results, pricing	Can't show speed or flow
Animated GIF	One quick interaction (5–10 s)	Large file sizes, no sound
Short screen recording	A full task from start to finish	Needs trimming, captions
Narrated walkthrough	Complex or technical products	Long and often skipped
Mockup in device frame	Mobile apps, to show context	Can hide detail if too small

Whatever the format, check how your launch platform handles embedded video and whether it accepts uploads or only links. If it isn't stated on the form, assume you need a hosted link and a still image as a fallback.

How do you prepare visuals for a product nobody knows yet?

When you have no audience, no reviews and no users, your images carry the credibility. Make them do three jobs: show the real product (not a concept render), show it working, and show what makes it specific.

If you're pre-revenue, don't fake proof. Avoid made-up testimonials, invented user counts and logos of companies that don't use you. What you can honestly show instead:

• the real product with real, sample content you created
• a before-and-after of a task done with and without the product
• the founder's own use case, labelled as such
• a roadmap or changelog screenshot, if you ship often

For more on the mindset, see our launch note on launching when nobody knows you.

How do you test your images before publishing?

Test by viewing every image at the smallest size a visitor will see it, on a phone, and asking someone unfamiliar with the product to describe it from the images alone. If they can't, the images need work.

Run this pre-publish check:

• Squint test: shrink each image to thumbnail size. Can you still tell what it shows?
• Five-second test: show the first image and tagline to someone for five seconds, then ask what the product does.
• Phone test: open the listing on a phone. Is any text unreadable?
• Dark-mode and light-mode test: if your background is white, check it doesn't vanish against the page.
• Accuracy test: does every screen match the live product today? Outdated UI in screenshots is a common source of support questions.
• Privacy test: no real emails, API keys, tokens or customer names visible.
• File check: compress images so the page loads quickly, and name files descriptively (for example, weekly-report-dashboard.png) rather than Screenshot 2026-11-09.png.
• Alt text: write a plain description for each image, for accessibility and for anyone whose images fail to load.

Do this a few days before launch, so there's time to fix things. Our product launch checklist puts this step in the context of everything else to do before, during and after launch day.

On Launch Orbit, you get a permanent product page and a tile on the live launch canvas, so your images stay visible after launch day, not just for one day. You can submit your product here when your visuals are ready.

Frequently asked questions

How many screenshots should a product launch page have?

Three to five screenshots plus a thumbnail is a sensible target. That's enough for the result, the workflow and one differentiator without repeating yourself. Some platforms, such as Product Hunt, need at least two images for a gallery to show, according to LaunchList's 2026 checklist.

What size should launch page screenshots be?

It depends on the platform, so use the dimensions given on the submission form. Product Hunt, for example, is reported to recommend 1270 by 760 pixels for gallery images. Whatever the size, preview the image at the size visitors will see before you submit.

Should I use mockups or real screenshots?

Use real screenshots as the core of your set. A device frame or styled background is fine for polish, but a mockup that hides the actual interface makes visitors suspicious. A real screen with realistic data is more persuasive than a rendered concept.

Is a demo video necessary?

No, but it helps when your product's value is in a process or speed. A 15 to 45 second silent, captioned clip showing one task is usually enough. If your result is obvious from a single screenshot, put your effort there first.

Can I update my images after launch?

That depends on the platform's editing options, which this article can't confirm for every site. As a rule, plan to refresh screenshots whenever your interface changes noticeably, so the page never shows something your product no longer does.