How to Take a Full Page Screenshot in Chrome

You need to show someone a page. Not a piece of it — the page. The hero, the three sections under it, the pricing table, the footer, in order, the way it actually renders. So you press your screenshot key, and you get back the top 900 pixels and nothing else.

Then you do what everyone does: scroll, capture, scroll, capture, four more times, and paste the results in a row. And now the person you sent it to is looking at four images with the navigation bar repeated in three of them, a heading sliced in half across two, and no reliable sense of what came between them. There are better ways to do this — one of them is already inside Chrome and most people have never opened it.

Why Chrome's screenshot stops at the fold

This is not a bug, and it is worth understanding because it explains why every workaround works the way it does.

Your operating system's screenshot tool photographs the screen. It has no idea what a webpage is; it captures pixels that are currently being displayed. Chrome's own capture API works on the same principle — it grabs the visible tab, meaning the viewport, meaning whatever fits between the top and bottom edges of the window right now. Everything below the fold has not been painted to the screen, so there is nothing there to photograph.

Getting the whole page therefore always requires the same trick: scroll the page in stages, capture at each stage, and join the pieces afterwards. Every tool below is a different answer to who does the scrolling and joining, and where.

Method 1: Chrome DevTools, with nothing installed

Chrome has shipped a full-page screenshot command for years. It lives in DevTools, which is why most people never find it.

1. Open the page, then press F12 (or Ctrl+Shift+I, Cmd+Option+I on macOS) to open DevTools.
2. Press Ctrl+Shift+P (Cmd+Shift+P) to open the command menu.
3. Type screenshot.
4. Choose Capture full size screenshot.

Chrome renders the entire document and drops a PNG in your downloads folder. The same command is available from the device-toolbar menu, which Google documents in the Chrome DevTools device mode guide.

Where DevTools falls short

For a straightforward article or marketing page, that four-step method is often all you need. It stops being enough in a few specific, very common situations:

• Lazy-loaded content. Images and sections that only load as you scroll may never load at all, because DevTools renders the document rather than scrolling through it like a person. You get grey boxes where the screenshots should be.
• Very long pages. Full-size capture has practical limits, and a page that scrolls for dozens of screens can come back truncated or blank.
• Sticky headers and floating elements. A fixed navigation bar or a cookie banner sometimes lands in the middle of the image, or repeats.
• The four-step tax. Open DevTools, open the command menu, type, choose — every single time. If you take three screenshots a week, fine. If you take twenty a day, it is friction you will feel.

It is also worth knowing that other browsers made this easier. Firefox has Take Screenshot in the right-click menu with a Save full page option, and Edge has Web capture with a full-page mode. Chrome, oddly, is the one that buried it.

Method 2: An extension that scrolls and stitches

The other approach is to do what a person would do, automatically: scroll the real page in the real browser, capture each section as it comes into view, and join the sections into one image. Because the page genuinely scrolls, lazy-loaded content loads, and because it is your browser, anything you can see is capturable — including staging sites and dashboards behind a login.

That is the job ShotDock does. Press Alt+Shift+S on any page and it scrolls, captures, and stitches the whole thing into a single PNG or JPG, then hands it to you three ways: copied to the clipboard, saved to your downloads folder, or opened in a new tab. Alt+Shift+V captures just the visible area for the times when the viewport is the point — an open dropdown, a hover state, an error message that would vanish the moment the page moved.

Two details matter more than the feature list. The first is that the stitching overlaps each capture with the one before it and aligns them on that overlap, so the joins land where they belong instead of leaving a visible band through the middle of a paragraph. The second is that sticky headers are accounted for while it scrolls, so a fixed navigation bar appears once, at the top, rather than stamping itself down the image every few hundred pixels.

None of it leaves your machine. There is no account, no upload, no watermark, and the extension requests no host permissions at all — no "read and change your data on all websites" prompt on install, which is the permission most screenshot extensions ask for up front. It is free on the Chrome Web Store and open source under the MIT licence.

What to look for in any screenshot extension

If you evaluate a different one, these are the questions worth asking — they are where most of them quietly fall down:

