Home / Guides / When capture fails
Troubleshooting
Full page screenshot not working in Chrome: nine causes, in order
"Full page screenshot not working" almost never means the extension is broken. It usually means the page is doing one of about nine specific things that defeat scroll-and-stitch capture, and each of them has a recognisable signature in the image you got back. Find your symptom below; the cause and the fix are underneath it.
Find your symptom
| What you got | What is actually happening |
|---|---|
| Blank or grey strips lower down | Lazy loading, capture outran the images |
| Navigation bar repeating every few hundred pixels | A sticky or fixed header |
| Only one screenful, on a dashboard or mail client | The document does not scroll, an inner pane does |
| Nothing happens at all when you click | A page Chrome forbids extensions from reading |
| Visible seams, or content duplicated at a join | Scroll animation, or the page moved mid-capture |
| Capture fails or truncates on a very long page | The browser's maximum canvas size |
| A cookie banner or chat bubble in every frame | Fixed overlays, same cause as sticky headers |
| Wrong colours, or a dark page captured light | Theme and print stylesheet mismatches |
| Worked yesterday, fails today, on every page | The extension itself, or a conflicting one |
1. Blank strips: the page lazy-loads
Most modern sites do not load images until they are about to enter the viewport. A capture that scrolls faster than the network can respond photographs the placeholder instead of the picture, and you get grey or white bands where the images should be — usually starting a screen or two below the fold and getting worse further down.
Fix: scroll to the very bottom of the page yourself, slowly enough that everything renders, wait a second, then scroll back to the top and capture. The images are now in memory and the capture cannot outrun them. On a very image-heavy page, do it twice.
Chrome's built-in DevTools "Capture full size screenshot" is the worst tool for this specific problem, because it renders the full document height in one pass without ever scrolling the page. Anything waiting on a scroll event to load will simply never load.
2. The navigation bar repeats down the image
This is the single most common complaint about full page screenshots, and
the cause is structural rather than a bug. A header with
position: sticky or position: fixed stays glued to
the top of the viewport while the page scrolls underneath it. A capture
tool takes one photograph per screenful, so the header is in every single
one of them, and stitching those together stripes it down your image at
regular intervals.
Two ways to fix it. Tools generally either hide the pinned element before capturing, or exclude the band of pixels it occupies from every frame after the first. Hiding is fragile — it depends on correctly identifying the element, and pages that re-pin it on scroll defeat it. Excluding the pixel band does not depend on the page cooperating, which is the approach this extension takes: it measures the pinned band once, and never sources those pixels from a later frame.
Manual workaround with any tool: open DevTools, select the header in the Elements panel, press Delete to remove it from the document, then capture. Reload afterwards to get it back.
3. You only get one screenful
Open the page and try scrolling with the keyboard's Page Down after clicking on the background rather than inside the content. If the page does not move, the document is pinned to the viewport height and a container inside it is doing the scrolling. This is how nearly every app shell is built: mail clients, admin dashboards, chat apps, project boards, social feeds.
A capture tool that walks document.scrollingElement finds
nothing to scroll here, takes one photograph, and reports success. Nothing
errored, which is why this one is so confusing.
Fix: use a tool that finds the element which actually scrolls and walks that instead. Failing that, three workarounds that work anywhere: zoom the browser out to 50% or 33% so more fits in one screenful before capturing; use DevTools device emulation to set a very tall viewport; or capture the pane in sections and join them.
4. Clicking the icon does nothing
Chrome blocks every extension from reading certain pages, as a security boundary rather than a policy any extension can opt out of:
- The Chrome Web Store itself
chrome://pages — Settings, Extensions, History, Downloads, Flags- The New Tab page
- Other extensions' pages (
chrome-extension://) - PDF files opened in Chrome's built-in viewer
- Local files, unless you have explicitly granted file URL access at
chrome://extensions
Fix: there is none, for any extension. Use Chrome's own DevTools screenshot command, or your operating system's screenshot key (⌘⇧4 on macOS, Win⇧S on Windows). For a PDF, download it and open it in a real PDF reader.
5. Visible seams or duplicated content at the joins
Between frames, the page moved in a way the capture did not account for: a scroll-triggered animation fired, an ad slot resized, a lazy-loaded element pushed everything below it down, or the site uses smooth scrolling and the page was still gliding when the next photograph was taken.
Fix: let the page settle completely before you start — no animations mid-flight, no video playing, no infinite feed still appending. If the site has an obvious scroll-animation library, capturing after a full manual scroll-through usually settles everything into its final position. Reader mode, where the site supports it, strips the whole category of problem.
6. Very long pages fail or truncate
A stitched screenshot is one image, held in one canvas, and browsers cap how large a canvas can be. The exact limit varies by browser and device, but a page tens of thousands of pixels tall can exceed it. The failure is usually silent: a capture that stops short, or one that never finishes.
Fix: export to PDF rather than PNG, where the content is paginated instead of held as a single enormous bitmap — see saving a full page screenshot as a PDF. Or capture the page in two or three sections. Or zoom the browser out before capturing, which reduces the pixel height proportionally at some cost in legibility.
7. Cookie banners and chat bubbles in every frame
Same mechanism as the sticky header, and worth naming separately because people do not always connect them. A cookie consent bar, a live-chat bubble, a newsletter pop-up and a "back to top" button are all fixed to the viewport, so they land in every frame.
Fix: dismiss them before capturing — accept or reject the cookie banner, close the chat widget. It sounds obvious and it is the thing everyone forgets. A tool that excludes fixed pixel bands handles the ones you cannot dismiss.
8. Wrong colours, or a dark page came out light
Two separate causes. If the site follows your system theme, the capture reflects whatever the page was actually rendering, so switch the theme before capturing rather than after. If you used a print-based method (Ctrl+P → Save as PDF), you got the site's print stylesheet, which is often a deliberately different, colour-stripped layout — that is not a bug either, it is what printing means, and it is the main reason print to PDF makes such a poor screenshot.
9. It worked yesterday and fails everywhere today
If every page fails, the problem is not the page. Work through these in order:
Reload the tab. An extension that updated while the tab was open cannot inject into that already-loaded page. This fixes it surprisingly often.
Check the extension is still enabled at
chrome://extensions. Chrome disables extensions whose listing leaves the store — which is what caught GoFullPage in August 2026 — and shows only a small warning when it does.Check for a conflicting extension. Ad blockers, privacy tools and other capture extensions can interfere. Disable the others, test, re-enable one at a time.
Check the shortcut is still bound at
chrome://extensions/shortcuts. Chrome silently drops a binding when two extensions claim the same combination.Try an Incognito window with the extension allowed there. If it works, something else in your profile is the cause.
If the fix was "get a tool that handles this"
Sticky headers, inner scroll panes and lazy loading are the three that actually break captures, and they are the three this one was built around. Free, no account, and it asks for one tab at a time.
Free. No account, no premium tier, no network requests.
FAQ
Why is my Chrome full page screenshot blank at the bottom?
The page lazy-loads images as you scroll, and the capture reached the bottom before those images finished decoding. Scroll to the very bottom of the page yourself first, wait for everything to appear, scroll back to the top, then capture. Chrome's built-in DevTools command is the worst offender here because it does not pre-scroll the page at all.
Why does the navigation bar repeat down my screenshot?
A sticky or fixed header stays glued to the viewport while the tool scrolls the page, so it is photographed in every frame and stitched in at regular intervals. The reliable fix is a tool that measures the pinned band once and never sources those pixels from any frame after the first. The manual workaround is to delete the header element in DevTools before capturing.
Why does my screenshot only capture one screenful?
You are almost certainly on an app-style page — a mail client, a dashboard, a chat app — where the document itself does not scroll. A pane inside it does. Tools that only walk the document find nothing to scroll and hand back a single screenful. You need a tool that detects the element which actually scrolls, or you need to capture that pane another way.
Why does the extension do nothing when I click it?
Chrome forbids every extension from reading certain pages: the Chrome Web Store, chrome:// pages such as Settings and Extensions, the New Tab page, and other extensions' pages. Nothing is broken and no extension can work around it. Use Chrome's own DevTools screenshot command, or the operating system screenshot key, on those pages.
Why did a very long page fail or come out truncated?
Browsers cap how large a single canvas can be, and a page tens of thousands of pixels tall can exceed it — the result is a capture that fails outright or stops short. Capture the page in sections, or export to PDF, where the page is paginated instead of held as one enormous image.
Keep reading
