Run the 60-second preflight
Many failed captures come from the page state rather than the export button. Reset the conditions first so that an overlay, half-loaded feed, or inactive tab does not obscure the real cause.
- Confirm the address begins with http:// or https://. Browser settings, extension pages, and web stores are restricted surfaces.
- Reload the page, wait for fonts and images, dismiss cookie banners or dialogs, then scroll once to expose any content that loads on demand.
- Return to the top, set browser zoom to a stable value, and avoid resizing the window after capture begins.
- Keep the source tab in the foreground and do not click, type, play media, or open menus while the page is moving.
Eight fixes, in the order worth trying
- 01
Move off a protected browser page
Chrome does not allow ordinary extensions to run on chrome:// pages, the Chrome Web Store, or other extension pages. Open the information on a normal webpage if possible; no permission toggle inside FullPageRoll can bypass this browser restriction.
- 02
Reload and let the page settle
A page can look ready while fonts, images, or client-side sections are still changing its height. Reload, wait, make one manual pass through the content if necessary, then return to the top before starting again.
- 03
Close temporary overlays
Cookie banners, chat launchers, newsletter dialogs, and consent sheets can cover content or change page scrolling. Dismiss what you are allowed to dismiss and capture the page in the exact state you want to preserve.
- 04
Keep the tab active
Keep the selected browser tab visible until capture finishes. Switching away, minimizing the window, or changing the source page can interrupt the process or produce an incomplete result.
- 05
Identify the real scroll container
Some application shells keep the browser window fixed and scroll a large inner panel. FullPageRoll detects common nested scrollers, but unusual layouts may still need a clean reload or a simpler page state. Record which panel moves when you report the issue.
- 06
Give lazy content a first pass
If cards or images appear only near the viewport, scroll through the page once so its data requests can complete. Then return to the top and start a fresh capture. Do not do this for an endless feed unless you have chosen a clear stopping point.
- 07
Pause motion where possible
Pause video, carousels, and autoplay animation where possible. Content that keeps changing during capture can appear inconsistent between adjacent parts of the final image.
- 08
Inspect before exporting again
Open the preview and check the first screen, middle joins, sticky controls, and footer. If only the PDF looks wrong, compare the PNG from the same capture. That separates a capture defect from an output-format problem.
Match the symptom to the first useful action
A specific symptom narrows the problem faster than reinstalling everything. Use this table to choose the first action, then change one variable at a time.
| Symptom | Likely cause | First action |
|---|---|---|
| Capture stops before the footer | Page height changed or an infinite feed kept growing | Preload a finite range and define the stopping point |
| Header appears many times | Fixed or sticky element was not deduplicated in that layout | Reload, close overlays, and record the header behavior |
| Images or cards are blank | Lazy content had not loaded or settled | Scroll once, wait, return to top, and recapture |
| Extension does nothing | Restricted page or missing page access | Try a normal https:// page and check extension access |
| Content is duplicated near an animation | The page changed while it was being captured | Pause motion or capture a stable page state |
Recognize the hard limits
Some failures are browser or media boundaries, not settings mistakes. FullPageRoll documents these limits so that a difficult result is not presented as a guaranteed success.
- Protected Chrome pages, the Chrome Web Store, extension pages, and some cross-origin content do not allow ordinary extension capture.
- Local file pages require “Allow access to file URLs” in the extension settings before an extension can run there.
- Infinite feeds have no natural endpoint, and exceptionally wide or long pages can exceed the browser's image-size limits. Capture only the finite range you need.
- Continuously playing video, WebGL animation, and interactions driven only by physical wheel events may not preserve every moment or state in one static result.
Chrome's extension documentation explains the browser-controlled page restrictions in its activeTab permission guide (opens in a new tab).
Turn a failure into a reproducible report
A useful report describes the environment and the first visible defect without sending private page content unnecessarily.
- Browser name and exact version.
- How you started the capture: toolbar button or keyboard shortcut.
- Operating system, browser zoom, viewport size, and whether the window was maximized.
- Page type and behavior: fixed header, inner scroller, lazy grid, video, WebGL, or infinite feed.
- The earliest wrong location, expected result, actual result, and whether PNG and PDF differ.
If the page is private, share a simplified reproduction or a redacted image instead of sending confidential content. Never send passwords, authentication tokens, private messages, or customer data.
Common full-page screenshot problems
Why does the screenshot stop before the bottom?
The page may still be changing height, loading an endless feed, or scrolling inside a separate panel. Wait for a stable endpoint, identify the panel that actually moves, return it to the start, and capture again.
Why are images blank even though the text is present?
The images may load only when they approach the viewport or may be served from a protected embed. Scroll through once and wait for the requests to finish. If the embed remains blank, use its own download option or a visible-area screenshot.
Why does the result contain duplicated menus or chat buttons?
Those controls are usually fixed to the viewport. Close disposable overlays before capture and avoid interacting while the page moves. If the same control still repeats, record the page URL, browser, zoom, and a screenshot of the defect.
Will reinstalling the extension fix every capture?
No. Reinstalling can repair a damaged extension state, but it cannot bypass browser-restricted pages or turn an endless feed into a finite document. Match the symptom first so you do not erase useful evidence without addressing the cause.