Website Screenshot Tool, Capture Any Page Full Page Free
This website screenshot tool captures a full page image of any URL in seconds. Choose mobile, tablet, or desktop viewport widths, add a load delay for animated pages, then download or copy the image, no sign up needed.
How this works. The page is loaded in a headless browser on a rendering service and returned as an image. Nothing is installed and nothing is stored on our side. Pages behind a login, a paywall, or bot protection cannot be captured, and some sites block automated browsers entirely.
About splitting. Slicing a full page capture into scroll-sized tiles happens in your browser using a canvas. That needs permission to read the image pixels, which the rendering service controls. When it is not granted, the split option is hidden and the message says so rather than failing quietly.
How this tool renders a screenshot of any URL without a browser engine of its own
Capturing a pixel accurate image of a web page requires an actual rendering engine, laying out HTML and CSS, running JavaScript, painting the result, and encoding a bitmap from it. That is a full headless browser’s job, something well beyond what a static web page can do inside another browser’s JavaScript sandbox. So this tool does not render anything itself. It builds a specially formatted image URL and hands the rendering work to a free public service called thum.io.
The image URL is the entire request
There is no API key, no POST request, and no backend on this site involved in generating the image. The tool assembles a URL following thum.io’s path based parameter format and sets it as an <img> tag’s source. Your browser requests that URL exactly the way it requests any other image, thum.io’s servers render the target page headlessly on their end, and stream back a PNG or JPEG.
https:// prefix added automatically if it is missing one, so a bare domain like example.com becomes a fetchable address.
width/{px} sets the virtual browser viewport width thum.io renders at, crop/{px} optionally cuts the capture to a fixed height instead of the full page, and wait/{seconds} optionally delays the capture, giving slow loading pages, animations, or cookie banners time to settle before the screenshot fires.
Image() object. thum.io renders the page on its own infrastructure, which typically takes 5 to 15 seconds on a page’s first capture and is much faster on repeat requests due to their own caching, and returns the finished image once ready.
Because this is a plain image request, the URL you enter is sent to thum.io, a third party public service unaffiliated with this site, and thum.io in turn fetches and renders the destination page you specified. Nothing about the capture is stored or processed on our servers. If you want a private capture with no third party visibility, that means running your own headless browser instance, which is outside what a browser hosted tool can offer.
| Parameter | Path segment | Effect |
|---|---|---|
| Device width | width/{px} | Sets the rendering viewport, desktop, tablet, or mobile widths |
| Crop height | crop/{px} | Cuts to a fixed height instead of capturing the full scrollable page |
| Load delay | wait/{seconds} | Pauses before capture so late loading content and animations settle |
| Format | trailing format flag | PNG by default, JPEG optionally for smaller file size |
Full page vs cropped
Leaving crop unset captures the entire scrollable page height, which is what most people expect from a full page screenshot. Setting a crop value gives you a fixed above the fold capture instead, useful for consistent thumbnail sizing.
Why capture can fail
Pages that require a login, block headless browser user agents, or sit behind aggressive bot protection will often fail to render through any third party screenshot service, this one included, since thum.io’s renderer is itself detectable as automated traffic by some sites.
- thum.io’s documentation covers the full parameter set this tool builds URLs against, including options not exposed in this interface.
- MDN’s HTMLImageElement reference explains the Image object mechanics used to detect a successful load.
- Chrome’s headless mode documentation describes the kind of engine a service like thum.io runs behind the scenes to produce the render.
Where screenshots get used
Grabbing a visual reference of a competitor’s landing page for a design review, archiving what a page looked like before a redesign or content change, generating link preview thumbnails for a newsletter or internal wiki, quickly checking how a site renders at mobile versus desktop widths without opening dev tools, and capturing evidence of a page’s state for a support ticket or dispute.
FAQ: Website Screenshot Tool
The rendering service needs to spin up a real headless browser, load the full page, wait for any specified delay, then capture and encode the image, which typically takes 5 to 15 seconds for a page it hasn’t rendered recently. Subsequent captures of the same URL are often faster since some rendering services cache recent results briefly.
No, this tool can only capture publicly accessible pages, since the rendering service loads the URL without any of your personal session cookies or login credentials. Any page that requires authentication will render as its login screen or an access denied page instead of the content behind it.
The rendering service loads the page fresh each time with no prior cookie consent recorded, so cookie banners, newsletter pop-ups, and similar overlays that appear for first time visitors will show up in the capture, exactly as a new visitor would see them. There is no way to dismiss these automatically since every site implements them differently.
This usually means the page hadn’t finished loading its content, images, or animations by the time the capture happened. Increase the Load Delay setting to give the page more time to render before the screenshot is taken, particularly for pages with heavy JavaScript, video backgrounds, or content that loads in as you scroll.
The rendering service returns a standard PNG image by default, which preserves sharp text and clean edges well, making it suitable for documentation, presentations, or design references without noticeable compression artifacts.
Extremely long pages, such as infinite scroll feeds, may be capped at a maximum practical height by the rendering service rather than capturing forever. For most standard web pages, blog posts, and landing pages, the full scrollable height captures completely without any issue.
The tool itself places no restriction on how you use the image, but the content shown in the screenshot, including any logos, text, or design, still belongs to whoever owns that website. Using a screenshot of a page you don’t own for commentary, comparison, or reference purposes is generally fine, but check copyright and fair use considerations before using it in commercial marketing material.
No, this site does not log or store the URLs you capture. The screenshot request is made directly from your browser to the public rendering service, which may briefly cache the resulting image on its own end for performance, subject to that service’s own policies.
From the blog
How the web actually moves
DNS, TLS, headers and the hops between a click and a page.
