One capture, not a scrolled strip glued together
Free, PNG or JPEG, 1x or 2x, straight to your downloads.
Almost every full-page screenshot tool scrolls down the page taking pictures and glues them together. That approach has three failure modes you will recognize: the sticky header appears four times, lazy-loaded images arrive late and show up half drawn, and the joins are visible if you look.
This captures the page as a single image instead, so none of those happen. It also nudges lazy-loaded images to load before capturing, which is the other half of the problem and the half people forget.
The short version
Full Page Screenshot takes the whole page in a single capture, so there is no seam and no repeated header.
- Capture the whole page in one shot, with no repeated sticky header and no seam where two screenshots met.
- Choose PNG or JPEG at 1x or 2x and have it land in your downloads folder.
- Get the lazy-loaded images, because the page is captured properly rather than photographed in strips.
Best for: anyone sending a client a full page for review, or filing a bug with proof.
Replaces: the scroll-and-stitch extensions that duplicate your header four times down the image.
How to use it
- Open the page.
- Click the icon and pick full page, the visible area, or a region.
- Choose PNG or JPEG, and 1x or 2x if you want it retina.
- It saves to your downloads folder.
What it can access, and why
| Permission | Why it needs it |
|---|---|
| Reads the current tab | Only when you click the icon. |
| Chrome's debugger interface | This is the only way to capture a full page as one image. It attaches for the moment of capture and detaches straight after. |
| Runs a script on the page | To trigger lazy-loaded images so they are not half drawn in the capture. |
| Downloads | To save the file. |
Full detail in the privacy policy.
The things people ask before installing
Why does Chrome show a banner while it runs? The single-shot capture lives behind Chrome's debugger interface and there is no other route to it. The banner appears while the capture happens and goes when it finishes. I would rather explain the banner than ship the stitched version.
Is the image uploaded anywhere? It goes from the page to your downloads folder. It does not pass through a server, and there is no share link, no gallery and no account.
Does it cost anything after so many captures? There is no counter. Take ten thousand.
Free, and it stays free. No account, no sign-up, and nothing leaves your browser.
FAQ
Why does Chrome say it is being debugged?
Because it genuinely is, for a second or two. The full-page capture interface lives behind Chrome's debugger protocol and there is no other route to it, so the banner appears while the capture happens and goes when it detaches. I would rather you saw the banner and knew why than had it hidden.
Can it capture a very long page?
Yes, though a genuinely enormous page can run into browser memory limits, and at 2x scale that arrives sooner. If a capture comes back blank on a huge page, drop to 1x and it will usually go through.
Does it capture fixed headers correctly?
Yes, once. That is the main thing it does better than a stitching tool, which repeats the header at every scroll boundary.
Is anything uploaded?
No. The capture happens on your machine and the file goes to your downloads folder. There is no server and no network code.