• Does it capture locally, or upload the page? Many "online screenshot" tools render your URL on their server. That cannot work for anything private, and it means a copy of the page exists somewhere you do not control.
• What permissions does it request? Broad host access on every site is a large amount of trust for a tool you use occasionally.
• How does it handle sticky headers? Take one capture of a site with a fixed navbar. You will know within a second.
• Is there a watermark? Some free tiers stamp the output, which makes the screenshot useless for client work.
• Can you cancel a capture? On a very long page, starting one on the wrong tab should not mean waiting it out or reloading.

Method 3: Online screenshot services

Paste a URL into a website, get an image back. These have a real place: they run without installing anything, and they are the only option if you need a screenshot of a page from a machine that is not yours.

They are also the wrong tool for most day-to-day work. The service loads the page from its network, not yours — so a staging URL, an internal tool, a localhost port, or anything behind a login is simply unreachable. And the page you asked about is now a request in someone else's logs. For a public marketing page, that is nothing. For an unreleased design or a customer's dashboard, it is a decision you should make deliberately rather than by default.

PNG or JPG for a full-page capture?

Both formats are offered by almost every tool, and for tall captures the choice actually matters.

PNG is lossless, so text stays crisp, thin borders stay exactly one pixel, and nothing gets the soft halo that lossy compression leaves around high-contrast edges. For anything with interface detail — documentation, bug reports, design reviews, anything a reader will zoom into — PNG is the right answer.

JPG is lossy and dramatically smaller. A page that scrolls for twenty screens produces a genuinely large PNG, and email clients, ticketing systems, and chat tools all have attachment limits. When the capture is mostly photography, or when it simply has to travel, JPG earns its place. MDN's image file type guide is a good reference if you want the underlying detail.

A reasonable default: PNG for anything you will archive or annotate, JPG for anything you are about to attach to a message.

Five things that make a long-page capture come out clean

1. Scroll to the bottom first. This forces lazy-loaded images and sections to load. Then scroll back to the top and capture. It is the single highest-value habit on this list.
2. Dismiss the overlays. Cookie banners, newsletter modals, chat widgets, and "subscribe" slide-ins all get captured. Close them before, not after.
3. Close the sidebar in DevTools. If you use the DevTools method, an open drawer changes the rendered viewport width and the capture with it.
4. Pick your window width on purpose. A full-page screenshot records the layout at whatever width the window happens to be. If you are documenting a responsive breakpoint, set the width deliberately — DevTools device mode is good for this.
5. Wait for animation to settle. Sections that fade or slide in on scroll can be captured mid-animation, leaving half-transparent blocks. Give the page a moment before you start.

Frequently asked questions

Can I take a full page screenshot without installing anything?

Yes — the DevTools command menu method above needs nothing installed and works in any Chrome. It is the right choice for occasional captures of simple pages. An extension is worth it when you take screenshots often, when the pages lazy-load, or when four steps every time has started to annoy you.

Why does my screenshot repeat the navigation bar?

Because the bar is position: fixed or position: sticky — it stays pinned to the top of the viewport while everything else scrolls. A tool that captures at fixed intervals without accounting for that photographs the bar in every single capture, and the joined image shows it over and over. Handling sticky elements during capture is the fix; it is not something you can correct afterwards without cropping by hand.

Why is half of my screenshot blank or grey?

Almost always lazy loading. The page never rendered that content because nothing ever scrolled past it. Scroll to the bottom of the page yourself, wait for everything to appear, scroll back to the top, and capture again.

Does a full-page screenshot capture content inside a scrollable box?

No — and this catches people out. If a table or a code block has its own inner scrollbar, the capture records that box exactly as it appears on screen, showing only the visible portion. Nothing scrolls it but you. Scroll the inner box to the part you need before capturing, or capture it separately.

Can I capture a page I have to log into?

With a browser-based tool, yes: it captures the page in your session, so it sees precisely what you see. Server-side screenshot services cannot, since they load the URL as an anonymous visitor with none of your cookies.

The takeaway

A viewport-sized crop is not a picture of a page — it is a picture of the top of a page, and everyone who receives one has to take your word for the rest. Chrome can do better than that today, through a DevTools command most people have never run, and better still with a tool that scrolls the page properly, aligns the seams, and puts the finished image on your clipboard in one keystroke.

If you want that second version, ShotDock is free, local, and about ninety seconds from installed to first capture. It sits alongside the rest of our browser extensions — small, single-purpose tools that do one job and stay out of the way. If the reason you have too many screenshots is that you also have too many tabs open, exporting and saving all your open tabs is the companion habit worth picking up next.