How to Make ArchiveBox Capture Full-Page Screenshots of Long Web Pages
ArchiveBox’s standard Chrome screenshot uses a configured viewport. Learn how to save a full-page PNG with its browser extension and where that capture is stored.
ArchiveBox’s standard headless Chrome screenshot is documented as a viewport capture. Its resolution settings control the viewport dimensions; they are not documented as a switch that guarantees a screenshot of the full document height. For a documented full-page screenshot, use the ArchiveBox browser extension: it can save a full-page screenshot locally and export it as a PNG.
The extension workflow is a browser action, and its documented local capture is stored in browser extension storage. Do not assume that the locally saved image has automatically become a file in the server-side ArchiveBox Snapshot.
Use the ArchiveBox browser extension for a full-page PNG
- Make the ArchiveBox server accessible from the browser where you have installed the extension.
- Configure the extension’s server URL and authentication or API key as appropriate for your ArchiveBox version and setup.
- Open the long page in that browser. Use the extension icon or its “Save to ArchiveBox” context-menu action.
- Find the capture in the extension’s Saved URLs or local capture view. When local capture saving is enabled, the extension README documents a path like
snapshots/YYYYMMDD/example.com/{uuid}/chrome_extension_screenshot/screenshot.pngin extension-local OPFS storage. - Use the extension’s Export menu to export the screenshot as a PNG.
This produces a local extension artifact. If you need the screenshot in a server-side collection, verify that it was transferred or exported into the intended collection. The documented local-saving and export workflow does not establish automatic transfer of that screenshot into the server-side Snapshot directory.
Configure the built-in screenshot extractor
Use the built-in extractor when you want ArchiveBox’s server-side archive workflow and a screenshot at a chosen viewport size. The configuration reference describes RESOLUTION as the default screenshot/PDF viewport resolution and SCREENSHOT_RESOLUTION as the screenshot-specific override.
Set configuration using the method appropriate to your collection:
# Set the default screenshot and PDF viewport resolution
archivebox config --set RESOLUTION=1440,1200
# Override the screenshot viewport resolution only
archivebox config --set SCREENSHOT_RESOLUTION=1440,1200The values above are examples of width and height in pixels. Check the effective setting for the Crawl, Snapshot, or Persona that runs the capture: existing Crawl configuration can take precedence over later environment defaults. You can also set options through the collection’s ArchiveBox.conf or environment variables, as supported by your setup.
These settings change the viewport dimensions. A taller viewport may show more of a page, but the documentation does not say it guarantees a screenshot of the entire document. Raising the timeout can give a slow extractor more time to run; it does not extend the screenshot to the page’s full height.
Choose the right workflow
| Need | Workflow | What to expect |
|---|---|---|
| Full-page image through a documented ArchiveBox workflow | Browser extension | Full-page screenshot saved locally; export as PNG. Confirm separately if it must be in a server-side collection. |
| Server-side ArchiveBox screenshot output | Built-in Chrome screenshot extractor | Screenshot uses configured viewport dimensions. No universal native full-height switch is established by the inspected documentation. |
| Automated screenshot capture through a screenshot API | ScreenshotNeo | One GET request returns an image or PDF; see the section below for a runnable call. |
The extension README also describes MHTML capture through Chromium’s pageCapture.saveAsMHTML() API, available in Chrome, Edge, and Chromium builds. Firefox and Safari builds skip MHTML because that API is unavailable there. This MHTML limitation does not establish that screenshot behavior is identical across all browsers, so check the behavior of the extension build you use.
Long-page edge cases
- Lazy-loaded images: The inspected ArchiveBox documentation does not guarantee that either workflow will load every image below the fold. Check the exported PNG for missing content.
- Infinite scroll: There is no documented guarantee that the built-in extractor or extension will scroll indefinitely or capture dynamically appended content. A page may need to be loaded or scrolled before capture.
- Very tall documents: The inspected documentation does not specify a maximum full-page image height or promise that extremely long documents will be captured in one image. If the output is incomplete, try the extension workflow and inspect its PNG export.
- Browser differences: Confirm screenshot behavior in the browser and extension build you run. The documented MHTML support differences are specific to MHTML.
- Local versus archived output: Extension-local OPFS storage and a server-side ArchiveBox Snapshot are distinct locations. Verify the final artifact’s location before relying on it in an automated archive pipeline.
Troubleshooting
| Symptom | Likely cause | What to do |
|---|---|---|
| Only the top portion appears in the built-in screenshot | The standard screenshot is viewport-sized. | Use the browser extension’s documented full-page capture and export its PNG. |
| A larger resolution still does not show the full document | RESOLUTION and SCREENSHOT_RESOLUTION specify viewport dimensions; they are not documented full-height switches. |
Use the extension workflow for full-page capture. Check that the intended effective configuration is active for the run. |
| The extractor times out or runs too slowly | The page or extractor may need more runtime than the configured ceiling. | Review TIMEOUT and any plugin-specific setting such as CHROME_TIMEOUT. These affect runtime, not capture height. |
| The extension cannot reach the ArchiveBox server | The server URL may be inaccessible from the browser, or the extension’s URL or authentication settings may be wrong. | Check browser-to-server reachability and the extension’s configured server URL and credentials for your version. |
| The screenshot is visible in the extension but absent from the server archive | The capture may still be in extension-local OPFS storage. | Export or transfer it using the workflow available in your setup, then verify the destination collection. Do not infer that local saving automatically creates a Snapshot artifact. |
| Images or content near the bottom are missing | Lazy loading or dynamic page behavior may not have completed; the inspected documentation does not guarantee those cases. | Load or scroll the page as needed before capture, then inspect the PNG. Infinite-scroll behavior is not guaranteed. |
Or skip the browser setup
For a screenshot API, ScreenshotNeo takes a URL in one GET request and returns an image or PDF. Its cookie and consent handling removes known consent banners, newsletter popups, and chat widgets before the capture; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and responses identify the page verdict and billing status in headers. ScreenshotNeo also has an MCP server with take_screenshot, get_page_info, and capture_pdf tools for AI agents.
Here is a runnable cURL example; replace the key and target URL. See the ScreenshotNeo API documentation for request options.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpThe free plan includes 1,000 screenshots per month with no card. Paid plans start at $5 for 3,000 screenshots. Sign up for 1,000 free screenshots a month, with no card.
Performance, reliability, and cost
For ArchiveBox, the main operational choice is whether the capture needs to run as part of the server-side extractor or can be made in a browser and exported. The extension’s documented local storage means you should plan for an explicit artifact handoff if a server-side archive needs the PNG. The built-in extractor’s timeout settings are per-extractor runtime controls; increasing them may help slow pages complete, but cannot make a viewport screenshot full-page.
The inspected ArchiveBox material provides no benchmark or cost figure for either capture path. For ScreenshotNeo, only clean shots are billed; bot checks, CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing. The plans are Free: 1,000 shots/month; Starter: $5 for 3,000; Growth: $15 for 15,000; Pro: $39 for 60,000; Scale: $99 for 250,000; Business: $249 for 1,000,000. Yearly billing gives two months free, and every feature is on every plan.
FAQ
Does increasing ArchiveBox’s screenshot resolution capture the whole page?
No such guarantee is documented. The settings control viewport dimensions. Use the extension’s documented full-page screenshot workflow when you need a full-page PNG.
Does increasing TIMEOUT make a screenshot full-page?
No. Timeout controls how long an extractor may run. It does not change capture height.
Is the extension screenshot automatically stored in the server-side Snapshot?
The inspected README documents local extension storage and PNG export, not automatic transfer into the server-side Snapshot directory. Verify the artifact’s destination in your setup.
Does ArchiveBox guarantee capture of infinite-scroll pages?
The inspected documentation does not establish that guarantee. Load the content you need before capturing and inspect the resulting image.
