Concepts 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.

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 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.