GoFullPage: How to Take a Full-Page Screenshot in Chrome
Install GoFullPage, capture a long Chrome page, and export it as an image or PDF. Learn the shortcut, permission prompts, limitations, and fixes for common problems.
To capture a full webpage with GoFullPage in Chrome, install the official GoFullPage – Full Page Screen Capture extension, open the page, then click the GoFullPage icon or press Alt+Shift+P. Wait while it scrolls through the page and assembles the capture. The result opens in a new tab, where you can save it as an image or PDF.
1. Install the official extension
- Open the official Chrome Web Store listing and check that the publisher is Full Page LLC.
- Select Add to Chrome and review Chrome’s installation prompt.
- If the GoFullPage icon is not visible beside the address bar, open Chrome’s puzzle-piece Extensions menu and pin it.
Use the official listing rather than an extension with a similar name. GoFullPage reported a temporary Chrome Web Store removal in August 2026 and announced its restoration on September 14, 2026. Store availability and version details can change; check the listing for current information. GoFullPage’s restoration announcement
2. Capture the whole page
- Open the webpage you want to save in a regular Chrome tab. Let its main content load first.
- Click the pinned GoFullPage icon, or press Alt+Shift+P.
- Keep the tab open and wait. The extension scrolls through the page, captures sections, and combines them into a result.
- When the result opens in a new tab, inspect the top, middle, and bottom for missing, duplicated, or blank areas.
The capture process scrolls the source page. Pages with lazy-loaded content may need that scroll to reveal images and sections. Pages that implement scrolling with custom JavaScript can behave differently, and the extension’s FAQ identifies PDF documents and some custom-scroll pages as exceptions. GoFullPage FAQ
3. Export as PNG, JPEG, or PDF
Choose the output according to how you plan to use it:
| Format | Useful when | Trade-off |
|---|---|---|
| PNG | You want an image capture without JPEG compression. | Large, very tall captures can use substantial memory and disk space. |
| JPEG/JPG | You want a compressed image for sharing. | Compression can soften small text and fine edges. |
| You need a document for printing, sharing, or filing. | It may be split over standard paper pages unless you choose a continuous full-image page. |
For PDF, GoFullPage’s FAQ says to set PDF Size to Full Image when you want a single continuous page. Otherwise, use a standard paper size and orientation if the document needs to print on sheets. The Chrome listing describes PNG, JPEG, and PDF exports; available controls may vary by current version. GoFullPage FAQ · Chrome Web Store listing
GoFullPage’s listing describes cropping, annotation, and emoji tools as Premium editor features. They are optional editing steps, not required to make a capture. Its Files page can be used to view, download, or delete saved screenshots according to the older usage guide. GoFullPage workflow guide
4. Understand permissions and local storage
GoFullPage’s Chrome listing says the developer discloses that it will not collect or use your data. That is the developer’s disclosure, not an independent audit. GoFullPage’s permissions guide says screenshots stay in the extension’s browser storage. Saving them into your Downloads folder can prompt for the Downloads permission.
Capturing content inside an iframe can trigger a separate permission request involving tabs, webNavigation, and host access. The guide says the extension runs on the current tab when you activate it; if you deny the iframe-related request, it will not capture that page’s embedded content, though it can still work on other pages without iframes. Read Chrome’s prompt before allowing access. GoFullPage permissions guide
5. Fix common capture problems
| Problem | Likely reason | What to try |
|---|---|---|
| The icon is missing | Chrome has not pinned the extension in the toolbar. | Open the puzzle-piece Extensions menu and pin GoFullPage. Check chrome://extensions if Chrome has disabled it. |
| The shortcut does nothing | The extension may not be pinned/enabled, or the current page may be protected. | Try clicking its toolbar icon on an ordinary website. Chrome restricts extensions on some internal pages, such as Chrome settings. |
| The page does not scroll or capture stops early | The site may use custom JavaScript scrolling or show content in a PDF viewer. | Try the page’s regular HTML view, capture a smaller section, or use the browser’s print/save option. GoFullPage does not guarantee capture of PDF documents or every custom-scrolling page. |
| Part of the result is blank | Content may not have loaded when that section was captured, or the page may render only after interaction. | Wait for the page to settle, dismiss overlays if appropriate, then capture again. For lazy-loaded pages, scroll through the page once before starting. |
| Embedded content is missing | The page contains an iframe and its optional permission was denied or not granted. | Activate the extension on that page and review the contextual permission prompt. Grant it only if you are comfortable with the requested access. |
| Download fails or asks for permission | Chrome has not granted Downloads access. | Review the prompt. GoFullPage says its capture can remain in extension storage and can be copied to the clipboard without Downloads permission, but saving files requires that permission. |
| The image is split or too large | Very long pages can exceed what Chrome can hold in one image. | Capture smaller portions or export as a paginated PDF. GoFullPage notes that exceptionally long captures may be split into multiple images. |
For a persistent issue, use the support flag on the capture page. GoFullPage’s older guide says a support report may include the page URL, app version, browser type, and operating system, so avoid reporting a sensitive page unless you are comfortable sharing those details. FAQ · Permissions guide
6. Performance and reliability tips
- Wait for dynamic content: let animations, fonts, and important images finish loading before starting. A capture records what the page renders during the scroll.
- Reduce page complexity: close unrelated tabs if Chrome is under memory pressure, and capture a smaller region or page section when the full page is exceptionally long.
- Check the assembled output: inspect transitions between sections, sticky elements, and lazy-loaded areas before relying on the screenshot as a record.
- Choose an export for its destination: use PNG for a sharp image, JPEG when a smaller compressed file is useful, or PDF for paper-oriented sharing.
- Keep sensitive pages in mind: GoFullPage describes screenshots as stored locally in browser storage, but exporting, copying, or sharing the resulting file moves it into the chosen destination.
GoFullPage is a browser extension workflow: it captures the rendered page in Chrome. It does not provide a screenshot API, so this flow is manual and tied to the browser tab and its permissions.
7. Or skip the browser setup
If you need screenshots from code or an automated workflow, ScreenshotNeo is a website screenshot API and MCP server. One GET request returns an image or PDF. Its capture options include full-page screenshots with lazy images loaded and formats such as PNG, JPEG, and WebP.
For a direct request from the shell, replace YOUR_API_KEY with your key:
curl -G "https://api.screenshotneo.com/v1/shot" \
-d access_key=YOUR_API_KEY \
--data-urlencode url=https://stripe.com \
-o shot.webp
Python:
import requests
r = requests.get(
"https://api.screenshotneo.com/v1/shot",
params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
timeout=90,
)
r.raise_for_status()
with open("shot.webp", "wb") as f:
f.write(r.content)
Node.js (Node 18 or later for built-in fetch):
const q = new URLSearchParams({
access_key: 'YOUR_API_KEY',
url: 'https://stripe.com'
});
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const bytes = new Uint8Array(await res.arrayBuffer());
await (await import('node:fs/promises')).writeFile('shot.webp', bytes);
See the ScreenshotNeo API documentation for request parameters and response details. Cookie banners, newsletter popups, and chat widgets are removed before the shot; each of those steps can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers report the page verdict and billing status. An MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients. The Free plan includes 1,000 screenshots per month without a card; paid plans start at $5 for 3,000 screenshots. Every feature is available on every plan.
Sign up for ScreenshotNeo and get 1,000 screenshots a month free, with no card required.
Frequently asked questions
Can I use GoFullPage on Chrome settings or the Web Store?
Chrome restricts extension access to certain protected pages. Open a normal website to capture it.
Can I make one continuous PDF page?
Yes. GoFullPage’s FAQ says to choose Full Image for PDF Size. Standard paper sizing produces a document intended for paginated printing.
Does GoFullPage capture every iframe automatically?
No. Capturing embedded frame content can require an optional permission prompt. Without the permission, that embedded content may be unavailable.
Where are screenshots stored?
GoFullPage says its extension stores screenshots in browser storage on the computer. Downloading or sharing a capture creates a copy outside that storage.
Can I capture a page without installing an extension?
Chrome’s print dialog can save many ordinary pages as PDF, though it may paginate the content and is not equivalent to an assembled full-page image. For a code-driven capture, use a screenshot API such as ScreenshotNeo.


