Remove Your Photos and Pages from the Wayback Machine

0

πŸ”Ž Reverse Image Search

Image search techniques made simple: upload a photo or paste a URL and search 6 engines at once. 100% free, nothing stored.

πŸ”’ Your image is never stored on our servers longer than 24 hours and is never shared.

You deleted the page. You took the photo down. Yet there it still is, an old copy of your page, photos included, sitting in the Wayback Machine for anyone to open. Deleting the live page does not delete the archive, and that surprises almost everyone who finds their old content there.

To remove a page from the Wayback Machine, email info@archive.org with the exact URLs, the time period to exclude, and the period during which you controlled the site. The Internet Archive reviews the request and, if it agrees, hides those snapshots from public view. There is no web form, and robots.txt alone will not remove anything already archived.

This guide walks through that request step by step: how to find exactly what is archived, what to put in the email, how to check whether it worked, what to do about a single photo rather than a whole page, and when a DMCA notice is the right route instead. It covers archive.org captures only. Removing the same photo from live search results is a separate job, covered in our guide on how to remove your photos from Google.

What is the Wayback Machine, and why does it still have your page?

The Wayback Machine is the Internet Archive’s archive of the public web. It has been saving copies of web pages since 1996, and the Internet Archive announced in October 2025 that it had preserved one trillion web pages. When its crawler visits a page, it stores a snapshot, the page’s text, images and layout as they looked on that date, and anyone can later open that snapshot at web.archive.org.

That is why deleting a page changes nothing in the archive. The live page and the archived copy are two different things, stored by two different organisations. Your host controls the live page; the Internet Archive controls the snapshot. The same applies to photos: an image file that was on a captured page is stored as part of that capture, and it stays there after you remove it from your site.

Snapshots also get made in ways you may not expect. The Archive’s own crawler finds pages by following links, but any person can also save a single page on demand through the Archive’s “Save Page Now” feature at web.archive.org. According to the Internet Archive’s Help Center, Save Page Now saves that one page only, not the whole site, and does not add the URL to future crawls. There is also a delay: the Help Center states there is a 3–10 hour lag between a site being crawled and the capture appearing in the Wayback Machine.

How do I remove a page from the Wayback Machine?

There is one official route: an exclusion request by email. The Internet Archive’s Help Center, on its “Using the Wayback Machine” page, says: “If you would like to submit a request for archives of your site or account to be excluded from web.archive.org, send us a request to info@archive.org and indicate” the URLs, the time period to exclude, and the period during which you had control of the site or account.

Three things about that route matter before you write anything. First, there is no web form and no account dashboard for removals, email is the whole mechanism. Second, the Archive reviews each request and, in its own words, “do[es] not make any guarantees beforehand about the outcome of a request”. Third, the Archive publishes no turnaround target, so do not plan around a date. Other people’s firsthand reports suggest replies arrive after days to about a week, but that is their experience, not a promise.

One more distinction matters: an approved request hides the snapshots from public view; it does not necessarily delete the underlying data from the Archive’s internal storage. So the honest way to describe the outcome is “excluded” or “hidden”, not “deleted”. If you need outright deletion, for example under a court order or a privacy law, say so explicitly in the request rather than assuming the standard exclusion does it.

How do I send the exclusion request, step by step?

Work through the steps in order. The request is much stronger when every URL and date in it is exact, because the Archive’s reviewers act on what you list, nothing more.

  1. List every snapshot first. Go to web.archive.org and type the page’s URL into the search box. The calendar view shows every capture date. Click through the captures that matter and note their dates. Do this for each URL you want excluded, including image files, which have their own URLs.
  2. Decide the scope. You can ask for one page, several pages, a whole directory, or a whole site. Be specific: “all captures of https://example.com/old-page/ between 1 January 2021 and 31 December 2023” is actionable; “remove my site” is not.
  3. Note the period you controlled the site. The Archive asks for the time period during which you had control of the site or the relevant account. If you bought the domain in 2022, say so, it stops the request being read as a claim over captures from before you owned it.
  4. Gather your evidence. If the request is about your own content, have proof ready: domain registration records, hosting invoices, or the original files. You do not need to attach everything, but the Archive may ask, and having it ready avoids a second round of emails.
  5. Write the email using the template below. One email can cover several URLs. Keep the subject line plain and factual.
  6. Send it to info@archive.org from an address connected to the site, for example, the address on the domain registration or the site’s contact address. A request from an unrelated address is weaker and slower.
  7. Wait, then verify. Do not send a second request the next day. Give it at least a week, then run the verification steps in the section below. If a capture is still visible after several weeks, reply to the same thread rather than starting a new one.

