Full page
Scrolls, captures and stitches the entire document — seam-free, even at 40,000 pixels tall. Alt+Shift+P
Four ways to capture
Every mode ends in the same place: a pixel-perfect image and a local editor.
Visible area
Exactly what's on screen, exactly once. The quick one. Alt+Shift+V
Select area
Drag a marquee anywhere on the page. A live size label shows the crop before you commit.
Select element
Hover to highlight any element; arrow keys walk up and down the DOM to widen or narrow the shot.
An editor, not an upload form
Crop, arrows, rectangles, text, highlight, freehand pen and pixelating blur — with 100 levels of undo. Opens instantly in a local tab.
Export anywhere
PNG for fidelity, JPG for weight, PDF for sharing, or straight to the clipboard for pasting into chat, docs and issues.
Delay timer
Arm a 3–10 second countdown, open that hover menu or dropdown, and let the capture fire on its own.
The boring parts, done right
Full-page capture fails in a dozen quiet ways. Pagerama's engine was built around each one.
| The page does this | Pagerama does this |
|---|---|
| Sticky header repeats on every screen | Un-sticks it during capture — it appears exactly once, where it lives |
| Cookie bars & chat bubbles burn into every tile | Hidden after the first screen, restored the instant capture ends |
| Images lazy-load only when scrolled into view | A time-boxed pre-scroll wakes them up before capture begins |
| The app scrolls in an inner pane, not the document | Detects the real scroller and captures its full height |
| Browser zoom / HiDPI misaligns tiles | Pixel ratio is measured from the first tile, never assumed |
| Infinite feed grows forever | Capture is bounded and de-duplicated — it always terminates |
| You cancel halfway | Scroll position, styles and hidden elements are restored — always |
Privacy isn't a setting.
It's the architecture.
Pagerama has no backend. Captures are stitched in your browser, stored in
your browser and deleted by your browser. The extension requests four narrow
permissions and not one of them is «read your browsing history».
activeTabcapture only after you click — no standing access to any sitescriptinginject the measuring script into the one tab you're capturingstorageremember your settings, locallyclipboardWritethe “Copy” button
Don't take our word for it — open DevTools on this very page.
Network: 2 files, both from this site. Cookies: 0.
Questions
Is it really free?
Yes. Capture, editing and export are free, local and unlimited. If we ever add paid extras, they'll be workflow features — the core will stay free and offline.
Where are my screenshots stored?
In your browser's local storage (IndexedDB), on your machine. Pagerama keeps the last 10 captures so the editor can reopen them; exporting saves a normal file wherever you choose.
Why can't it capture the Chrome Web Store or chrome:// pages?
Chrome forbids all extensions from reading its own pages. Pagerama tells you instead of failing silently.
Does it work on very long pages?
Yes — that's the whole point. Pages are captured in tiles and stitched. Beyond roughly 40 megapixels the image is proportionally scaled to keep memory in check, and you're told when that happens.
What data do you collect?
None. No analytics, no crash reporting, no “anonymous usage statistics”. The extension makes zero network requests.
Put it on your toolbar
Free · no account · 30-second install
Add Pagerama to ChromeFree on the Chrome Web Store. No account, no sign-in.