Guide
What the Wayback Machine can’t restore: database, forms, search and more
The Wayback Machine keeps what a crawler saw from the outside: the HTML of each page and the files that page loaded when it was captured. Anything that lived only on the server is not in the archive: the database, user accounts, form handling, site search, private pages. Below is the full list, why each item is missing, and what you can do instead.
By Dmitriy Gabdrakhmanov · Updated 9 October 2026
Why the archive has these gaps
The archive works like a visitor with no password. Its crawler requests a public address, stores the response and moves on. It never sees the server behind the page, never logs in, never fills in a form, and only follows links it can find. Three consequences follow:
- Only public, linked pages are captured. A page nobody linked to, or one behind a login, was never requested.
- Every address is captured on its own dates. The homepage may have hundreds of captures, a deep post one or none.
- Some sites are excluded. A site owner can block the crawler or ask the archive to remove captures. Those pages are not available, even if they once were.
Everything below is a variation of these three rules.
The database: users, orders, settings
What you see on an archived page survives as HTML: the text of a post, the product description, the comments that were shown. The database those pages were built from does not. That means none of these come back:
- User accounts, passwords and roles
- Orders, customers and payment records
- Drafts, private posts and scheduled posts
- Site settings, plugin settings and anything stored only in the admin
What to do instead
Rebuild the content from the archived HTML, then recreate what lived in the database. Users register again or are re-invited. Shop products can be re-entered from the archived product pages, but past orders are gone. Before you start, ask your old hosting company for a backup: many keep copies for weeks after an account closes, and a real backup beats any archive.
Forms: contact, sign-up, checkout
The archive saves how a form looked: its fields, labels and button. It does not save what happened after someone pressed Send. That part was a script on the server, which emailed the message or saved the sign-up. In an archived copy, the button leads nowhere or to an error.
What to do instead
Keep the form as a picture of the original or connect a new one. In WordPress that is a form plugin and a few minutes of setup per form. In my restorations, forms stay visible with sending switched off, so the page looks as archived and nothing is sent to a dead address; reconnecting them is your choice after delivery.
Site search
Search results are built on request from whatever the visitor typed. The archive only holds the few result pages its crawler happened to fetch, for queries someone linked to. The search box itself is just a form, so it has the same problem as any other form.
What to do instead
Add a new search to the restored site, or remove the box. In my restorations search is not restored: a search address answers with an empty page instead of an error, and the box can be replaced after delivery.
Pages behind a login and pages nobody linked
Member areas, client dashboards, account pages, carts and the WordPress admin were never seen by the crawler: it does not log in. The same goes for pages that existed but had no links pointing to them, such as old landing pages removed from the menu, or files shared only by email.
What to do instead
Check the full list of captured addresses first. The step-by-step guide shows the one request that lists every address the archive holds for a domain. Whatever is not on that list cannot be restored from the archive and has to be rewritten or dropped. Give each missing address a deliberate answer: a 410 if it is gone for good, or a 301 where the original site already redirected it.
Content loaded by scripts and third-party widgets
Some pages fill in their content after loading: infinite scroll, “load more” buttons, comment widgets from an outside service, social feeds, embedded maps and videos. The crawler often stores the empty frame without the content that arrived later. Embeds from services that still exist may work again on the restored site, because they load from that service, not from the archive.
What to do instead
Open the key pages in the archive viewer and scroll to the bottom. If a block is empty there, it will be empty after restoration. Decide page by page: keep it, replace it with static content, or remove it.
Images, downloads and other files
Files are captured separately from pages and often on different dates. Common gaps:
- Images in a size that was never requested, or captured only in a thumbnail size
- PDFs and downloads that were large or linked from few pages
- Fonts and stylesheets loaded from other domains
- Media added shortly before the site disappeared
What to do instead
Look for each missing file in captures outside your chosen window: the same file is often there a few months earlier or later. What cannot be found is replaced or removed, and the page is checked again. A restoration report should list every file that could not be recovered and why, so nothing goes missing silently.
At a glance
| Item | In the archive? | What you can do |
|---|---|---|
| Page text and layout | In the archive?Yes, as HTML | What you can doRestore on the original URL |
| Images and styles | In the archive?Mostly, with gaps | What you can doSearch other captures; replace what is missing |
| Shown comments | In the archive?As text on the page | What you can doKeep as part of the page |
| Database, users, orders | In the archive?No | What you can doAsk the old host for a backup; recreate |
| Forms | In the archive?Look only | What you can doReconnect with a form plugin, or leave sending off |
| Site search | In the archive?No | What you can doAdd a new search, or remove the box |
| Pages behind a login | In the archive?No | What you can doRewrite or drop |
| Script-loaded content | In the archive?Often missing | What you can doReplace with static content, or remove |
| Pages never captured | In the archive?No | What you can do410, or 301 where the site redirected |
Questions
Can I recover my WordPress database from the Wayback Machine?
No. The archive never had access to the database. It keeps the pages the database produced, so the content can be rebuilt from them, but users, orders, settings and drafts cannot.
Can I get old passwords or user accounts back?
No. Accounts and passwords lived only in the database. After a restoration, users register again or receive new invitations.
Why are some images missing when the page looks fine in the archive?
The archive viewer sometimes fills gaps with a file from another date, or the browser shows a copy from its own cache. A restoration has to find a real capture of every file. When none exists, the image is missing.
Where else can I look if the archive is not enough?
Your old hosting company’s backups, other public web archives, your own computer and email for files you sent or received, and anyone who maintained the site for you. Google’s cached copies are no longer available: Google removed that feature in 2024.
Does a restored site work like the original?
Pages, layout and addresses come back. Server-side features do not: forms, search, logins and anything stored in the database have to be rebuilt or dropped. Knowing that before you start avoids most disappointments.
Next step
Want to know what the archive holds for your domain before you decide? The free audit lists the captured pages, what looks recoverable and what is missing, with a price and a date.