What should the exclusion email say?

Below is a copy-ready template built from the Internet Archive’s own list of what a request should include. Replace the bracketed text with your details, and delete any line that does not apply.

Subject: Exclusion request, [your domain or page URL]

Dear Internet Archive team,

I am writing to request the exclusion of archived material from web.archive.org.

URLs to exclude:
[Full URL 1, e.g. https://example.com/old-page/]
[Full URL 2, e.g. https://example.com/wp-content/uploads/2021/05/photo.jpg]

Time period to exclude: [e.g. all captures, or captures between 1 January 2021 and 31 December 2023]

Period during which I controlled the site: [e.g. March 2020 to the present]

Reason: [e.g. “I own this site and the pages have been deleted from the live site. The archived copies contain photographs of me that I no longer wish to be publicly available.”]

Evidence of control: [e.g. “The domain is registered in my name; I can provide registration records or hosting invoices on request.”]

Please confirm once the exclusion has been applied. Thank you for your help.

[Your full name]
[Your email address]
[Your relationship to the site, e.g. site owner]

What to include, checklist

ItemWhy the Archive needs itDone?
Exact URL of every page or imageReviewers act only on the URLs you list☐
Time period to excludeStops the request being read as “everything, forever”☐
Period you controlled the site or accountShows you are entitled to ask☐
Reason in one or two sentencesHelps the reviewer judge the request☐
Proof of control, or an offer to provide itAvoids a second round of emails☐
Contact address tied to the siteConfirms the request is genuine☐

How do I check the removal worked?

Do not take silence as confirmation. Check it yourself, in this order:

  1. Open the snapshot URL directly. An excluded capture returns the message: “Sorry. This URL has been excluded from the Wayback Machine.” That message is the confirmation.
  2. Check the calendar view. Go to web.archive.org/web/*/your-page-url and confirm the captures for the excluded period no longer appear.
  3. Check each image URL separately. A page exclusion does not always cover every image file that was captured with it. Open each image’s archived URL and confirm it shows the same exclusion message.
  4. Re-check a week later. Exclusions sometimes take time to show across the Archive’s systems. One check on the day you hear back is not enough.
  5. Check future crawls. An approved exclusion usually also stops the Archive crawling that URL again. Open the live page’s calendar view a month later and confirm no new captures have appeared.

If a capture is still visible after several weeks, reply in the same email thread, list the exact snapshot URLs that remain, and ask for an update. Starting a fresh request can slow things down, because the new request has no link to the first one.

Can robots.txt remove pages from the Wayback Machine?

No, not pages that are already archived. This is the most common misunderstanding in this area, and the Internet Archive changed its position on it in 2017.

Before 2017, the Archive honoured robots.txt files for both crawling and display, much like a search engine. In April 2017 the Archive explained on its blog that “robots.txt meant for search engines don’t work well for web archives”, and that it was moving away from using robots.txt to decide what to show. The Archive had already stopped referring to robots.txt files on US government and military sites a few months earlier, and said it was “now looking to do this more broadly”. Its advice to site owners who wanted material excluded was the same then as now: send an exclusion request to info@archive.org.

The old method people still quote, blocking a crawler called ia_archiver in robots.txt, is dead for a second reason. ia_archiver was Alexa Internet’s crawler, not the Internet Archive’s, and Amazon shut Alexa Internet down on 1 May 2022. A robots.txt line naming it now addresses a crawler that no longer runs. The Archive’s current crawler uses the user-agent archive.org_bot.

That leaves robots.txt with a narrow, forward-looking role only. A robots.txt block may signal the Archive not to crawl a page in future, and the Help Center still notes that some sites “may have been excluded… due to a robots.txt file”. But it does not guarantee future non-crawling, and it does not retroactively remove anything already saved. The email request is the only mechanism that removes existing snapshots.

If you still want the belt-and-braces version, block both user-agents in robots.txt, but do it as a complement to the email request, never as a substitute. And remember that server-level blocks do not stop a third party saving your page through “Save Page Now”, because that is a person asking the Archive to save a page, not a crawler visiting your server.

What if it is one photo, not a whole page?

The same email route covers individual images, because every image file has its own URL and its own captures. List each image URL separately in the request, for example, https://example.com/wp-content/uploads/2021/05/family-photo.jpg, with the same time period and control details. Do not assume that excluding the page automatically excludes every image that appeared on it; check each image URL afterwards, as described above.

Before you write the request, find out where else the photo lives. An archived copy is often only one of several copies. Run a reverse image search on the photo to find other sites using it, our guide to finding out if someone is using your photos online walks through that check, and deal with each copy on its own terms. The Archive request removes the archived copy; it does nothing about the same photo on a live site, in a search index, or in another archive such as archive.today.

Also consider whether the photo is the problem or the page is. If the image appears in dozens of captures across many pages, a whole-site or whole-directory exclusion may be cleaner than listing every image URL one by one. If it is a single photo on a single page, the single-URL request is the tidier option.

When should I use a DMCA notice instead of an exclusion request?

Use the plain exclusion email when the issue is your own site, your own photos, or personal material you want out of the public archive. Use a DMCA notice only when you own the copyright in the archived material and someone else’s archiving of it infringes that copyright.

The difference is legal, not just procedural. The Internet Archive’s Help Center, on its Rights page, states: “If the Internet Archive is made aware of content that infringes someone’s copyright, we will remove it per our Copyright Policy.” A DMCA notice is a formal legal notice: it must identify the copyrighted work, identify the infringing URLs, and include the good-faith and perjury statements the law requires. It is not a general privacy or embarrassment route. If the photo is of you but you do not own its copyright, the plain exclusion email is the right channel; UK and EU readers can also cite GDPR erasure in that same email.

There is also a counter-notice process. If material is removed after a DMCA notice and the person who posted it files a valid counter-notice, the Archive may restore it after 10–14 days unless the copyright owner sues. That is why the DMCA route is worth using only when the copyright claim is solid. For a full walkthrough of the DMCA process for photos, see our guide to DMCA takedowns for stolen photos.

What the exclusion request cannot do

What you might expectWhat actually happens
Removes the live pageNo. The live page is on your hosting; delete it there.
Removes the photo from Google or BingNo. Search removal is a separate request to each search engine.
Removes copies in other archivesNo. archive.today and other archives need their own requests.
Deletes copies people already savedNo. Files downloaded from the archive are out of the Archive’s control.
Stops anyone re-saving the pageUsually stops future crawls, but a person can still try “Save Page Now”.
Guarantees a resultNo. The Archive reviews each request and makes no promises in advance.

The Google point deserves emphasis, because the two removals are so often confused. Removing a page from the Wayback Machine does not remove it from Google’s index, and removing it from Google does not remove it from the Wayback Machine. They are separate systems with separate request processes, and you need to do both if you want the content gone from both. If the live search result is your problem, start with our guide on how to remove your photos from Google.

How do I stop the Wayback Machine archiving my pages in future?

Once an exclusion is approved, the Archive usually stops crawling the excluded URLs, so the request itself is the main preventive step. For pages you have not yet had archived, you have three additional options, each with limits:

  • Robots.txt: disallow the Archive’s current crawler, archive.org_bot, and the legacy ia_archiver name. This is a request, not a lock, and as explained above, it removes nothing already saved.
  • Server-level user-agent blocks: block archive.org_bot at the server or through a service such as Cloudflare. Stronger than robots.txt against crawlers, but it still cannot stop a person saving the page through “Save Page Now”.
  • Keep sensitive pages off the public web: the only reliable prevention. Anything publicly reachable can be saved by someone, whether by a crawler or by hand. Pages behind a login are not crawled.

For a fuller prevention plan, including watermarking, hotlink protection and monitoring for reuse, see our complete guide to protecting your photos online, and our guide to protecting your photos from being stolen.

Worked example: we checked our own site, and found nothing archived

On 10 November 2026 we ran the check in this guide against our own site, imagesearchtechniques.co.uk, to show what the process looks like in practice.

First, the homepage. We opened the Wayback Machine calendar view for https://imagesearchtechniques.co.uk/ and for the http and https variants. Every one returned the same message: “The Wayback Machine has not archived that URL.” No calendar grid appeared, and no capture dates were shown, zero captures for 2026, and no earliest or latest date to report. The direct snapshot URL, web.archive.org/web/2026/https://imagesearchtechniques.co.uk/, gave the same result.

Second, an old page. The site’s former guide page, /image-search-techniques-guide/, was redirected to the main guide in November 2026. Its calendar view returned the same message: “The Wayback Machine has not archived that URL.” No captures were shown for it either.

Third, we cross-checked with the Archive’s own CDX search API, which returned no records for the homepage, the old guide page, or a banner image file. A wildcard listing of all archived pages under the domain failed differently, the page displayed “Wayback Machine failed to return archive information”, which is a backend error on that view, not a capture count, and it does not change the calendar findings.

The honest conclusion: as of 10 November 2026, the Wayback Machine holds no snapshots of this site, so there is nothing to exclude and no email to send. That is a real outcome, not a failed test, the check did its job. If the calendar had shown captures, the next step would have been to list their dates and send the template email above for exactly those URLs.

Two caveats from the same test. A zero result today is not a guarantee for tomorrow: the Archive’s own Help Center notes a 3–10 hour lag between crawling and display, and a site the crawler has not visited yet can be captured later. Re-run the calendar check every few months if the content matters to you. And a failed view is not a result, when the wildcard listing errored, we did not treat it as evidence of anything; we relied on the calendar views that loaded cleanly.

FAQs

How long does it take to remove a page from the Wayback Machine?

There is no published turnaround time. The Internet Archive reviews each exclusion request individually and makes no promises in advance. Other people’s firsthand reports suggest replies arrive after days to about a week, but that is their experience, not a guarantee. Give it at least a week, then check the snapshot URL for the exclusion message.

Can I remove someone else’s page from the Wayback Machine?

No. The exclusion route is for material from a site or account you controlled, and the Archive asks for the period during which you had control. If the page holds your photo or personal data but belongs to someone else’s site, explain that and ask what the Archive needs. Copyright owners can use a DMCA notice instead.

Does deleting my website remove it from the Wayback Machine?

No. Deleting the live site removes the live pages only. Archived snapshots are stored separately by the Internet Archive and stay publicly viewable until an exclusion request is approved. You must send the request to info@archive.org even after the live site is gone, listing the URLs and the period you controlled the site.

Will the Wayback Machine re-archive my page after it is excluded?

Usually not. An approved exclusion generally stops the Archive crawling that URL again, so new captures should not appear. Check the calendar view a month later to confirm. A person could still try to save the live page through Save Page Now, so keep the live page deleted or protected if you want the content to stay out.

Ali Butt is the lead writer and SEO specialist at Image Search Techniques, where he covers reverse image search, visual search, and online image verification. With over four years of experience in SEO and content, he writes practical, hands-on guides that help readers trace a photo to its source, identify people, products, plants and brands from a picture, protect their own images online, and spot catfish, fakes and AI-generated images across Google, Yandex, Bing, TinEye and more.

Leave A Reply