How to Find Old Website Screenshots

Direct answer: Enter the exact page URL in the Internet Archive Wayback Machine, open Browse History, choose a year and marked date, then inspect the archived page. If the exact URL has no capture, try the domain or homepage and check another archive such as the UK Government Web Archive. An archived replay is evidence of what the archive retrieved; it may be incomplete, missing assets, redirected, or partly dependent on the live web.

1. Find a capture of a specific page

Copy the page’s exact historical URL, including its path and important query parameters.
Open the Wayback Machine and paste the URL into the search field.
Select Browse History.
Choose a year, then a date marked on the calendar. Select a capture time if more than one is available.
Confirm that the replayed address is the page you intended to investigate.

Exact URLs are the best starting point for a specific screenshot. If you do not know the path, enter the site’s domain or homepage and follow links in the archived navigation. A domain search can reveal older paths, redirects, and alternate URL forms.

Understand the calendar colors

The timeline uses status colors that describe the archived HTTP response: blue indicates a 2xx response, green a 3xx redirect, orange a 4xx client error, and red a 5xx server error. A colored marker means a request was recorded; it does not guarantee that the page will replay perfectly.

2. Choose the right date

Pick captures close to the event you are researching: a redesign, product launch, legal change, or content removal. Compare several captures around that date instead of assuming the first or latest result represents the whole period.

Question	What to check
Was this the right page?	Compare the replayed URL, path, title, and visible content with other records.
Was the date meaningful?	Use captures immediately before and after the change you are studying.
Did the page load completely?	Check images, fonts, stylesheets, embedded media, and interactive sections.
Did a redirect alter the result?	Record the original URL, destination URL, and status behavior.
Can the visual claim be supported?	Describe only what is visible in the replay; do not call it a complete screenshot when important parts are absent.

3. When the exact URL has no capture

Search the site’s root domain and homepage.
Try common URL variants: http versus https, trailing slash, locale path, and an older hostname.
Search the archived site’s navigation for the page title or distinctive phrase.
Check the UK Government Web Archive when the site or material is UK-related. Its search supports combinations of phrases and individual words.
Look for independent contemporaneous references, such as a linked document or press announcement, then search those URLs in an archive.

A missing result cannot prove that a page never existed. It only means that the archive has no replayable capture for the URL and search path you tried.

4. Save a page that is live now

Use the Wayback Machine’s Save Page Now workflow when you need to preserve a page going forward. Enter the single URL, submit it, and keep the permanent capture URL it returns. This creates a new capture; it cannot recreate an older screenshot. The documented workflow saves the page entered, not an entire site.

Saving can fail when a site blocks crawling or has SSL settings the archiver cannot use. A successful save can still be partial, especially for JavaScript applications, third-party embeds, or assets that are not crawlable.

5. Treat an archived replay as evidence, not a perfect screenshot

The Wayback Machine is an archive of retrieved web responses. A replay may differ from the original visitor experience:

Stylesheets, images, fonts, or scripts may be missing.
Interactive controls may not work because their APIs were not archived.
JavaScript can change the page after load or request resources from the live web.
Redirects can lead to another page than the one originally requested.
Cookie banners, advertisements, and personalization may be absent or different.
Some images and links can come from the live web under browser settings, so distinguish archived content from live content.

For a historical report, record the capture URL, timestamp, original URL, redirect chain, visible assets, and any missing or live-loaded resources. If visual fidelity matters, preserve a local copy of the replay for your records according to the archive’s terms.

6. Capture a reproducible screenshot yourself

An archive replay is useful for discovery. For a page that is available today, a browser automation script can create a screenshot with a known viewport and wait condition. The following Playwright example captures the full page.

import { chromium } from 'playwright';

const browser = await chromium.launch();
const page = await browser.newPage({ viewport: { width: 1440, height: 900 } });
await page.goto('https://example.com', { waitUntil: 'networkidle' });
await page.screenshot({ path: 'page.png', fullPage: true });
await browser.close();

Use a fixed viewport, timezone, locale, and authenticated state when you need repeatable comparisons. Wait for a known selector when the page renders asynchronously, and disable animations if they introduce visual differences. This method captures the current page; it does not recover a historical state that is no longer online.

7. Or skip the browser setup

