Remove photos from PimEyes

How to remove photos from PimEyes and reduce the chance the same headshot shows up again

If you found your face in PimEyes, the immediate job is removal. The follow-up job is preventing the same clean image from staying public and feeding future matches.

Use case

Removal is the urgent step when you already have a live result.

Use case

If the same public headshot stays online, similar results can come back later.

Use case

The durable fix is usually removal plus replacing and protecting the source image you still control.

What you found, and what it actually means

If you searched your own face and found results, what you have learned is that your face is indexed and that at least one public page carries a photograph good enough to match. You have not learned that anyone has looked you up, and the results themselves are not evidence that anything has been done with them.

That is worth saying because the first reaction is usually alarm, and alarm tends to produce the wrong first move — deleting accounts, pulling down profiles, changing photos everywhere at once. None of that removes the indexed results, and some of it makes the next steps harder.

Removal and deletion are different words here

Removal from a face-search engine means you stop appearing in its results. Deletion would mean the underlying photograph is gone from the site that published it. The opt-out processes offered by these engines do the first. Only the site hosting an image can do the second, and whether they will depends entirely on who they are.

So the realistic target is this: break the link between a photograph of your face and a searchable identity, and accept that individual photographs on individual websites are a separate, slower, often unwinnable negotiation.

The order that saves you the most work

Start with removal from the engines, because that is the step with a multi-week clock on it and the step that does the most per unit of effort. File with PimEyes, then FaceCheck.ID, then any other engine that surfaced you.

Only then deal with the supply side: which public photograph of you is the strongest reference, whether it needs to stay published, and what the replacement should be. Doing this first feels productive and achieves nothing, because the old image is already indexed.

What to expect on timing

PimEyes confirms opt-out requests by email, typically in two to six weeks. Other engines run their own timelines. Nothing about this is instant, and there is no escalation path that makes it instant.

During that window your results are still live. If the situation is urgent for safety reasons rather than privacy preference, the engine opt-out is necessary but not sufficient, and it is worth treating the hosting sites as a parallel track rather than a later one.

Guide

Removal plus prevention

1

Locate the source page behind the result

Figure out whether the image comes from LinkedIn, a company bio, an old press page, or another public site you can still edit.

2

Request removal where possible

Follow the current removal path for the service and keep notes on what you submitted and when.

3

Swap the public source image

If the old clean headshot stays live, removal becomes a loop. Replace it with a protected version on the sites you control.

FAQ

Frequently asked questions

Is removing the result enough?

Not usually. If the original image is still public in the same form, other indexes or later crawls can recreate the problem.

What if I cannot control the page where the image appears?

You may need to combine a removal request, direct outreach to the site owner, and changes to any other public copies you do control.

Why scan the source image after I already found a result?

Because the next decision is whether that same image is still too exposed to keep using. The scan helps you decide whether it should be replaced or protected.