Web pages are editable. The listing that promised "free returns" can say something else tomorrow, the seller profile can vanish an hour after you file a complaint, and the article you were quoted in can be silently rewritten. When a dispute starts, the page as it was at the time is often the whole argument — and by then it's usually gone.
A screenshot from your own phone or laptop is the natural reflex, and it's better than nothing. But it has a credibility problem: everyone knows how easy screenshots are to crop, retouch, or fabricate outright. There's no capture time anyone can check, no proof of which URL it came from, and the file sits in your camera roll where you could have done anything to it.
What actually works is a capture made by a neutral third party: a service that visits the URL itself, records when it did so and what settings it used, stores the image where you can't modify it, and gives you a link you can hand to the other side. This guide shows how to make one in under a minute, what it's good for, and — just as important — where its limits are.
What a screenshot needs to work as proof
Four properties separate a usable record from "trust me":
- A capture time you didn't type yourself. The timestamp should come from the capturing service's clock and be displayed on the record, not written into a filename by you.
- The exact URL, on the record. A crop of a page proves nothing about where it came from. The full address needs to be stored alongside the image.
- The whole page, not a fragment. A full-page capture shows the claim in context — the header that identifies the site, the fine print below the fold, the date on the post. Crops invite the question "what's outside the frame?"
- Storage you can't edit. If the image lives on your device, you could have altered it. If it's rendered and hosted by an independent service with no edit function, that objection disappears.
Saving a page as evidence in under a minute
- Open site-shot.com and paste the URL of the page. Capturing is free and needs no account.
- Turn on Full page in the options so the capture includes everything from header to footer.
- Tick Save to my library, then capture. The screenshot goes straight into your saved library with the URL, time, and settings on record.
The library comes with any paid plan — plans start at $5/month on the pricing page, and the Save to my library checkbox appears once you're on one. Not on a plan? The free tool doesn't store anything — but you can still capture and download the full-page image on the spot: a whole-page image beats a cropped device screenshot even when it lives on your own disk. The hosted record — the part the other side can check — is what the library adds.
Two details matter more than they look:
What lands in your library is the exact image the tool showed you. The save doesn't re-visit the page — it stores the very capture you're looking at, byte for byte. The page can change or go offline seconds later; your record is still the page as you found it.
What you get is a record page, not just an image file. Each saved screenshot lives at its own link that displays, alongside the image: the source URL in full, the capture date and time, the image dimensions and file size, and the capture settings used. The record starts private — only you, signed in, can open it. When you want someone else to see it, switch it to public; you can switch it back, download the image, or delete the record at any time — but there is no way to edit it, which is exactly the point.
Disputes where this is usually enough
Most disagreements never see a courtroom. They're settled by a marketplace support team, a payment processor, a platform moderator, a landlord, or the other party deciding it isn't worth it once you show your record. That's the arena where a timestamped third-party capture earns its keep:
- Marketplace and shop disputes. The product listing said one thing when you ordered; now it says another, or it's gone. Capture the listing the moment something feels off — before you open the dispute, because sellers edit fast afterwards.
- Chargeback documentation. Card issuers ask for evidence of what was promised — the price, the delivery terms, the "in stock" label. A dated capture of the offer page is precisely that.
- Changed terms and policies. Return policies, guarantees, pricing pages, "lifetime deal" promises. If a promise influenced your purchase, save the page that made it, on the day it made it.
- False or misleading claims. A competitor's landing page making claims about your product, an ad promising what the product can't do. Capture it while it's live; such pages have short lives once challenged.
- Harassing or defamatory public posts. Public posts, reviews, profiles, and comments get deleted the moment their author senses consequences. A capture with a recorded time and URL is what you attach to the platform report — or hand to a lawyer.
- Your content used without permission. Your photos, texts, or designs on someone else's public site. Capture the infringing page and its context (the homepage, the about page) before sending the takedown notice.
- Listings that expire by design. Job postings with a promised salary, rental listings with a stated price, event pages with stated conditions — all routinely gone in weeks, and routinely the thing you need to reference later.
Making the record stronger
A few habits separate a capture that settles the argument from one that raises new questions:
Capture at first sight. The moment you think "I might need this" is the moment to capture. Pages change fastest exactly when a conflict begins.
Capture the neighborhood, not just the page. The seller's profile, the site's terms page, the pricing page next to the product page. Individually small, together they make the story hard to dispute. Your library groups saved captures by site, so the cluster stays together.
Re-capture the same URL as things develop. If the page changes mid-dispute, capture it again — the before/after pair is often more persuasive than either shot alone. In the library, repeated captures of the same URL stack into a little history you can step through.
If location matters, capture from the right one. Prices, availability, and ads can differ by country. A capture routed through the relevant market shows what a visitor there saw — see screenshots from another country (included with any paid plan).
Keep it private; share it deliberately. The record starts private, visible only to you. When it's time to show it — to the support team, the platform, the opposing party — switch it to public and send the link. The link is unguessable and kept out of search engines, so in practice it's seen by the people you send it to; and a neutral, view-only page with the metadata visible is more convincing than an image pasted into an email.
Download a copy anyway. The record page is the evidence; a local copy is your backup. For a bundle — say, everything you're attaching to a claim — select the captures in your library and export them as a ZIP in one step.
Where the honest limits are
Public pages only. Site-Shot visits the URL as a fresh, logged-out visitor. Anything behind your login — order pages in your account, direct messages, members-only groups — will not appear. For those, you're back to device screenshots (take them immediately, keep the originals, and photograph the screen with a second device if the stakes justify it).
This is not notarized forensic evidence. For everyday disputes — platform reports, chargebacks, support escalations, demand letters, small-claims preparation — a timestamped third-party capture is typically what's asked for and what works. But formal litigation sometimes requires evidence collected under stricter, certified procedures (hash-signed captures, chain-of-custody records, notarization). Whether you need that level is a question for your lawyer, and it's better asked early. What you can always do meanwhile: capture the page now — it won't wait for the consultation.
The Wayback Machine is a complement, not a substitute. The Internet Archive's Save Page Now is free and its timestamps carry real weight — use it too when the stakes are high. The trade-offs: archived pages are public forever (awkward when the dispute is private), the archive can decline or later remove pages, JavaScript-heavy pages often archive broken, and what you get is a re-rendered page, not a fixed image with its capture settings on record. When it really matters, do both: archive publicly and keep a private full-page image on record — they cover different failure modes.
FAQ
How do I save a screenshot of a web page as evidence? Capture the page at site-shot.com with Full page enabled and Save to my library ticked. You get a private record page showing the image together with the source URL, the capture date and time, dimensions, and the capture settings — recorded by the service, not typed by you. Capturing and downloading the image is free with no signup; the library is included with any paid plan.
Is a screenshot valid proof in a dispute? It depends on who's judging. For marketplace support, payment disputes, moderation reports, and most everyday disagreements, a capture with a third-party timestamp and the URL on record is substantially stronger than a screenshot from your own device, and usually sufficient. For court proceedings, evidence standards vary by jurisdiction — ask a lawyer whether certified forensic preservation is needed in your case.
How long is the saved screenshot kept? Screenshots in your library stay as long as your subscription is active — there's no per-screenshot expiry to keep track of. You can download the image at any time (a downloaded copy is yours forever) and delete the record whenever you choose.
Can other people see my saved screenshot? Not unless you let them. Saves start private — only you, signed in, can open the record; for everyone else the link simply doesn't resolve. To show it to someone, switch the record to public: the link is unguessable and excluded from search indexing, so it reaches the people you send it to. You can switch it back to private, or delete it, at any time.
Can I capture a page that requires logging in? No. The renderer visits the URL as a fresh visitor, so it sees what any logged-out member of the public sees. That's a feature for evidence — it shows the page wasn't personalized to you — but it means account pages, DMs, and paywalled views can't be captured this way.
Found a page you might need later? Capture it free — no signup — at site-shot.com. To keep pages on record, every plan on the pricing page includes library storage, search, and ZIP export.