web-archive
archive.today (.ph / .is / .md / .li / .vn / .fo)
An on-demand archiver where anyone can submit a URL and get a permanent snapshot; it flattens dynamic pages into static copies and often gets past paywalls, with tens of millions of snapshots accumulated. Existing captures are found via its Memento timemap and opened as direct snapshot links on archive.ph and its mirror domains; saving a new page is done on the website and may require solving a CAPTCHA. Reach for it when a page changed or vanished too recently for other archives, or when a paywalled article needs a readable copy.
Why it’s useful & how it works
Archive.today is the right tool when a page has changed or vanished too recently for crawl-based archives, or when you need a readable copy of a paywalled article. Anyone can submit a URL on the website to create an immediate, static snapshot; the page is flattened into a permanent copy that strips most dynamic elements. Existing snapshots are found by searching on archive.ph or through its Memento timemap, which lists all captures of a given address. Echo links you directly to the most recent snapshot or to the timemap so you can choose a date.
What’s inside
The total number of snapshots is not publicly disclosed. The service has operated since 2012 and has accumulated tens of millions of captures, with no authoritative figure available from the operator.
API access
No REST API. Memento TimeMap: http://archive.ph/timemap/ <url> (works). Save via POST https://archive.ph/submit/ (url=).
What we measured
Our own probes, not the archive’s own claims. Re-run periodically; every reading below is dated.
Reachability
- Direct request
- Rate-limited HTTP 429 752 ms
- Through a datacenter proxy
- Rate-limited HTTP 429 1.4 s
- API, direct
- Rate-limited HTTP 429 397 ms
- API, through a proxy
- Rate-limited HTTP 429 804 ms
- API timemap, direct
- Rate-limited HTTP 429 392 ms
- API timemap, through a proxy
- Rate-limited HTTP 429 1.8 s
Did a real search return anything?
The request failed · median 11.2 s · down during the run
Slow: budget for long waits, or call it asynchronously.
HTTP 429 on every attempt (direct and proxy).
Benchmark coverage
Found 0 of 10 test items (0%) in the Web pages / sites cluster. Median response 232 ms.
By how well known the item is: 0/3 well-known, 0/4 mid, 0/3 obscure .
Reachability measured 2026-08-22. Search checked 2026-08-22. Benchmark run 2026-08-22.
Access
May require solving a captcha before it responds.