Recommended Free Tools
For a timeout affecting Chrome alone, increase ArchiveBox’s CHROME_TIMEOUT setting. To make it persistent for the collection, run archivebox config --set CHROME_TIMEOUT=300. Use TIMEOUT for the per-extractor limit across extractors without their own override; CRAWL_TIMEOUT controls the total crawl duration, not an individual Chrome capture.
Increase the timeout for Chrome
Run this command from the ArchiveBox environment that manages your collection:
archivebox config --set CHROME_TIMEOUT=300This stores a Chrome-specific timeout of 300 seconds in the collection’s configuration. The setting is measured in seconds. The official ArchiveBox configuration reference documents CHROME_TIMEOUT as a Chrome-specific override and uses 300 seconds as an example; it does not establish that 300 seconds is right for every site or deployment.
To check the effective value, run:
archivebox config --get CHROME_TIMEOUTYou can also inspect the full effective configuration with archivebox config. ArchiveBox documents CLI settings, configuration files, and environment variables as configuration methods, including for Docker workflows (configuration reference; project repository; usage documentation).
#1 Best Overall
Choose the setting that matches the timeout
ArchiveBox has separate limits for one extractor, Chrome specifically, and an entire crawl. Raising the wrong one may not affect the failure.
| Setting | What it limits | When to change it |
|---|---|---|
CHROME_TIMEOUT |
Chrome’s per-snapshot extractor runtime; it takes precedence over the shared TIMEOUT for Chrome. |
Use this for a Chrome-only timeout. |
TIMEOUT |
Maximum runtime for one extractor on one snapshot. The configuration reference gives a default of 60 seconds. | Raise this when multiple extractors, rather than Chrome alone, need more time and do not have their own override. |
CRAWL_TIMEOUT |
Total wall-clock runtime for the crawl, including snapshots, extractors, retries, and discovery passes. | Change this only when the whole crawl is hitting its overall time limit. It does not extend an individual Chrome invocation. |
The configuration reference recommends 30 to 3000 seconds for TIMEOUT and warns against setting it below 5 seconds. Those are documentation guidelines, not a universal target; choose a value appropriate to the page and the runtime your deployment can allow (ArchiveBox configuration reference).
Set the value in a configuration file or for one command
Use ArchiveBox.conf
In the data directory’s existing [ARCHIVING_CONFIG] section, add:
CHROME_TIMEOUT=300Use the existing section rather than creating a duplicate. Then verify the effective setting with archivebox config --get CHROME_TIMEOUT.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Use an environment variable for one command
To apply the setting only to a particular command, prefix it with the environment variable:
env CHROME_TIMEOUT=300 archivebox add 'https://example.com'Replace the URL with the page you are archiving. This is useful for testing a longer limit without changing the collection’s persistent configuration. The documented configuration methods also apply in Docker; make sure the variable or stored setting reaches the ArchiveBox process that runs the capture (configuration reference; usage documentation).
Rank #4
Raise the shared extractor timeout instead
If the slow extractor is not limited to Chrome, set the shared value:
archivebox config --set TIMEOUT=120An extractor-specific override takes precedence over TIMEOUT, so changing the shared value alone will not replace a Chrome-specific limit that is already set.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Diagnose the failure before raising the limit again
- Identify what failed. Note whether the missing or failed output is DOM HTML, a screenshot, a PDF, or SingleFile. Different outputs can fail for different reasons.
- Check the effective configuration. Inspect
CHROME_TIMEOUTandTIMEOUTwitharchivebox configorarchivebox config --get CHROME_TIMEOUT. Also check whether an environment variable or collection configuration is affecting the command. - Raise the Chrome-specific limit and retry. Use
CHROME_TIMEOUTwhen the Chrome extractor is the one timing out. - If it still fails, investigate the particular output and page behavior. A longer limit cannot guarantee that Chrome renders a page successfully or that ArchiveBox produces every output.
A 2023 ArchiveBox issue described Chrome PDF and screenshot outputs that retained a loading spinner while HTML-related outputs were missing. It is a historical report, not evidence of a general problem in current releases, but it illustrates why the exact failed output matters (ArchiveBox issue tracker).
What a longer timeout can—and cannot—fix
Increasing CHROME_TIMEOUT helps when Chrome is still working and ArchiveBox is stopping that extractor at its configured limit. It gives the browser more time, but it does not fix a page that never finishes rendering, a browser problem, or an output-generation failure. There is no single timeout value that guarantees success for every page; the documented range is guidance, and the right setting depends on the workload and how long the deployment can wait.
Or skip the browser setup
If you need a screenshot rather than an ArchiveBox collection, ScreenshotNeo is a website screenshot API and MCP server. One request can return a screenshot or PDF; its capture options include full-page shots, element selection, and waiting for a selector, delay, or network idle. For setup and available parameters, see the ScreenshotNeo documentation.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpScreenshotNeo accepts cookie banners before capture and removes supported consent banners, newsletter popups, and chat widgets. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed. An MCP server lets AI agents use screenshot tools. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 shots.
Sign up for ScreenshotNeo’s free plan to get 1,000 screenshots a month with no card.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
