OpenCapture › How-to › Full page screenshot in Chrome
Chrome is the only one of the three major desktop browsers with no full page screenshot anywhere in its interface. There is a command that does it, and it works — it is just in the developer tools, and it has four limits worth knowing before you rely on it.
If you would rather not open DevTools, OpenCapture, a free and open-source extension, takes a full page screenshot in Chrome from the toolbar and lets you crop and blur it before you save. That is method 2 below.
Nothing to install. This is the built-in way to take a Chrome full page screenshot: it captures the entire scroll height, not just the part on screen.
The other three are worth knowing while you are here. Capture area screenshot lets you drag a box over a region. Capture node screenshot photographs whichever element you have selected in the Elements panel, cropped exactly to its box — the fastest way to get a clean shot of one card or one table. Capture screenshot takes the visible viewport and nothing more.
Four limits of a Chrome full page screenshot taken this way, roughly in the order you will meet them.
There is no PDF option and no JPEG option. If you are archiving a page or sending something to someone who expects a document, you get an image and convert it yourself — and converting a very tall PNG to PDF usually re-introduces the page breaks you were trying to avoid. The two routes to a PDF, and why they produce different files, are in how to save a webpage as a PDF without page breaks.
Browsers cap how large a single canvas surface can be; on Chrome that is 32,767 pixels on any one dimension. Exceeding it raises no error — the canvas quietly stops working and you get a blank or cut-off image with nothing in the console. Documentation sites, long changelogs and social feeds reach that height more easily than you would expect. The mechanism is in how full-page screenshots work.
Images that load when they scroll into view need a moment. The capture scrolls faster than that, so it photographs the placeholder. The page looked complete while you were reading it because you scrolled at human speed.
What lands in your downloads folder is the raw page. Cropping the cookie banner off the top, circling the thing you are pointing at, or blurring an email address before you send it all happen somewhere else.
This is where OpenCapture fits. It is a full page screenshot extension for Chrome — also Edge and Firefox — it is free, and it needs no account.
Sticky headers and fixed sidebars are rendered once, where they belong, instead of marching down the finished image — which is the failure you are most likely to have seen from a tool that skips that step.
What to check before installing any Chrome screenshot extension — the permissions it asks for, where captures go, what is free — is set out on its own page.
Edge ships Web capture, with three modes and a pen, on Ctrl + Shift + S. Firefox puts Take Screenshot in the right-click menu. Chrome, the browser most people use, has neither, so a full page screenshot in Chrome means DevTools or an extension — which is why the full page screenshot extension category exists at all, and why it is as crowded as it is. The three built-ins side by side are in scrolling screenshots on desktop; the extensions are compared on alternatives.
In the DevTools Command Menu, not in any of Chrome’s own menus. Press F12 to open DevTools, then Ctrl + Shift + P to open the Command Menu, type screenshot, and pick Capture full size screenshot from the four capture commands that appear.
Yes. OpenCapture is a free full page screen capture extension (or plugin) for Chrome, Edge and Firefox: one click scrolls the page, stitches it into one image and opens it in the editor, with nothing uploaded.
Not with anything built in: Chrome’s menus have no full-page capture. The options are the DevTools command above or an extension, such as OpenCapture, which also crops, blurs and exports PDF.
A browser caps how large a single canvas surface can be — on Chrome, 32,767 pixels on any one dimension. Past that the capture comes back truncated or blank, and nothing appears in the console to explain it. A page that long has to be captured in segments or written out as a multi-page PDF.
Images that load only when they scroll into view need a moment to arrive. A capture that scrolls and photographs without pausing gets the placeholder instead of the picture, which is why a page that looked fine while you were reading it can come back full of grey boxes.