Reload the page once
After installing or updating the extension, reload the tab you want to capture so Chrome can grant access to that page.
Capture troubleshooting →
Ready2UP Support
Get back to a clean capture, quickly
Start with the short checks below. They solve most capture and export problems without changing your data or privacy settings.
No account or ticket portal
Help is public, direct and privacy-conscious. Contact details are available below if the quick fixes do not work.
Start here
Three checks before anything else
Keep the page open while capturing, and avoid refreshing until the progress indicator finishes.
Use a regular web page
Chrome blocks extensions on browser settings, the Chrome Web Store, some built-in PDF views and other protected pages.
Check restricted pages →Keep the tab visible
For a long capture, leave the source tab active until scrolling and stitching finish. Switching away can interrupt browser capture.
Fix incomplete results →
Troubleshooting
Common problems and practical fixes
Open the issue that best matches what you see.
The capture does not start
- Reload the page after installing or updating the extension.
- Click the extension while the page you want is the active tab. This grants the temporary
activeTabaccess used for capture. - Try a normal
https://page. Chrome does not allow capture scripts on protectedchrome://pages or the Chrome Web Store. - If the popup is hard to find, open Chrome's puzzle icon and pin Full Page Screenshot.
The full page is incomplete or looks misaligned
- Wait for images, charts and web fonts to finish loading, then start again from the top of the page.
- Keep the source tab active until the progress indicator completes.
- Pause animated feeds, auto-loading pages or live dashboards when possible; changing content can move between captured slices.
- For a scrollable panel, click inside it first and retry. Cross-origin iframe content may remain restricted by the browser.
Chrome says the page cannot be captured
This is usually a protected browser page rather than a missing permission. Chrome blocks extensions on chrome:// pages, the Chrome Web Store, some browser-owned PDF viewers and a few security-sensitive surfaces. Open the content in a regular website tab or download the PDF and use a dedicated PDF tool.
Why can a PDF only be captured one page at a time?
Chrome opens PDFs in a built-in viewer that is sealed off from extensions. The page an extension receives is empty: there is no scrollable document to advance and no viewer frame to read, so a full-page capture could only ever contain the page already on screen. This is a Chrome limitation that applies to every screenshot extension, not a fault in this one.
Rather than quietly saving a one-page image that looks like a failure, the extension now says so and stops. To capture a PDF, use Visible area once per page, which works normally. To keep the document itself, use the download button inside Chrome's PDF viewer.
The file does not download or export
- Check Chrome's Downloads page for a blocked or renamed file.
- Confirm the browser is allowed to download files to your chosen folder.
- For an extremely tall page, try PNG or JPEG first. Large PDF or WebP exports can need more available memory.
- Close memory-heavy tabs, retry the capture and export before opening more pages.
Text or images look softer than expected
Very tall pages can exceed Chrome's maximum canvas dimensions. When that happens, the extension scales the finished image so it remains valid instead of creating a blank file. Capture a smaller region or split the page into sections when full native resolution matters most.
What should I share when asking for help?
Describe the browser version, extension version, capture mode and what happened. A public example URL is useful when available. Do not send private screenshots, passwords, payment details or confidential page content. Read the privacy policy for the extension's complete data handling details.