The wayback_machine_downloader Ruby gem — alternatives in 2026.

What the Ruby gem is and what it still does

wayback_machine_downloader is a command-line tool originally written by Hartator and published as a Ruby gem on GitHub. It takes a domain, queries the Wayback Machine’s CDX index for every captured URL on that domain, and fetches each one sequentially to a local folder.

Install and run (if you already have Ruby):

gem install wayback_machine_downloader
wayback_machine_downloader http://example.com \
  --to 20130425000000

That still works today for small sites. It gives you a near-raw copy of the archived HTML, keeps the original folder structure, and doesn’t do anything fancy. For a quick snapshot of a small brochure site, that’s fine.

Where the gem hits its limits today

Four things to know before you commit:

1. No link rewriting. Internal links still point at web.archive.org/web/{ts}/..., which means the extracted folder doesn’t open standalone — you’d have to find-and-replace the whole tree yourself.
2. No Wayback toolbar removal. The HTML still contains the injected archive toolbar and tracker script. Those have to be stripped manually or with a post-processing script.
3. Rate limit sensitivity. For medium-to-large sites, the gem’s request rate is enough to trigger HTTP 429 on the archive. Jobs stall or finish with silent gaps. See the 429 guide for why.
4. Maintenance lag. Ruby versions and gem dependencies move on; installing it cleanly on a new machine in 2026 often means fighting a Ruby version manager before you even start the download. (For scripters already in that ecosystem, this isn’t a cost; for everyone else, it is.)

None of this makes the gem bad — it makes it a 2015 tool that works best on a 2015 scale of problem. Good for a small personal blog, painful for a 300-page WordPress site.

Five realistic alternatives

1. A hosted downloader — the lowest-friction option

A browser-based downloader like wayback.download handles rate limiting, toolbar stripping, link rewriting and the smart page selection for you. You paste the timestamped URL, add an e-mail, and get a ZIP in a few minutes.

• Pros: no install, no Ruby, no 429 hunting, ZIP is ready to re-host.
• Cons: free pack has a page cap (which is fine for small sites, upgrade for bigger).
• Best for: site owners, one-off recoveries, people who don’t want to live in a terminal.

wget --mirror — the honest Unix baseline

If you just need a raw copy and you’re comfortable at the command line, stock wget pointed at a Wayback URL still works. With the right flags it also throttles politely:

wget --mirror \
     --convert-links \
     --adjust-extension \
     --page-requisites \
     --no-parent \
     --wait=1 --random-wait \
     --limit-rate=200k \
     https://web.archive.org/web/20130425054636/http://example.com/

• Pros: ships with every Linux and macOS; small, auditable, nothing to install.
• Cons: no toolbar removal; --convert-links is imperfect against archive URLs; needs manual cleanup.
• Best for: scripters who need something reproducible in a CI job.

HTTrack against a Wayback URL

HTTrack is a mature cross-platform offline site copier with a GUI. Pointed at a timestamped Wayback URL it does a reasonable job on small sites.

• Pros: Windows GUI, stable, familiar to a lot of sysadmins.
• Cons: wasn’t built for the Wayback Machine specifically; still leaves the toolbar; concurrency defaults can trigger 429s.
• Best for: Windows users who want a GUI for small jobs.

Browser “Save Page As” — one page at a time

If you only need one page (say, a specific blog post you’re quoting in an article), you can open the capture in Chrome or Firefox, hit Ctrl+S, and choose “Webpage, Complete”. You get an HTML file plus an assets folder.

• Pros: trivially simple; no tools at all.
• Cons: single page only; still has the Wayback toolbar in the HTML; links still point at archive URLs.
• Best for: saving a single capture for reference.

A human restoration team — when it has to be right

If the site is big, needs to end up on WordPress or Elementor, or matters for a legal/business reason, the lowest-friction option is actually to hand it to people who do this for a living. Our team at waybackrevive.com rebuilds sites by hand from the archive — HTML from $30, WordPress from $110, Elementor from $149, WooCommerce from $249. Pricing and terms are on that site.

• Pros: finished site, not a folder of raw files; works for CMS targets.
• Cons: costs money; turnaround is 24–48 hours, not instant.
• Best for: business-critical restores, WordPress targets, anything bigger than a weekend project.

Side-by-side comparison

How to pick

Honest flowchart, no jargon:

• Single page? Save it from the browser and move on.
• Small static site (< 20 pages) and you don’t want to install anything? Use the free pack on wayback.download.
• Already a Ruby developer with a small job and 20 minutes to clean up links afterwards? The gem still works. Set concurrency to 1, read the 429 guide.
• You live in a terminal and want it in a shell script? Use wget --mirror with the polite flags from the example above.
• Big site, needs WordPress or similar at the end, matters for a business or legal reason? Pay the restoration team. A couple hundred dollars is cheaper than two days of your time fighting link rewriting.

Try the free downloader →   Read the FAQ