Full page screenshot extension · Chrome & Firefox
Most full-page tools scroll, photograph each screenful, and glue the pieces together. Uncut renders the entire page in a single pass, so there is nothing to glue and nothing to tear.
Free. No account, no sign-up, nothing leaves your computer.
The problem
Scroll-and-stitch tools take a picture, scroll, take another, and paste. Between two frames the page keeps living. A carousel advances, a sticky header re-pins, a lazy image finally loads, a counter ticks. The result is a hairline where the halves no longer agree.
Frame two lands 14 px off and repeats 3 px. Real pixels, same page.
One frame. There is no join, so there is nothing to misalign.
How it works
No tool wins on every page. Uncut ships both approaches and tells you honestly what each one costs, instead of choosing badly on your behalf.
Draws the entire page off-screen in a single pass through the DevTools Protocol. Nothing is scrolled, so nothing can move between frames. Sharper text and no seams, at any page height.
The classic method: photograph each screenful while scrolling, then join them. Uncut freezes sticky headers and parallax first, so the joins land where they should.
What you get
PNG for fidelity, JPEG for size, PDF for sharing, SVG when you want the image wrapped in something scalable.
A very tall capture gets shrunk to fit your screen, which softens text and reads as blurry. One click shows actual pixels so you can judge the real thing.
Capturing means briefly changing the page: freezing sticky bars, pausing effects. Every one of those changes is undone when the capture ends.
Browsers cap how tall an image can be, and they fail quietly. You get a correct-looking file with the bottom missing. Uncut checks, and tells you.
About a thousand lines of plain JavaScript across six files. Nothing bundled in, nothing to audit but the thing itself.
Install it and press the button. There is nothing to sign up for, because there is no server on the other end.
Privacy
Uncut contains zero network calls. Not analytics, not crash reporting, not a licence check. Your screenshot is made on your machine and stays there until you save it.
Read the full policyWhat's next
A Pro tier is coming for the work that takes real effort: scheduled captures, batch URLs, annotation. Tell us where to send one email when it lands. That is the only email you will get.
Questions
Because it is, in the narrow technical sense. The one-pass engine uses the DevTools Protocol, the same channel DevTools itself uses, and Chrome warns you any time an extension opens it. That warning is a good thing: it means you can always see when an extension has that level of access. Uncut attaches when you click capture and detaches when the image is ready. If you would rather never see it, use Scroll & stitch.
Most often another debugger already holds the tab. DevTools being open is the usual culprit, since Chrome allows only one per tab. Close DevTools and try again. Chrome's internal pages and the Web Store are off-limits to every extension, and always will be.
Yes, and it is the browser's, not ours. Past a certain pixel area a render comes back correctly sized with the overflow simply not drawn, silent, and easy to miss. Uncut checks for exactly that and says so instead of handing you a quietly broken file.
Scroll & stitch does. One render does not, and cannot, because Firefox gives extensions no equivalent of the DevTools Protocol. The Firefox build ships with the fallback engine and says so in the popup rather than offering a button that fails.
Don't take it on faith. The extension has no network code in it at all, which is a thing you can check yourself. Unpack the extension folder and search it. Six files, no bundler, no minification, nothing hidden.