Snow ShotHow to Screenshot a Whole Web Page in Chrome, Edge and Firefox
A web page is taller than your screen, so a normal screenshot always cuts it off. Every major browser can capture the whole page — the trick is knowing which method gives you a clean image rather than a stitched mess. Here is how to screenshot an entire web page in Chrome, Edge and Firefox, plus the cases where the built-in tools fall short.
Chrome: DevTools full-size capture
Open DevTools with F12, then Ctrl + Shift + P for the command menu and type "Capture full size screenshot". Chrome resizes the viewport to the full document height, renders it, and saves a PNG. This is the cleanest built-in method because the browser re-renders instead of scrolling — no sticky headers repeated down the image.
Edge: the same command, plus web capture
Edge is Chromium underneath, so the DevTools command works identically. Edge also has a Web Capture panel (Ctrl + Shift + S) with a "Full page" option, which is friendlier but flattens the image at screen resolution. Use DevTools when you need maximum quality, Web Capture when you need speed.
Firefox: the built-in screenshot tool
Firefox's screenshot tool lives in the address bar under "Take Screenshot", or via Right-click → Take Screenshot. Choose "Save full page". Firefox captures lazily-loaded sections correctly in most cases, which Chromium's DevTools sometimes misses on infinite-scroll pages.
Why lazy-loaded pages break the capture
Images and sections that only load when scrolled into view will be blank in a full-page capture, because the browser renders the tall viewport once. Fix it before capturing: scroll to the bottom of the page slowly, wait for everything to load, scroll back to the top, then capture. On very long feeds, capture in two halves instead.
Sticky headers, cookie banners and chat widgets
These elements are positioned relative to the viewport, so in a full-page capture they appear once at the top (DevTools) or repeat on every stitched segment (scroll-and-stitch tools). Hide them first with a CSS rule in DevTools, or accept the repetition and crop afterwards.
When you are not capturing a web page
Browser tools only work inside a browser. For a desktop app, a PDF viewer, an Excel sheet or a chat client, you need an OS-level scrolling capture. Snow Shot does this: select a region, click the scrolling-capture action, and the tool scrolls the window for you, stitching the frames and stopping when the content repeats.
Quality checklist before you save
Capture at 100% zoom — 80% zoom produces smaller text that looks fine on screen and blurry in the file. Prefer PNG for text-heavy pages; JPEG artefacts destroy thin fonts. If the page is wider than 1920 px, capture at the browser's full width rather than scaling down afterwards.
Frequently asked
Can I capture a page that requires a login? Yes — the browser captures what is rendered, logged-in state included, as long as you do not capture personal data you should not be storing. Does the method work on mobile pages? Use the device toolbar in DevTools to emulate a phone, then capture full size.
Capturing pages that lazy-load as you scroll
Infinite feeds and image galleries load content only when it enters the viewport. A full-page capture renders once, so anything below the initial render is blank. Workaround: scroll to the bottom in steps, waiting a second at each stop, then scroll back and capture. Alternatively use Firefox's screenshot tool, which handles lazy loading more gracefully than Chromium's DevTools in practice.
Saving and sharing long images
A full-page capture of a long article can be 10,000 px tall. PNG keeps text sharp but the file may be several megabytes; JPEG shrinks it at the cost of text clarity. Many chat apps downscale tall images until the text is unreadable — for sharing, split the capture into screen-height slices, or send the PNG as a file rather than a photo.
Scrolling capture on macOS
macOS has no built-in full-page browser capture outside Safari's developer menu, and Preview cannot stitch a scroll. Third-party tools handle it: select the region, start the capture, and let the tool scroll the window while stitching frames. The same rules apply as on Windows — hide sticky headers, let content load, capture at 100% zoom.
Common mistakes that waste a capture
Three habits cause most bad full-page screenshots. Capturing before the page finishes loading, which leaves grey placeholders. Capturing at a browser zoom other than 100%, which produces text that looks fine on screen and soft in the file. And cropping the result afterwards instead of hiding the sticky element first — cropping a stitched image usually cuts through the middle of a paragraph.
Automating the routine
If you capture the same dashboard or report every week, bind a single hotkey that opens the capture, selects the window and saves to a dated folder. Ten seconds saved per capture is the entire value of a dedicated tool over a browser command you have to remember.
Want the condensed version? Read the full scrolling screenshot guide.