Remove images from Google Image search: what works

To remove images from Google Image search, you first remove or block the image where it is hosted, then ask Google to refresh or remove the result. Google lists images from other people's websites but does not own them, so a request to Google changes what Search shows, never what the host publishes.

Image results run on different doors from page results. Google offers separate requests for personal information, explicit or fake imagery, and photos of people under 18, and thumbnails and copies can outlast a page-level fix. This guide sets out which door fits which image, the order of work, and why the same photo can come back. Google's policies are described as of the help pages read for this guide, so check the named page before you file.

The short version

Remove the image at its source first: the platform, the site owner or the host. Google says it usually cannot remove images from sites it does not own.
If you own the site, block the image with robots.txt or a noindex header, or use the Search Console Removals tool for a temporary hide.
If you do not own the site, ask Google to refresh the image once it is gone, or use the personal information, explicit imagery, under-18 or legal request that fits.
A removal covers only the URLs you submit. Copies on other URLs, other sites and other search engines need their own work.

Why images need a different route from pages

Google Images indexes images mainly by crawling pages and reading the image tags on them, and it uses the surrounding text, the file name and the alt text to decide what the image shows. One photo can therefore exist as several results: the image file has an address, and each page that embeds it has another.

Three consequences follow. The image URL and the page URL are different things: Google's steps for refreshing an image tell you to copy the link address from the thumbnail in Google Images, not the page address. Google's image documentation says the thumbnail in results is generated at crawl time, so it can stay in results until Google updates or removes the result. And removal is per URL: for personal information requests, Google says it reviews only the URLs you submit.

About six monthshow long a successful Search Console Removals tool request lasts

Under 18the age limit of Google's policy for non-explicit images of minors

Submitted URLs onlywhat Google reviews in a personal information request

Figures come from Google's Search Console Removals tool help page, its non-explicit minors policy page and its personal information removal page, as read for this guide.

Remove the image at its source first

The durable fix is at the source, because Google says it usually cannot remove images from websites it does not own. Once the file is gone or the page is changed, Google drops the result through its regular updating process, and you can speed that up with a refresh request.

Google's help page for removing an image sets out the order. For a website, contact the site owner through the "Contact us" page or the owner details in a Whois record, and if you cannot reach the owner, contact the hosting company, which Whois also shows. For a social platform, remove the image yourself if you control the account that posted it, or use the platform's report flow, looking for terms such as "Report a photo" or its image removal policy. For photos you uploaded to Google products, delete them through Google Photos or Album Archive.

When you write to a site owner or host, name both the image address and the page address, state the ground in one line (posted without consent, your copyright, a minor), and ask for deletion of the file, not only the page.

A host or platform may refuse or ignore you. If so, the Google routes below are the fallback, and a lawyer is the next step for anything that needs a court order. This guide is information, not legal advice.

If you own the site: remove, block or hide the image

If you control the site, you have three tools, and they behave differently. Google's documentation for removing a site's own images from Search describes them.

Delete the file and return an error. Deleting the image is the simplest result. Google's Removals tool page says that to make a removal permanent you return a 404 or 410 status, require a password, or use a noindex tag.
Block it from crawling or indexing. For a non-emergency removal, Google offers two methods with the same effect: robots.txt rules for the Googlebot-Image user agent, or a noindex rule sent in the X-Robots-Tag HTTP header of each image. The robots.txt rule supports wildcards, and robots.txt rules apply to all search engines.
Hide it fast and temporarily. The Removals tool in Search Console is the emergency option. Google says a successful request lasts only about six months, requests usually process within a day, and approval is not assured. It covers images, and it works only for verified properties.

In a robots.txt file, the Googlebot-Image user agent plus one Disallow line naming the image path blocks that image from Google Images. Using the Googlebot user agent instead removes it from all Google Search results.

If a content delivery network or content management system cannot set robots.txt rules or headers, Google says you may need to delete the images instead.

If you do not own the site: refresh the result after the image is gone

Once the image is deleted at the source, ask Google to refresh the image result so the thumbnail does not linger. Google's refresh outdated content page says to use the tool when content was deleted from a site but still appears in Search. If the live page has already been updated, the page says you do not have to fill out the form.

For an image, the page gives these steps: find the image at images.google.com, right-click the thumbnail and choose Copy link address, then choose Request refresh, New request, Image, paste the link into the URL box and submit. You can check the status in the Refresh outdated content section of Search Console.

