Screenshots That Explain a Product Without Words

Most people decide whether to look further at a product before they read a single sentence. They glance at the pictures. If the pictures explain the product, they stay. If the pictures are confusing, cluttered or dull, they go. Screenshots are therefore not an illustration of your listing. They are the main argument.

Here is how to make screenshots that make the argument well.

What a screenshot is for

A screenshot answers three questions: What does this look like? What does it do? Would I know how to use it? A good one answers all three at a glance. A weak one answers none, and merely proves that an interface exists.

Before you capture anything, write down the one idea each image should carry. "You can see all your invoices in one place." "Pick a date and it plans the route." "Here is the report your client receives." If you cannot name the idea, the image does not need to exist.

Choose the right moments

Products have many screens. Visitors want to see the ones where value appears.

The result. The finished thing the user gets: the chart, the plan, the design, the report.

The moment of action. The single step that makes people say "ah, I can see how this works".

The distinctive detail. Something that sets you apart: an unusual control, a clever view.

The context. How it fits into a user's world: a phone beside a laptop, an email notification, an integration.

Skip the settings page, the empty dashboard and the login screen, unless the login is itself your selling point.

Tell a story in sequence

Most platforms show images in order, so plan the order.

1. Image one: the hook, the most compelling view.
2. Image two: how you get there, the key action.
3. Image three: a closer detail.
4. Image four: the outcome or proof.

Product Hunt's preparation guidance asks makers to plan their gallery thoughtfully and notes a minimum of two images, with the ability to reorder them. The same attention to order helps on any platform.

Prepare the data

Empty screens tell no story. Fill your product with plausible sample content before capturing.

• Use realistic names, numbers and text. "Q3 campaign report", not "Test 1".
• Avoid obvious placeholder text such as lorem ipsum, unless it is truly irrelevant.
• Do not use real customer data. Ever. Create a demo account with invented people.
• Show variety. A list with five different items looks alive. Five identical ones looks fake.
• Keep numbers modest and believable. Wildly impressive figures invite scepticism.
• Check for personal details in the browser: bookmarks, tabs, email addresses, notification pop-ups.

A helpful practice is to maintain a permanent "demo" account, filled with tidy, believable data, which you can use whenever you need to capture a screen.

Frame it cleanly

A raw screenshot of a browser window looks like a screenshot. A framed one looks like a product image.

• Crop to the relevant part. Remove browser chrome, toolbars and unused areas.
• Keep consistent margins. Use the same padding, background colour and corner radius across the set.
• Use a simple background. A flat colour or a very soft gradient.
• Add a subtle shadow to lift the screenshot from the background.
• Maintain consistent size and aspect ratio across the gallery. Product Hunt's guide recommends 1270 by 760 pixels for gallery images, which is a convenient reference even if you publish elsewhere.
• Avoid tilted, perspective or three-dimensional frames that make text hard to read.

Make text readable

Interface text is small, and images shrink on a phone. Test at actual size.

• Zoom the interface before capturing, so labels are larger.
• Hide parts that are not needed to keep the view uncluttered.
• Annotate sparingly. One arrow or highlight beats five. A thin leader line to a single element is plenty.
• Check contrast. Light grey on white vanishes.
• Consider a dark-mode version if your product has one and your audience likes it.

Add words only where they help

If you add captions, keep them to a handful of words and make them large. "Plan a week in two clicks" is fine. A paragraph in a caption is not.

For people who cannot see the image, write alternative text. Google's image guidance advises meaningful alt text that focuses on context and not keyword stuffing, using an example of describing what the picture actually shows. For a screenshot, describe the view and the key point: "Weekly meal planner showing seven days with breakfast, lunch and dinner slots filled."

Also use descriptive file names, such as meal-planner-weekly-view.png, as Google suggests, instead of default names.

Choose the right format and size

Google's image documentation lists JPEG, PNG, WebP, SVG, AVIF, BMP and GIF as supported formats, and notes that images significantly affect page load times. For screenshots with sharp text, PNG or WebP generally works well. For photographic images, JPEG or WebP is smaller. Keep file sizes reasonable and check the platform's limit before uploading. Product Hunt, for instance, mentions that thumbnails should be under 3MB.

Consider motion carefully

Short animated captures can show a flow better than a still. If you use one:

• Keep it brief. A few seconds.
• Make the first frame good, since some viewers see only that.
• Avoid flashing, which can harm some viewers.
• Provide a still alternative for anyone who prefers it.

If a flow needs more than a few seconds, a separate short video may be better. Our article on product videos covers that.

Check from the viewer's side

Before you publish, view your images the way a visitor will.

1. Open the listing on a phone. Can you read the key text?
2. View it in a small thumbnail. Is the subject clear?
3. Check in both light and dark modes if the platform has them.
4. Look at it on a slow connection. Does it load quickly enough?
5. Ask a stranger to describe what they see.

Common mistakes

• Showing everything. A screenshot of a whole complex screen says nothing in particular.
• Showing nothing. An empty state proves the product is empty.
• Leaking data. Emails, names and tabs you did not mean to share.
• Inconsistent frames. Mixed sizes and styles look careless.
• Old interface. An out-of-date screenshot is quietly misleading.
• Hiding the product. A logo slide in a gallery of screenshots.
• No alt text. Missed access and missed context.

A routine for every release

Screenshots go stale. When you change a main screen, replace the matching image. Keep a folder of current originals with dates, and a simple checklist: clean demo data, consistent frame, readable text, alt text written, file name descriptive. A small routine prevents the slow decay that makes a listing look abandoned.

On this site

Every entry shows a logo and an automatic screenshot of the homepage, and any entry, free or paid, can add a gallery of your own screenshots. You upload them from your account once the listing is started. A launch entry is currently $5. Who designed and built the site is on the about-founders page.

A worked example: capturing a meal planner

Imagine you are capturing images for a meal-planning app. The raw version of your first screen shows an empty week with a "No meals yet" message and a browser with fourteen tabs open. Improve it in four steps.

First, fill the week with believable meals: a lentil stew on Monday, a fish tray bake on Wednesday, pancakes on Sunday. Give a couple of slots a small cooking-time label. Second, close the browser tabs, hide the bookmarks bar and use a clean window at a consistent size. Third, crop to the planner itself and place it on a soft, flat background with even margins. Fourth, write the alt text: "Weekly meal planner with seven days of dinners filled in, each with a cooking time."

The result tells the whole story. A visitor sees a full week, understands the product in a second and can imagine their own meals in the same slots. The raw version would have told them only that the app exists.

Keeping screenshots accessible

Not everyone sees images the same way. Make sure essential information in a screenshot is also available in text on the page, for example by describing the key result in a sentence nearby. Avoid putting critical instructions only inside an image. Use sufficient contrast, and do not rely on colour alone to show a status; add an icon or a label. These habits help people with low vision, people on poor connections and anyone viewing in bright sunlight, which is most of us at some time.

When a screenshot is the wrong tool

Some products do not look like much. A command-line tool, an API or a background automation may have little to photograph. In those cases show the result instead of the interface: the output file, the notification that arrives, the chart the data produces, a short code snippet beside the thing it makes. Treat the picture as evidence that the product works, and let the words explain the rest. A tidy, honest image of an outcome is always better than a decorative illustration that says nothing.

The takeaway

A screenshot should answer "what does it look like, what does it do and could I use it?" without a word of explanation. Choose the right moments, fill them with believable data, frame them consistently, keep text readable and describe each image for people who cannot see it. Do that and your pictures will do the selling while you do the building.