Is your Wayback Machine downloader not working? Most failures come from four causes: the archive is rate-limiting your requests, the snapshot you picked is empty or an error page, the assets were never captured, or the links still point at web.archive.org. Check them in that order and you will fix most problems in one session. If the Wayback Machine website itself will not load, start with our checklist for when the Wayback Machine is not working. This guide covers those four, plus the less common errors: slow or timed-out downloads, the wrong version of the site, odd file names, and tools that will not install.
Wayback Machine downloader not working? Quick checklist
- Did the download stop with HTTP 429 or a timeout? Slow down and resume.
- Do the saved pages show content when you open them on web.archive.org?
- Are images, CSS or fonts missing only in your copy, or in the archive too?
- Do links in your files still start with web.archive.org?
- Is the tool’s runtime installed and up to date?
- Does the archive actually hold more than the homepage?
1. The download stops partway or returns 429 errors
The Internet Archive limits how many requests one client can make in a short time. A downloader that fetches hundreds of files in a minute gets HTTP 429 (Too Many Requests) responses, or the connection stalls.
- Add a delay of one to two seconds between requests if the tool allows it.
- Resume the existing download instead of starting over. Most tools keep the files they already saved.
- If it keeps failing, wait an hour and run it again with fewer parallel connections.
2. The files download but the pages are empty or show an error
Archive snapshots are not all equal. Some captures are redirects, server errors or pages blocked when the crawler visited. A downloader saves them without complaint, so the result looks like a broken site.
- Open the page on web.archive.org and use the calendar view to pick a date where the page shows real content.
- Run the download again with that timestamp, or restore the single page from the snapshot you chose.
- Check the first few saved pages before you download the whole site.
3. Pages load but images, CSS or fonts are missing
The archive only has the files the crawler captured. Assets served from another domain, a CDN or a script that loaded late may never have been saved. This is the most common reason a downloaded site looks plain or broken.
- Open the saved HTML and find the missing asset URLs.
- Search web.archive.org for those exact URLs. An asset may exist under a different date than the page.
- If an image or stylesheet is still missing, rebuild or replace it. Do not invent content that was never captured.
Our guide on recovering missing images from the Wayback Machine covers this in more detail.
4. Links still point to web.archive.org or to broken paths
Archive pages rewrite links to the archive’s own address, so a downloaded site often links back to the live archive instead of its own files. Relative paths, trailing slashes and query strings can break after the download too.
- Search the downloaded files for web.archive.org and replace those links with local paths.
- Check that every internal link points to a file that exists, following the trailing-slash rule your files use.
- Test the site offline in a browser before you upload it.
The step-by-step fix is in how to fix broken links and archive URLs in a downloaded website.
5. Downloads are slow or time out on large sites
A site with thousands of captured URLs can take hours, and one slow response can stop the whole job. Large blogs, shops and sites with many image sizes are the usual cases.
- Limit the job to the paths you need, for example only the blog or only the pages, instead of every captured URL.
- Restrict the date range so the tool does not fetch every version of every file.
- Skip file types you do not need, such as old video files or tracking scripts.
- Split the work into several smaller runs and check each one before starting the next.
6. You downloaded the wrong version of the site
Many downloaders fetch the newest capture of each file by default. If the site changed owners, was redesigned, or was replaced by a parked page, the newest capture is not the version you want, and pages from different dates can mix into one inconsistent copy.
- Decide the target date first: the last capture where the site looked the way you remember.
- Use the tool’s date options to download from that period only.
- Open a few pages from the result and compare them with the archive at your chosen date.
7. Files are saved with odd names or query strings
Archived URLs often include query strings like ?ver=5.2 on stylesheets and scripts, or several versions of the same page with and without index.html. Downloaders save these as separate files with long or encoded names, and the pages then fail to find them.
- Look for duplicate files that differ only by a query string and keep one clean copy.
- Update the references in the HTML to the file name you kept.
- Check that the homepage is saved as index.html at the root, so hosting serves it correctly.
8. The command-line tool will not install or run
Open-source downloaders are written for a specific runtime. A version mismatch, a missing library or a folder path with spaces is enough to stop them before they start.
- Read the first line of the error. It usually names the missing package or version.
- Install the runtime the tool asks for, then reinstall the tool from its official repository (for the Ruby-based wayback-machine-downloader, that is the project page on GitHub).
- Run it from a folder with a short path and no special characters.
For a clean install from scratch, follow our step-by-step guide on how to use Wayback Machine Downloader on Windows, Mac and Linux.
9. The archive has no usable copy at all
A downloader can only save what the archive holds. If the site was never crawled, or only the homepage was saved, no tool can create the missing pages. If the archive is thin, read what to check when a website is missing from the Wayback Machine.
Check the archive before you download
Five minutes of checking saves hours of failed downloads. Open the domain on web.archive.org and look at the calendar to see when it was captured most often. Then list the captured URLs for the domain to see how many real pages exist, which sections were archived, and whether images were saved. If most pages only have one or two captures, expect gaps and plan to fill them by hand.
When to stop fixing it yourself
DIY downloads suit developers who want raw files and can clean them up. If your Wayback Machine downloader is not working after these checks, or you need a working business site, the cleanup often takes longer than the download. A done-for-you download checks every page, removes archive code, fixes links and images, and delivers files you can upload. Our HTML website download service starts at $30, and the full plans are on the pricing page.
If 429 responses are the main thing stopping you, our dedicated guide to the Wayback Machine 429 Too Many Requests error explains how long blocks last and how to pace a download so it finishes.
Frequently asked questions
Why does my Wayback Machine download keep stopping?
The most likely cause is rate limiting. Slow the request rate, resume the download and retry later instead of restarting from zero.
Can I download a website from a specific date?
Yes. Choose the date on the web.archive.org calendar, then point the downloader at that timestamp. Some tools accept a date range directly.
Why do my downloaded pages look different from the original?
The archive did not capture every file the page used, or the page loaded content with scripts the crawler could not run. Missing assets cannot be recovered from the archive alone.
Is it allowed to download a website from the Wayback Machine?
Downloading your own old website is the common case. Content written by someone else may still be protected by copyright, so get permission before you republish it, and follow the Internet Archive’s terms of use.