ScreenshotNeo provides a website screenshot API and MCP server. One request returns a PNG, JPEG, WebP, or PDF. It can accept consent banners before capture, remove more than 60 known consent platforms plus newsletter popups and chat widgets, and lets each step be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing; the response identifies the result with X-Page-Verdict and X-Billed headers.

See the ScreenshotNeo documentation for all options. A minimal request is:

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

Relevant capture controls include full-page shots with lazy images loaded, CSS-selector element capture, dark mode, 12 device presets or a custom viewport, retina scale, PDF paper size/margins/landscape/page ranges, HTML/CSS rendering, custom CSS and JavaScript, pre-capture clicks, hidden selectors, selector or delay or network-idle waits, blocking ads/trackers/requests/resource types, custom headers/cookies/user agent/Authorization, timezone and geolocation, transparent backgrounds, image resizing, selectable cache TTL, signed links, asynchronous jobs with signed webhooks, bulk capture of up to 100 URLs per call, and a usage API. An OpenAPI specification is available, and parameter names used by other screenshot APIs also work.

ScreenshotNeo has 1,000 shots per month free with no card. Paid plans are Starter $5 for 3,000, Growth $15 for 15,000, Pro $39 for 60,000, Scale $99 for 250,000, and Business $249 for 1,000,000; yearly billing gives two months free and every feature is on every plan. Its MCP server exposes take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients.

Start free with 1,000 screenshots a month and no card.

8. Troubleshooting

Symptom	Likely cause	Fix
No Wayback result	The URL was never captured, the path differs, or crawling was blocked.	Try the domain, URL variants, another archive, and independent links. Do not infer that the page never existed.
Replay redirects elsewhere	The original request returned a redirect or the site changed hosts.	Record both URLs and search the destination and original host separately.
Page is unstyled	CSS or font assets were not archived.	Try a nearby capture date and inspect the asset URLs; report the replay as incomplete.
Images are missing	Image requests were not captured, were lazy-loaded, or are blocked.	Check other captures and whether the browser loaded the image from the live web.
Save Page Now fails	Crawling restrictions or SSL incompatibility.	Confirm the URL works directly, remove temporary query parameters, and try again later or preserve a local record.
Automated screenshot is blank	The page needs more time, a selector, cookies, or authentication.	Wait for a selector or network idle, provide required state, and verify the response before saving.
ScreenshotNeo response is not an image	The page verdict indicates a bot check, blank page, timeout, or failed load.	Read `X-Page-Verdict` and `X-Billed`, then adjust waits, headers, cookies, blocking, or the target URL.

9. Performance, reliability, and cost choices

Archive research: Compare nearby captures rather than repeatedly loading one distant date. Keep the capture URL and timestamp with your notes.
Browser automation: Reuse a browser process for batches, set an explicit timeout, and wait on a meaningful condition instead of an arbitrary long delay.
API capture: Use caching with a TTL when the same page does not need a fresh render. Use bulk capture for up to 100 URLs and asynchronous jobs with signed webhooks for larger workflows.
Cost control: ScreenshotNeo bills only clean shots; bot checks, blank pages, timeouts, failed loads, and cache hits are not billed. Check the verdict headers and usage API when reconciling consumption.
Reproducibility: Fix viewport, device scale, timezone, geolocation, headers, cookies, and wait rules. Dynamic pages can still change between captures.

10. Checklist for a defensible historical screenshot

Exact URL and any known URL variants recorded
Capture date and time recorded
Original and replayed URLs compared
Redirect or HTTP status behavior noted
Text, images, styles, and embeds checked for completeness
Archived resources distinguished from live-loaded resources
Nearby captures compared around the event date
Claims limited to what the visible replay supports

FAQ

Can I find a screenshot if I only know the site’s name?

Start with the domain or homepage in the Wayback Machine, then follow archived links and search for distinctive page phrases.

Does a capture date mean the site looked that way all day?

No. It identifies a request captured at a particular time. Other captures can differ, and missing assets can change the replay.

Can Save Page Now recover a deleted page?

No. It preserves a page that is reachable now and does not retroactively create an old capture.

Can an archive prove a page never existed?

No. A missing capture only shows that the archive has no result for the URL and searches you performed.

When should I use an API instead of an archive?

Use an archive to investigate historical availability. Use an API or browser automation to create consistent captures of pages that are live today.