The tool is for content that has changed or disappeared, so it does not remove an image still live at the source, and the help page gives no timeline.

Which Google request fits which image

Each request has its own scope. Pick by what the image is, not by how upsetting it is: in our experience, a wrong form usually costs weeks.

Route	Fits an image that is	What it does	Main limit
Refresh request	Already deleted or changed at the source	Updates a stale thumbnail or listing	Does nothing for a live image
Removals tool	On a site you own and verified	Hides the URL for about six months	Temporary unless you also fix the source
Personal information request	An ID, signature, doxxing content or private record	Full or partial removal from Search	Newsworthy or public-interest content may stay
Explicit or fake imagery request	Sexual or intimate, real or fabricated	Removal, plus duplicate detection	Source site is untouched
Under-18 request	A non-explicit photo of a minor	Removes the image from Image Search and thumbnails	Image URLs only, and not from accounts you manage
Legal or copyright request	Infringing or unlawful under local law	Google can restrict access within its own products	A valid notice is required

Personal information and doxxing

Google's personal information policy covers contact details, government ID, bank and card numbers, pictures of a signature or ID, and private records such as medical records. It can also remove doxxing content: personal information combined with threats or calls for harm, or a significant amount of aggregated personal information with no legitimate purpose. You or a representative submit the URLs, with screenshots if useful.

The outcome is full removal, where the page no longer appears in Search at all, or partial removal, where it does not appear for searches containing your name or identifier but may appear for others. Google weighs public interest and whether other people are involved.

Explicit, intimate or fabricated imagery

For sexual images that show you, real or fake, Google has a separate policy and, in Image Search, an in-product Image Viewer removal flow for personal adult content and artificial imagery. Google also says it does its best to find and remove duplicates of such imagery, with an opt-out on the request form. The full flow and the law belong to their own guides. The mechanics that matter here: removal covers only the URLs you submit, and the content may remain at the source.

Images of people under 18

Google has a policy for non-explicit images of minors. The subject can request, or a parent or other representative can start the request. The image must show a person under 18, or who died before turning 18. Google states that the image must show the person the request is for, that it must not come from a social media account or webpage the requester manages, and that submissions must contain only image URLs, because webpages with both text and images are not eligible under this policy. Newsworthy images or matters of public interest may stay.

If approved, the image no longer appears in Google Image Search or as a thumbnail in other Search features. Sexual content showing anyone under 18 is different: Google says anyone can report it through a separate channel, and it must never be screenshotted or shared.

Copyright and other legal routes

If you took the photo or hold the rights, a copyright notice is an option. Google's copyright page says a complete notice needs your contact details, a description of the work, the specific URL of each allegedly infringing item, a good-faith statement that the use is not authorized, a statement of accuracy under penalty of perjury, and a signature. If a valid counter notification arrives, Google forwards it to the person who filed the notice, and the parties resolve the dispute in court.

For content outside Google's own policies, its personal information page points to the Legal Help Center for requests under local law. Google's legal removal page asks for the specific URL, not the home page, and a separate notice for each Google product where the content appears.

Thumbnails, snippets and cached copies after removal

A removal request targets the result, not every copy. Three kinds of stored copy matter for images, and each one is cleared differently.

The thumbnail. Because Google generates it at crawl time, the thumbnail can persist until the result is updated or removed. When the source image is deleted, a refresh request is the way to push the update. When Google approves an under-18 request, it states that the image no longer appears in Image Search or as thumbnails elsewhere in Search.

The page snippet. The Removals tool has a separate "clear snippet" option for site owners, for text left in a result after sensitive text is deleted from a page. It concerns the description, not the image.

Cached and archived pages. These follow their own rules and are outside this guide. A deleted image can survive in places you never requested.

Google says removed content may still exist online, reachable through direct links, social media or other search engines. A successful request makes an image harder to find through Google Images. It does not make it disappear.

Why the same image keeps coming back in reverse-image results

Reverse-image search finds other places where the same photo appears, which is why a removed image seems to resurface. Google's help page says that searching by image can return similar images and websites that have the image or a similar one, so each copy is its own result with its own address.

In most files, an image returns for one of four reasons:

