FAQ
Why does a capture sometimes fail?
It relies on a third-party screenshot service. Sites with anti-bot protection, login walls or very slow loading can fail; try a different width mode.
Can it capture pages behind a login?
No. The service visits anonymously, so only publicly visible content is captured.
Full page or first screen?
Full page scrolls to the bottom and captures everything, producing a very tall image. First screen captures just the viewport, better for thumbnails.
About this tool
After you enter a URL, the capture is produced by a third-party service: thum.io first, WordPress mshots as a fallback, 30 seconds each, with an error only if both fail. So this tool is really "send the URL to a screenshot service and display the image it returns" — the URL leaves your browser. Do not paste intranet addresses or links carrying tokens or signature parameters.
Widths are 1280 / 1920 / 375 / 768 for desktop, tablet and phone; modes are full page (scrolls to the bottom and captures everything, producing a very tall image) and above the fold (viewport only, cropped to roughly 16:9 by width × 0.9). Use the viewport mode for thumbnails.
Failures are normal rather than broken: the service visits anonymously, so anything behind a login or requiring interaction cannot be captured; sites with anti-bot or JS challenges return a placeholder; slow sites time out. Trying another width, retrying, or testing a different public page usually tells you whether the site or the service is at fault.
Download fetches the image and saves it as PNG; if the service does not allow cross-origin reads, it degrades to opening the original so you can save it manually. Third-party services also tend to cache a URL for a while, so repeat captures may return the same image — append a harmless query parameter to force a fresh one.