Product screenshots on a SaaS site should prove one claim each

A product screenshot on a SaaS website is evidence: a picture of the software that proves one claim the words next to it make. When it works, a buyer sees the thing they were promised. When it does not, it is the largest file on the page and the one part nobody reads.
The reason is measurable. In eyetracking studies, Nielsen Norman Group found that users ignore purely decorative images and scrutinise images that carry information, product photos included (Nielsen Norman Group). A screenshot falls on one side of that line or the other. A full dashboard shrunk into a hero, with text too small to read, lands on the decorative side, and it is one of the factors that decide what makes a landing page convert.
Where product screenshots go wrong
Five faults turn a screenshot into decoration.
- The whole window, shrunk. A 1440 px capture shown in a 640 px column is drawn at 44% of its size, so 14 px interface text arrives at about 6 px. Nobody reads 6 px text. The eye moves on.
- Empty or fake data. Lorem ipsum, "Test User 1", a chart with three points. The screen proves the layout exists and nothing else.
- No claim attached. The image sits beside a headline about saving time and shows the settings page.
- Words baked into the image. A headline or callout drawn into the PNG can't be translated, searched or resized, and a screen reader can't read it.
- A screen the product no longer has. The interface changed two releases ago and the site still shows the old navigation. The first demo call shows the difference.
Real UI, simplified UI or no UI: which to use where
There are three ways to show software, and each one proves something different.
A real screenshot, cropped
Use it when the claim is about the product itself: the density of a table, the wording of a report, what an approval flow asks for. A buyer comparing two tools wants the real screen, and a cropped real screen is the hardest image to argue with. Its cost is upkeep. It ages with every release that touches that view.
A simplified user interface
A simplified user interface (SUI) is an illustration of a screen that reduces the parts that don't matter to grey shapes and keeps the parts that do in full detail (Wikipedia). Slack and Google Analytics have used the style in onboarding. It suits a homepage that explains how the product works, where the order of steps matters more than the data. It brings two practical gains: it survives small interface changes, and it needs far less translation, since most of its text is gone.
No interface at all
An illustration or an abstract image fits only when the product has no screen worth showing: an API, an SDK, an infrastructure service. There, a code sample or a diagram of the request path proves more than any picture. How a product site picks its visual language is covered in our piece on art direction for SaaS.
The rule for one site: simplified screens to explain, real crops to prove, nothing decorative.
How to make a screenshot prove one claim
- Write the claim first. One sentence the image must prove, for example "you see who owes you money, and since when". If no sentence comes, the page doesn't need the image.
- Crop to the part that proves it. Keep the region the claim is about and enough of the frame to place it. A table with six rows proves "who owes you" better than the whole app with the table at the bottom.
- Capture at the size it will be shown. Size the browser window so the crop appears at 100% or close to it, then export at twice that width for high-density screens. Interface text should land on the page at the size it has in the product.
- Seed demo data that reads as real. Plausible company names, amounts with cents, dates in the last month, a chart with enough points to show a trend. Keep one demo account, so every screenshot on the site tells the same story. Never use a real customer's data, even blurred.
- Frame every screenshot the same way. One corner radius, one shadow or border, one background, the same browser chrome or none. Consistent framing is art direction: it makes twelve captures read as one product, the same rule our shot list for software photography applies to photos. Perspective device mockups rarely help. They shrink the screen and tilt the text.
- Put the words in HTML. The claim goes in the caption or in the copy beside the image, as real text, and the alt text says what the screen shows: "Receivables table with six clients, two overdue by more than 30 days". Arrows and callouts can be drawn, but the sentence they point to lives in the page.
Screenshots and page speed
The hero screenshot is often the slowest thing on a product page. The 2025 Web Almanac found that an image is the Largest Contentful Paint element on 76% of mobile pages and 85% of desktop pages, and that only 62% of mobile pages reach a good LCP (HTTP Archive Web Almanac 2025). Four settings decide whether the screenshot is part of that problem.
- Never lazy-load the hero. About 16 to 17% of pages lazy-load their LCP image, which delays the one picture that should arrive first.
- Raise its priority. With
fetchpriority="high"on the hero image, Google's test on Google Flights moved LCP from 2.6 s to 1.9 s (web.dev). - Set width and height. On mobile, 62% of pages leave at least one image without dimensions (same Almanac), and each of those can shift the layout as it loads.
- Serve the right file. Screenshots are flat colour and sharp text: WebP or AVIF, lossless or at high quality, with
srcsetso a phone downloads the phone-sized file (MDN). JPEG smears the text edges that make a screenshot readable.
What accessibility asks of a screenshot
A screenshot is an image, so it needs a text alternative that says what it shows and why it is there. A dense one, such as a dashboard full of numbers, counts as a complex image: W3C's guidance is a short alt plus a longer description nearby, in a caption or in linked text (W3C WAI). A headline drawn into the image runs into WCAG success criterion 1.4.5, which asks for real text wherever the same visual result can be achieved with text (W3C, Understanding 1.4.5). Keep the headline out of the image and the problem goes away.
How to keep screenshots current
A screenshot is a copy of the product that doesn't update itself. Three habits keep the copies honest.
- Keep an inventory. One list of every screenshot on the site, the product view it shows and the page it sits on. When a release changes a view, the list says which images to retake.
- Script the capture. A Playwright script that signs in to the demo account, opens each view, sizes the window and saves the crop retakes the whole set in one run. Run it in one pinned browser image, for the reason our visual regression guide gives: fonts render differently on each operating system.
- Draw what changes often. A view redesigned every quarter is a poor candidate for a real screenshot on the homepage. Show it as a simplified screen and keep real crops for the views that hold still.
What this looks like on one page
Take the homepage of an invoicing product whose headline is "Know who owes you, and since when". The hero image is a crop of the receivables table: six clients, amounts, days overdue, two rows past 30 days in a darker tone. It is captured at 600 CSS pixels wide, exported at 1200 for high-density screens, and served as WebP with a fixed width and height and fetchpriority="high". The caption under it repeats the claim in text. Further down, a simplified drawing explains the three steps from invoice to reminder, because there the order matters and the data doesn't. Every image on the page has a sentence it proves.
Sources
Frequently asked questions
A device frame helps when the device is the point: a mobile app, or a tool used on a tablet in a warehouse. For a desktop SaaS, a laptop mockup spends part of the width on the bezel and often tilts the screen in perspective, which makes interface text harder to read. A flat crop with a consistent border or shadow shows more product in the same space. If the brand wants a frame, pick one flat, front-facing style and use it on every page.
An image of an interface the product doesn't have is a promise the first demo breaks. Image models invent controls, labels and numbers that look plausible and don't exist in the software. AI tools are useful around the screenshot instead: generating realistic demo data, drawing a simplified version of a real screen, drafting alt text that a person then checks. The screen itself should be captured from the product.
Yes, wherever the interface text carries the claim. A visitor reading a Spanish headline next to an English dashboard can't tell whether the product works in their language. If the product is localised, capture each language from a demo account set to that language; with a capture script that is one more loop. If it isn't localised, say so near the image and lean on simplified screens, which carry little text.
Related articles
October 18, 2026 · 6 min read
September 28, 2026 · 10 min read
April 19, 2026 · 7 min read