The original was never removed. The result was hidden, but the file is still live at its address and reachable by a link or another search engine.
Copies exist at other URLs. A forum repost, a scraper site, an aggregator and a resized version each have their own address, and a request that named one URL does not reach the others. Google says in a personal information request that it reviews only the URLs you submit.
Another page still embeds it. Google's documentation notes that an image can still be indexed through other pages that embed it, even when one page carries a noimageindex tag.
A new copy appears. Someone saves and re-uploads the photo, creating a new address that Google crawls from scratch.

In an invented scenario with generic parties, a photo is posted on a small forum, copied by an aggregator, and shown as a thumbnail for a name search. A request naming only the forum image removes one result, and the aggregator copy and any resized version stay. List every address, ask each host to delete, file the Google request for each address that remains, then search again after the changes settle. Google's explicit imagery policy shows the contrast: it tries to find duplicates on its own, while the pages read for this guide describe no such sweep for other image types.

The order of work, step by step

The order starts with the cheapest door and ends with the legal ones.

Removing an image from Google Images, in order

Map every addressSearch Google Images and run a reverse-image search with Google's image search tool. For each result, save the image address, the page address and a dated screenshot.
Ask the source to delete the fileWrite to the platform, site owner or host, naming the image address, the page address and the ground. Log the date and any reply.
Block it if the site is yoursDelete the file and return a 404 or 410, or use robots.txt for Googlebot-Image or a noindex header, not both. Use the Removals tool if you need a temporary hide.
Refresh the resultOnce the image is gone, file the refresh request for each image address, copied from the thumbnail in Google Images.
File the matching Google requestIf the image is still live, choose the personal information, explicit imagery, under-18 or legal route from the table, and submit every remaining address.
Check again and repeatRun the search again after the changes settle. Any new address starts the loop from step two.

If steps two and five both fail, the remaining routes are a lawyer's letter, a court order, or leaving the image and building better results around the name, a legitimate answer for accurate, lawful images. Our remove negative content service assesses that on a real file.

What to expect after a request

Google's pages give few timelines. The table sets out what they state and what we usually see; our ranges are experience, never promises.

Stage	What happens	Usual range
Source request	Host or platform reviews and deletes, refuses or does not reply	In our experience, days to several weeks, and some never reply
Removals tool	Temporary hide for a verified site	Google says requests usually process within a day
Refresh request	Google updates the result after deletion	Google gives no timeline; in our experience, check back after days to weeks
Personal information or explicit imagery request	Google reviews the submitted URLs and emails you if it removes a result	Google gives no fixed timeline; in our experience, days to weeks
Reverse-image check	You confirm what remains and which copies are new	Repeat after each wave of removals

A request can end three ways: approved, partly approved for certain searches only, or declined, often because the content is newsworthy, lawful or outside the policy. After a refusal, bring new evidence, pick a route that fits the image, or return to the source. Resubmitting unchanged rarely helps. Do not publicize a pending removal: a thread about the attempt can put the image in front of more people.

The next step: a short audit of what is indexed

Before filing anything, know how many addresses carry the image, who hosts each, and which route applies. If an image is causing harm now, start with the source and the matching Google request the same day.

If this is happening to you now

Collect the image addresses and a dated screenshot, then write to the host before you file with Google. If you want the file reviewed, request a private audit and we will map the addresses, the hosts and the routes that fit.

Reputation Partners handles image removals as part of a wider file, which means checking what the name returns across images, pages and AI answers. For leaked or intimate images, see leak removal.

Questions people ask

Can I remove a picture from Google Images without removing it from the website?

You can ask Google to remove a result in some cases, such as an under-18 image, a personal information request or explicit imagery, but the file stays on the website. Google says it removes content only from Search, and the page can still be reached by direct link or another search engine. For a lasting result, deal with the site as well.

How do I remove an image from Google Images that I uploaded myself?

Delete the file from your site and return a 404 or 410, or block it with robots.txt for Googlebot-Image or a noindex header. For a faster hide, use the Search Console Removals tool on a verified property. Google says its effect lasts about six months unless the source also changes.

Will a request to Google remove images of my child?

Google has a policy for non-explicit images of people under 18, which a parent or representative can start. The image must show the person, must not come from an account or page the requester manages, and the request must contain image URLs only. Newsworthy images may stay. The policy removes the result, not the source file.

Why does my photo still show after Google approved my request?

Most often a copy exists at another address. Approval covers the URLs you submitted, and Google's own pages say removed content can remain reachable elsewhere online. Run a reverse-image search, list every remaining address, deal with those hosts, and submit the leftover URLs.