Capture the whole page header to footer, including everything below the fold as a single image. Lazy-loaded content is triggered, cookie banners and ads are removed, and the file downloads in seconds. Free, no signup, no extension.
Free to try - no account required.
Your full page screenshot will appear here.
This request matches the settings you selected above. Swap in your API key and drop it straight into your project to automate the same capture.
A normal screenshot captures whatever fits inside the browser window typically the first 900 pixels or so of a page. A full page screenshot captures the entire document: every section, every row of the footer, and everything that only appears after you scroll.
Getting that right is harder than it looks. Modern pages defer images until they enter the viewport, pin headers to the top of the window, and inject consent overlays on first visit. Naively stitching scrolled screenshots together produces repeated headers, blank image placeholders, and visible seams.
This tool renders the page in a real Chromium browser, scrolls the full document height so deferred content loads, dismisses consent dialogs, and then captures the result as one continuous image. No seams, no placeholders, no clipping.
The capture height is the height of the page itself, so a 12,000-pixel article comes back as a single 12,000-pixel image.
Lazy-loaded images and off-screen components render before the shot is taken, so the output is complete rather than half-empty.
Because the width is pinned, the same page captured on two different days is directly comparable which is what makes visual diffing possible.
Every major browser can already capture an entire web page without an extension. The feature is just buried in a different place in each one. Here is the exact route for all four, and the point at which each one stops being enough.
Open DevTools with F12, or Cmd + Option + I on macOS.
Press Ctrl + Shift + P, or Cmd + Shift + P on macOS, to open the Command Menu.
Type screenshot and choose Capture full size screenshot.
Where it stops: Captures the document at its current loaded height, so anything still lazy-loading below the fold comes out blank.
Right-click on any empty area of the page.
Choose Take Screenshot from the context menu.
Click Save full page, then Download.
Where it stops: The only browser with a genuinely one-click full page capture, but it offers no viewport width control and no way to script it.
Enable the Develop menu in Settings, under Advanced.
Open Web Inspector and select the Elements tab.
Right-click the html node and choose Capture Screenshot.
Where it stops: Hidden three levels deep behind a developer setting, and it fails on pages that pin elements to the viewport.
Press Ctrl + Shift + S to open Web capture.
Choose Capture full page.
Use Save to write the image to disk.
Where it stops: Edge is Chromium, so the DevTools method works here too. Web capture is friendlier but re-encodes and can soften fine text.
All four routes above share the same three blind spots. They are the reason a native capture of a long marketing page so often comes back half empty.
Operating system screenshot shortcuts photograph your screen, not the document, which is why Cmd + Shift + 4 and Print Screen always cut a long page off at the fold. Two of these four platforms do have a real full page capture. The other two only have a workaround.
Take a normal screenshot with the side button and volume up.
Tap the preview thumbnail in the bottom-left corner before it disappears.
Switch from the Screen tab to the Full Page tab at the top.
Tap Done, then Save PDF to Files.
Worth knowing: iOS returns a PDF rather than an image, and the Full Page tab only appears in Safari. It will not show up for a page opened inside Chrome, Instagram, or another in-app browser.
Take a normal screenshot with power and volume down.
Tap Capture more on Pixel, or Scroll capture on Samsung, in the toolbar that appears.
Drag the crop handles down to extend the capture, then save.
Worth knowing: The button vanishes after a few seconds, and the capture stops wherever you release the handles rather than at the true end of the document.
Cmd + Shift + 3 and Cmd + Shift + 4 capture the screen, not the document, so they stop at the fold.
For the whole page, press Cmd + P, then open the PDF dropdown and choose Save as PDF.
For an image instead, use the Chrome or Safari developer route above.
Worth knowing: Print to PDF re-flows the page through print stylesheets, so backgrounds, sticky navigation, and dark themes frequently come out looking nothing like the live site.
Print Screen and the Snipping Tool are limited to what is on screen.
Press Ctrl + Shift + S in Edge and choose Capture full page.
In any browser, Ctrl + P with Microsoft Print to PDF saves the full document.
Worth knowing: Snipping Tool has no scroll capture at all, so outside of Edge there is no way to get a full-height image without a third-party tool.
Every route on this page produces a different file, at a different width, in a different format, with a different set of overlays baked in. Capturing from a hosted renderer removes all of that variance: you pin the viewport width, get a real PNG, JPG, or WebP rather than a print-styled PDF, and the same URL returns a comparable image every single time, from a phone or a laptop.
Each control in the tool maps directly to an API parameter, so anything you can do here you can also do programmatically.
The renderer captures the full document height rather than the visible window, so footers, long articles, and infinite feeds all land in a single image.
full_page=trueImages and components that only load as you scroll are forced to render before the capture, so you never get a page full of grey placeholders.
Capture at desktop, tablet, or mobile width to see exactly how a responsive layout stacks at each breakpoint.
viewport=mobilePNG for lossless UI work, JPG for smaller photo-heavy pages, WebP when you want the best size-to-quality ratio for the web.
file_type=webpConsent dialogs are dismissed before the capture, so a full-height screenshot is not ruined by an overlay sitting across the top of the page.
block_cookie_banners=trueAd slots are stripped before rendering, which also keeps the page height stable and stops layout shift from breaking the capture.
block_ads=trueTaking a screenshot with your operating system's built-in shortcut works for one visible window. It falls apart the moment the page is longer than the screen.
| Capability | Manual screenshot | ScreenshotAPI full page tool |
|---|---|---|
| Content below the fold | Only the visible window; you stitch the rest by hand | Entire document height in a single image |
| Lazy-loaded images | Often captured as empty placeholders | Scrolled and rendered before the capture |
| Sticky headers | Repeat on every stitched section | Handled once, at the top of the page |
| Cookie banners and ads | Captured along with the page | Removed before the render |
| Consistency across machines | Varies with screen size, zoom, and OS | Fixed viewport width, identical every run |
| Automation | Manual only, one page at a time | One HTTP request; scale to thousands of pages |
Common questions about capturing an entire web page, choosing a format, and automating the same capture through the API.
Don't see your question here?
Browse all help articles