Public pages only

Capture Website Screenshots Online

Sign in, then paste a public URL. SnapSite opens it in a clean browser and returns a PNG or JPEG you can use for design reviews, reports, previews, and a record of how the page looked.

The capture form on this page needs JavaScript. The notes below explain what the service does and what it refuses.

How a capture works

• The address is checked before a browser starts. Loopback, private networks, link-local addresses, and cloud metadata services are refused.
• A throwaway browser opens the page through an egress proxy that checks the destination again, including after redirects.
• You get a preview in this browser and a download. The file is deleted from the server once the page has it. It is not added to a public gallery.
• Screenshots require a signed-in account. The free plan is a small daily allowance, and the API key uses that same limit. Paid plans raise the limit. Payment is Bitcoin only.

What people use it for

SnapSite is a still picture of a public page: a pricing page before a rewrite, a docs page in a bug report, a mobile layout at 390 pixels wide, or a full-page capture of a long article down to a fixed height.

It is the view a signed-out visitor gets. It is not a recording of a logged-in dashboard, and it is not a guarantee that every animation and live region froze at the same instant you see on your own machine.

Limits that are part of the product

Each capture has a time limit. Full-page shots stop at a maximum height and say so when they are truncated. Video and audio are not loaded. Only ports 80 and 443 are fetched. A delay before the shot cannot be longer than a few seconds, because an open-ended wait is a good way to stall the worker.

Pages are rendered in Chromium with an English locale and the UTC time zone. Safari-only bugs, localized prices, and anything behind a login will not match what you see in your own browser.

Can SnapSite capture a page behind a login?

No. The browser profile is empty and you cannot attach cookies or turn the security checks off. The image is the public page, or the public login wall, whichever the site shows to a signed-out visitor.

How long do you keep the image?

The image is deleted from the server as soon as your browser has it, and any leftover file is removed within 15 minutes. Download it before you leave the page. SnapSite does not claim that nothing is stored while the job is running.

Why was my address blocked?

SnapSite only opens public http and https URLs on ports 80 and 443. It blocks loopback, private and link-local addresses, reserved ranges, single-label hostnames, and cloud metadata names, including when DNS points a normal-looking name at one of those addresses.

Will the screenshot match my browser exactly?

Not always. The render is Chromium, in UTC, with motion paused at capture time. Dynamic pages, A/B tests, and late-loading widgets can still differ. Treat the file as a picture of one moment, not as a pixel-perfect copy of every state.

Do you store the URL I submit?

The worker needs the URL to open the page. It is kept only until the job finishes or fails, then removed. Application logs record the hostname and an error code, not the path or query string. Operators looking at the job list see the hostname, not the path.

Can I capture several pages at once?

Yes. Free captures accept up to three addresses at a time, and a paid plan raises that number. Each address is checked on its own, and the whole batch is rejected if any address is not allowed. Every URL counts toward the daily limit.