OpenCapture › Blog
BlogNotes on capturing web pages
How full-page capture works underneath, where it goes wrong, and how to get a screenshot that does its job — in a bug report, in a document, or in something you are about to share more widely than you think.
How full-page screenshots actually work — and the four ways they break
Capture scrolls, photographs each viewport and stitches the slices. Sticky headers repeat, lazy images arrive late, inner scroll regions never move, and device-pixel rounding leaves hairlines. Plus a one-minute test for any tool.
Your browser already takes full-page screenshots. When do you actually need an extension?
How to capture a full page in Chrome, Firefox and Edge with nothing installed — and the four things the built-in features do not do at all.
The screenshot that gets your bug fixed, and the one that gets it closed
A useful bug screenshot answers what you saw, where you were and what state the page was in. A cropped viewport answers only the first.
Blurring sensitive information in a screenshot — and when it is not enough
Blur averages pixels rather than removing them, so short predictable text can often be recovered. What needs a solid block instead, and what people forget to blur.
What permissions a screenshot extension asks for, and what they actually let it do
Why most screenshot tools ask to read and change data on all websites, what activeTab grants instead, and how to check a listing before you install.