Articles

On a Retina or high-DPI screen, the browser uses a devicePixelRatio greater than 1 (typically 2). This means every CSS pixel maps to multiple physical pixels, so a 1440px wide window produces a 2880px wide capture. The resulting image has double the linear resolution, four times the total pixels, and significantly larger file sizes. This higher resolution halves the maximum page height you can capture before hitting Chrome's 16,384px canvas limit.

An infinite scroll page has no total height, so there is no complete version to capture. Scroll to the point you want the capture to end, wait for loading to stop, then start. You will get everything currently in the document, which is the only well-defined answer available.

On iPhone and iPad, take a screenshot, tap the thumbnail, and choose the Full Page tab to save the whole webpage as a PDF. Safari on macOS has no equivalent: it ships no full page screenshot command, so the built-in route there is Command+P and Save as PDF, which prints the page rather than photographing it.

To take an edge full page screenshot, press Ctrl+Shift+S to open Web Capture and select "Capture full page." Alternatively, use DevTools (F12) and run the command "Capture full size screenshot" via Ctrl+Shift+P. Because Edge is Chromium-based, you can also install extensions like Full Page Screenshot from the Chrome Web Store for more reliable results.

To capture a page behind a login, you must use a local browser extension or built-in tool that runs within your active browsing session. Remote rendering services cannot authenticate because they lack your cookies and credentials. Local capture ensures data never leaves your machine, but be aware that sensitive session tokens may appear in the final image if visible on screen.

A full page screenshot cut off at the bottom is almost always the browser image size limit being hit without being handled: past roughly 16,384 pixels the draw fails and you are handed an image that looks complete but is not. The other four causes are lazy content, infinite scroll, a nested scrolling panel, and the tab losing focus mid-capture.

Any element visible on the screen becomes part of the image. To remove a cookie banner or popup, you must dismiss it manually before triggering the capture. If the banner reappears during a long scroll, disable automatic scrolling or delete the element directly in Chrome DevTools using the Elements panel before taking the shot.

Images that load only when scrolled into view have not finished downloading and decoding by the time a fast capture passes them, so they are photographed as empty placeholders. Scrolling the page to the bottom once before capturing forces every image to request, which fixes it in nearly every case.

For webpage captures, PNG is the superior image format because it uses lossless compression that preserves sharp text, thin borders, and flat colours without introducing visual noise. JPG should be avoided for UI elements as its lossy compression creates visible artefacts around hard edges. If the goal is to share the page as a document rather than an image, use PDF, which Full Page Screenshot supports via A4, Letter, or fit-to-image exports.

Chrome's Capture full size screenshot lives in the DevTools command menu: press F12, then Ctrl+Shift+P, then type the command. It works well on static pages. It does not neutralise sticky headers, does not wait for lazy images, cannot capture nested scroll containers, and truncates rather than splits past the image size limit.

A full page capture of a long site at 2x display density routinely produces a 40 to 80 MB PNG, which exceeds the upload limit of most issue trackers and chat tools. The four fixes, in order of how much they cost you: export JPG instead, export PDF, zoom out before capturing, or crop to the part that matters.

To properly hide personal data in a screenshot, you must use destructive redaction, not just a blur or black overlay. Blurs and rectangles leave the original pixels intact and recoverable. True redaction removes the pixel data entirely. You should perform this step using a dedicated editor like Full Page Screenshot's built-in tools before saving or sharing the file.

Firefox captures a whole page natively: right-click an empty part of the page and choose Take Screenshot, or press Ctrl+Shift+S, then click Save full page. The preview offers Copy and Download only, with no editing tools, and very long or lazy-loading pages remain the cases where it falls short.

To archive a webpage permanently, you must combine two distinct methods. First, use a capture tool like Full Page Screenshot to save an exact visual replica of your current view, including any logged-in content or dynamic state. Second, submit the URL to the Internet Archive's Wayback Machine via Save Page Now to get an independent third-party timestamp. A personal screenshot alone carries no external proof of time.

A sticky or fixed header sits in the viewport at every scroll position, so it appears in every individual capture and ends up stamped down the joined image. The fix is to neutralise fixed and sticky positioning for the duration of the capture, which puts the header back in the document flow where it appears exactly once.

If your website screenshot captures in dark mode when you expected light mode (or vice versa), it is because the site respects the operating system's `prefers-color-scheme` media query rather than its own default styling. The browser injects the current OS theme setting into the page context during rendering. To fix this, you must temporarily change your OS display settings or use a browser profile configured for the desired theme before triggering the capture.

If a capture returns exactly one screenful, the page body probably does not scroll at all. Application layouts commonly pin the body to the viewport height and put the scrollbar on an inner element, so scrolling the window does nothing. The capture has to detect that element and scroll it instead.

A normal screenshot captures the visible window. A scrolling screenshot describes the method: scroll, photograph each screenful, join them. A full page screenshot describes the result: one image containing the entire document. On desktop the last two usually mean the same thing, because scrolling is how a full page capture is produced.