A free, maintained reference for people who actually need to pull a site out of the Internet Archive — written by the team that does this work for a living. No fluff, no “100 % guaranteed” hype, and no login wall in front of the content.
Abandoned GitHub tools. Forum threads from 2015. Blog posts that still recommend commands that now return rate-limit errors or empty files. We’re the team people e-mail after those fail, so we decided to keep a short, honest handbook on this page — free, no account, no obligation to hire us afterwards.
Every guide is written by someone who has actually rebuilt a site from archive.org this month — not spun from a competitor’s SEO post. If a method stops working, we update the page.
When a guide calls for a downloader, we point at the free tool at wayback.download — our own, and the one we trust — without e-mail walls, sign-up gates, or fake “unlock” buttons.
When the free download isn’t enough, our restoration team at waybackrevive.com rebuilds the whole site by hand — HTML, WordPress, Elementor, WooCommerce. Pricing and terms are on that site.
Each guide is written as a standalone handbook chapter: a plain-English summary, numbered steps, honest caveats, and a short “when this isn’t enough” section at the end.
The complete walkthrough: find the right snapshot date, grab a clean timestamped URL, run it through a downloader, handle redirects and missing pages, and end up with a working folder you can re-host.
Why the archive rate-limits you, how to back off politely, what retry-after headers actually mean, and three concrete fixes depending on whether you’re using a browser, a command-line tool, or a hosted downloader.
An honest look at the classic wayback_machine_downloader
Ruby gem, where it still shines, where it hits rate limits, and five
alternatives — hosted, command-line, and browser-based —
that are more practical today.
See the full index in the guides library — more chapters land as we hit new questions in support e-mail.
The Internet Archive’s Wayback Machine stores point-in-time captures of public web pages. A download tool fetches the archived HTML, CSS and JavaScript, strips the Wayback toolbar overlay, rewrites internal links so they work locally, and packs the whole thing into a ZIP or a folder you can host anywhere — a cheap static host, a desktop browser, a USB stick.
readme.txt listing the snapshot date and pages the archive didn’t have.If a downloader quietly fabricates missing pages or substitutes images, that’s a red flag — the archive is ground truth, and honest tools say so.
Longer answers, edge cases, and licence questions live on the full FAQ page.
It’s shorthand for pulling a captured version of a webpage or website out of the Internet Archive’s Wayback Machine at web.archive.org so you can read it offline, archive it, or re-host it as plain HTML, CSS and JavaScript.
The archive stores snapshots only — you can’t “install” a Wayback Machine download. You re-create a static copy of what the archive captured at a specific moment.
Four steps: (1) find the capture date you want on
web.archive.org;
(2) copy the full timestamped URL (it looks like
https://web.archive.org/web/20130425054636/http://example.com/);
(3) paste it into a downloader — the free one at
wayback.download
is what we use ourselves — and (4) wait for the ZIP.
Full walkthrough with the gotchas: the “how to download a website” guide.
The Internet Archive rate-limits the Wayback Machine to protect their infrastructure. Any client that fires requests too quickly from a single IP — a browser on an aggressive script, a command-line downloader with concurrency turned up, or many people sharing one network — will hit HTTP 429 and either stall or get empty responses.
Fixes in order of effort: wait and retry with exponential backoff, throttle to roughly one request per second, or hand the job to a server-side tool that already handles polite backoff. Full fix list: the 429 guide.
wayback_machine_downloader still worth using?For small jobs, if you already have Ruby set up and know the command line, it still runs. It gives you a raw copy of the archived HTML without link rewriting or toolbar removal, and it often hits 429 rate limits on medium-to-large sites.
For most people in 2026, a hosted tool is less painful than fighting Ruby version managers; for scripters, the gem is still a reasonable DIY baseline. Honest comparison: Ruby gem alternatives.
Wayback Revive LLC is an independent company and is not affiliated with, endorsed by, or sponsored by the Internet Archive (operators of the Wayback Machine at archive.org). We read the public Wayback Machine snapshots the way a browser would.
Read the full FAQ or jump into the how-to walkthrough.
For large sites, WordPress conversions, Elementor rebuilds, or an expired domain you need back online quickly, our team at waybackrevive.com delivers hand-checked restorations in 24–48 hours. Pricing and terms are on that site. Already restored? Revive Guard is our WordPress care plan from the same people.
Restoration from $30 (HTML) / $110 (WordPress) · Revive Guard care plans available separately