Screenery

Screenery / Guides

Outdated product screenshots in marketing: homepage, sales decks, app stores

At every launch someone reads the headline, argues about the tagline and checks the pricing table. Almost nobody checks the screenshot next to them. This page goes through the five places marketing shows the product, says what anyone has measured about each one, and ends with what keeps the pictures current.

Why the pictures fall behind the words

A launch has a review process for words. Product marketing rewrites the copy, legal reads the claims, and someone signs off. A screenshot rarely has an owner in that process. It is a file exported from a design tool or pasted into a slide, and it shows the product on the day someone took it. When the product changes, nothing tells the image.

People do notice signs of neglect. The Stanford Guidelines for Web Credibility, published by B.J. Fogg in May 2002, came out of three years of research with more than 4,500 people. Guideline 8 says to "Update your site's content often (at least show it's been reviewed recently)." Two cautions apply. The guideline is about content in general, not screenshots. And it is 24 years old. It supports the idea that visitors trust a site that looks maintained. It doesn't measure what one old screenshot costs.

For the wider evidence, see what the research says about product screenshots.

Homepage hero

In our experience, the hero image is the most viewed screenshot most companies have. It is also the one most likely to be a mockup, an illustration of the product, or a screenshot from the last redesign.

Baymard Institute's SaaS UX benchmark found that 35% of SaaS sales sites fail to highlight the service's UI enough. In Baymard's usability testing, abstract drawings of an interface did worse than real screenshots. The article is from June 2022 and gives no count of sites or participants.

HowdyGo, which sells interactive demo software, looked at "over 200" B2B SaaS websites and reported that 29.8% don't show their product in a screenshot or GIF on the landing page. Of the sites that did show it, 94% used a plain screenshot. The post names its selection criteria (target customer, funding, industry, country) but gives no exact count, no list of sites and no date for the review. It is vendor data from a company with an interest in the answer.

Measured: how many sites show the product at all. Not measured: how many of the screenshots that are shown still match the product. Neither source checked that, and we found no study that did.

If your hero is a mockup, here is how one team chose to replace homepage mockups with real screenshots that its tests take. For why buyers care, see what B2B buyers look at.

Pricing and feature pages

In our experience, feature pages fall behind faster than the homepage. There are more of them, and each one shows a specific screen. A renamed menu or a moved button makes one page wrong in a way a buyer may not spot until the trial. A pricing page that shows a plan or billing screen goes wrong every time pricing changes.

These pages behave like documentation. A 2026 study of VS Code's docs found that a screenshot's age is a poor test of whether it is wrong. Some very old screenshots were still accurate, and people outside the docs team reported most of the outdated ones.

Measured: nothing specific to marketing feature pages that we could find. Not measured: how often they drift, or whether a buyer who notices trusts the page less.

The first step is a list: every page, every screenshot on it, and the screen in the product it shows. Without that list nobody can tell which pages a product change broke. See how to audit outdated screenshots.

Sales decks

We think decks keep outdated screenshots the longest. A rep downloads the deck in March, tailors it for one customer, and is still presenting that copy in October. Marketing fixes the master. The copies on laptops stay as they were.

Two companies that sell sales software say the same in their own guides. Apollo's guide to sales pitch decks, from February 2026, lists "deprecated product screenshots" among the ways decks go stale, and suggests a quarterly review. Highspot's guide, updated October 2026, describes sellers using AI to review an old deck and pull replacements from approved libraries, so they stop circulating "retired screenshots". Both are opinion. Neither cites data for these points, and Highspot sells a product that addresses exactly this problem.

Measured: nothing. Not measured: how old the screenshots in a typical deck are, or how often a prospect notices. Advice about an outdated sales deck, including ours, is experience, not evidence.

What helps is one master deck, product screenshots on their own slides so they can be swapped, and a "screens as of" date on those slides. A deck holds its own copy of each picture. A fresh screenshot only reaches it when someone puts it there.

App store listings

App stores are the only place on this list with written rules. Apple's App Review Guideline 2.3 asks that an app's metadata, screenshots included, accurately reflect the app's core experience and that developers keep them up to date with new versions. Guideline 2.3.3 says screenshots should show the app in use, not merely the title art, login page or splash screen.

Apple's App Store Connect help says you upload screenshots on the version page or in Asset Library, then submit them for review when the app has one of five statuses: Prepare for Submission, Invalid Binary, Rejected, Metadata Rejected or Developer Rejected. Each of those is the status of a version that hasn't gone live. The same page describes updating creative assets on a live version without submitting a new one, and it calls creative assets separate from screenshots. It describes no such path for screenshots. Plan a screenshot update as part of a version you are submitting anyway.

You may have read that App Store screenshots can't change after approval. Apple's pages don't say that in those words, so we don't repeat it. What they say is above.

Listings also multiply the copies. Apple scopes screenshots to each version, each Custom Product Page and each Product Page Optimization treatment, and you can add them per localization. Every one of those is another set to keep current. We did not check Google Play's rules for this page.

Measured: nothing about how often listings fall behind the app. Not measured: whether outdated App Store screenshots cost installs. Apple's guidelines are rules, not research.

Launch posts

A launch post is the one place an old screenshot can be correct. A post dated March 2025 that shows the product as it was in March 2025 is a record. It becomes a problem when the post keeps working as current marketing. It ranks for the feature's name, the docs link to it, or sales sends it to prospects. Then a reader sees a screen from last year with nothing to say so.

Put the date at the top of the post. When a post becomes the main page for a feature, write a current feature page and link to it from the post, rather than rewriting the post. The same goes for demo GIFs and videos, which take longer to redo than a still.

Measured: nothing we found.

How often to update product screenshots

No study gives an interval, and we won't invent one. Apollo's quarterly review is a vendor's suggestion for decks. The better trigger is a product change. When a screen changes, every picture of it is out of date that day, whether it was taken last week or two years ago. A calendar can't see that, which is the same reason age failed as a test in the VS Code study.

So update on change, and keep a calendar review only for the places a change can't reach on its own: decks and store listings.

What keeps them current

Two things help, and only web pages get the full benefit.

Decks and app stores need an upload. A deck stores its own copy of each image, and an App Store listing takes screenshots through App Store Connect and Apple's review. Tests can still make the files, so the update becomes a download and an upload instead of a retake. Someone still has to do it, so put it on the launch checklist next to the copy review.

Launch posts want the opposite, a picture that never changes. A Screenery version URL (@v_…) points at one build forever, so the post keeps showing what shipped that day. See Channels and versions.

Sources

We opened every page below on 15 November 2026 and checked each number and quote on this page against it. We marked the vendor pages.

  1. B.J. Fogg, "Stanford Guidelines for Web Credibility", Stanford Persuasive Technology Lab, May 2002
  2. Edward Scott, "35% of SaaS Sites Fail to Make the Service's UI Sufficiently Prominent to Prospects", Baymard Institute, June 2022
  3. Tom Bruining, "Your landing page has to show your product", HowdyGo, updated July 2026 (vendor)
  4. Apple, App Review Guidelines, sections 2.3 and 2.3.3
  5. Apple, App Store Connect Help, "Manage your App Store assets"
  6. Apollo, "Sales Pitch Deck: How to Create Presentations That Close Deals", February 2026 (vendor, opinion)
  7. Brooke Holland, "How to Create a High-Converting Sales Pitch Deck", Highspot, updated October 2026 (vendor, opinion)

Related guides