No repeated sticky headers
Fixed and sticky page chrome is handled for the length of a multi-section capture, then put back exactly as it was. Drag to compare it with scrolling and stitching by hand.
Free and open sourceMIT
Full page screenshot extension for Chrome, Firefox and Edge
Full-page screenshot extension. No repeats.
No repeated sticky headers, even when a page exceeds one browser canvas. PageShotter waits for lazy-loaded content, then lets you edit and export locally as an image or PDF. Nothing is uploaded unless you send it.
Watch the tour0:55 · sound on
Page, area or element
PNG, JPEG, PDF
No account
Nothing uploaded
Demo
Capture
Capturing
Full page0 / 12 sections
Measuring the page1440 × 0 px
Nothing leaves this browser
Pick a mode in the popup to run it
Drawn from the product's own parts, not a recording
16,918pxThe tallest documentation page in the test set, assembled into one 12-section result.
47sectionsPlanned across a single long Wikipedia article, each one measured before it is taken.
146/ 150Acceptance scenarios passing today. The four open ones need a recheck, not a fix.
3permissionsActive tab, scripting and the right-click menu. No site access at install and no browsing history.
0uploadsNetwork requests made while capturing. A capture leaves your browser only if you send it to Gmail.
The 55-second tour
Watch a whole page come together.
Capture, annotate, save as a PDF, find it again. Everything PageShotter does, in under a minute. The narration is written on screen, so it plays muted; turn the sound on to hear it.
That was PageShotter
One click, careful capture
Simple to use. Deliberate underneath.
Start the capture and keep the source tab active. Everything after that happens locally in Chrome. Keep scrolling and this page runs one.
- 01
Move through the page
PageShotter measures the full height, then advances through each visible section in turn.
- 02
Wait for nearby content
Lazy images and a shifting page height get a bounded chance to finish before the shutter fires.
- 03
Assemble the result
Sections are aligned into one full-resolution preview, ready to edit, copy or export.
- 04
Put the page back
Temporary style changes are reverted and you land at the scroll position you started from.
Built for real webpages
The difficult parts are the point.
PageShotter goes after the pages that make ordinary scrolling screenshots unreliable, then gives the finished capture to a focused editor when it needs explanation.
Long pages as one result
Moves through the page in measured sections and joins them. Pages too tall for a single browser canvas are captured in tiles, so one-canvas height stops being the limit.
Lazy-loaded sections
Gives nearby images and changing content a bounded chance to settle before each section is taken.
Real app layouts
Finds the scroller on pages whose content moves inside a dashboard, an admin tool or a signed-in app rather than the document itself.
Focused by design
Capture first. Edit when useful.
Open the page, capture it, then save the result as-is or annotate it in the local editor. No account setup or upload step in between. Try the tools below.
Everything around the capture
A small tool with no loose ends.
Every mode, format and limit, shown working rather than listed. Each card below runs on its own; the capture modes answer to a click.
Full page, visible area, or a selection
Drag any region, or hold Ctrl and click to capture a single element with its boundary found for you. See scrolling screenshots.
PNG, JPEG, clipboard and PDF
Save an image or convert the screenshot to PDF. A direct capture PDF can keep supported links clickable and text searchable in Latin scripts. You can also save a webpage as PDF.
Capture from the right-click menu
Right-click any page for the full page, the visible part or a region. Settings turns the menu off.
A whole list of pages
Paste addresses or tick open tabs, and each page saves as its own full-page screenshot, with a report and a Retry for failures. Your browser asks for access to all websites the first time. See batch screenshots.
Send to Gmail
A new Gmail message opens with the screenshot attached, in the format you picked. You write it and press Send. Your browser asks for mail.google.com access the first time, and files over 25 MB are refused.
Edit screenshots locally
Crop, add text, arrows and shapes, highlight details or blur an area. See the screenshot editor.
History on your own machine
Reopen or re-export a recent capture, and find it by a word that was on the page, not only by the title the tab happened to carry.
Your existing browser session
Capture pages you are already allowed to view, including many signed-in tools. See full-page screenshots.
Three permissions, and more only if you ask
Active tab, scripting and the right-click menu. No site access at install, no browsing history, no account. Saving into a folder, batch capture and Send to Gmail each ask for their own access, the first time you use them.
Limits stated up front
A capture stops after 200 sections and reports deeper pages as truncated. A result over 65,535 px cannot be one PNG or JPEG, but PDF can still export the captured depth. Searchable PDF text covers Latin scripts.
Capture the page you have open right now.
Free, local, and done in one click.
Evidence, not promises
Tested on pages built to expose capture failures.
The acceptance set uses self-announcing pages, where a skipped section, a repeated header, a bad seam or a wrong limit is visible in the result itself rather than something you have to pixel-peep.
The four open rows are not known failures. The code behind them changed after they passed and they have not been run again since, so they are recorded as needing a recheck rather than counted as passes. Browser behaviour also varies between versions and machines, so review anything that matters.
146/150
scenarios
passing today
passing today
PassingNeeds a recheck
Long pagesLazy contentFixed headersNested scrollersLive app layoutsElement selectionPDF text layerPDF links
Private by default
Your capture stays on your device.
Every step between the page and the file happens inside your browser. There is no server in the loop to trust.
Screenshot pixels and page contents are processed locally by the extension. Recent captures are kept in your own browser for as long as you choose, and the extension makes no network requests of its own.
PageShotter works only with pages you are already allowed to view. It does not bypass authentication, paywalls or access controls.
| Stored | For how long |
|---|---|
| The screenshot and a thumbnail | Until your retention setting, or you delete it |
| The page title and address | With its capture |
| The page's words and link positions | With its capture |
| Your settings | Until you change them |
Open source
Don’t take our word for it. Read the code.
Every claim on this page, from the permissions to the zero network requests, can be checked line by line. The extension’s code is public on GitHub under the MIT License.
activeTab + scripting + contextMenus
Three permissions. Check the manifest.
No host access at install, no tabs, no debugger. Downloads, all-sites and Gmail access are optional, asked for only when you use them.
npm ci && npm run buildBuild it yourself.
Load the result unpacked in Chrome: the same code the store version is built from.
Issues welcomeFound a page it gets wrong?
Open an issue with the page’s address. Every recurring failure becomes a test fixture.
Free for Chrome, Firefox and Edge
PageShotter is live
Free screenshots for Chrome, Firefox and Edge: a full page, the visible area, any element, or many pages at once. Nothing is uploaded and no account is required.
Chrome and Edge 120+ · Firefox 153+ on desktop · No account · Nothing uploaded · Open source