Image cloaking tools compared

Two of these protect your face. The third protects artwork.

Glaze gets compared to Fawkes because it came out of the same lab and works by a similar mechanism. It solves a different problem. If you are trying to stop a face-search engine matching your headshot, only two of the three are candidates.

Use case

Fawkes and LowKey are both adversarial perturbation tools aimed at face recognition.

Use case

Glaze perturbs artwork so image generators struggle to learn a visual style. It is not a face tool.

Use case

All three share the same limitations, and those decide more than the choice between them does.

Glaze is not really in this comparison, and that is the most useful thing to know

Glaze and Fawkes both come from the University of Chicago SAND Lab, both add a perturbation that is meant to stay below the threshold of ordinary human perception, and both get filed under the same heading in articles about protecting yourself from AI. That is where the similarity stops.

Glaze protects an artist’s visual style. The perturbation is designed to interfere with an image-generation model learning and reproducing how someone paints, so that training on their portfolio produces something that does not look like their work. It is available as a desktop application and as WebGlaze, a free invite-only hosted version processed on the project’s own GPU servers.

It does nothing for face matching. If your problem is that a public headshot is turning up in a face-search engine, Glaze is the wrong tool, and running your photo through it will not help no matter how many times you do it.

Fawkes and LowKey are the comparison that actually exists

Both are academic projects and both attack the same step. A face-recognition system converts a face into an embedding — a list of numbers describing its geometry — and decides whether two photos are the same person by comparing embeddings. Fawkes and LowKey both compute a perturbation that makes the model extract a substantially different embedding from your photo than it otherwise would, while leaving the image looking like your photo to a person.

The commonly reported difference between them is visibility. LowKey’s alterations tend to be more noticeable than Fawkes’. Whether that is a problem depends entirely on what the photo is for: on a professional headshot it matters a great deal, and on a photo where you care more about protection than polish it matters much less.

There is no single best tool here, and anyone presenting one as the winner is skipping the actual axis. Protection strength and visual fidelity trade against each other, both tools expose that tradeoff through settings, and where you want to sit on it is a judgement about the specific image rather than a fact about the software.

The limitations are shared, and they matter more than the choice

None of them is retroactive. Cloaking changes the file you cloak, at the moment you cloak it. Copies of your face already indexed by a face-search engine are completely unaffected, and getting those out of results is a separate process of opt-out and removal requests to each engine.

Recompression degrades all of them. Platforms resize, re-encode and strip metadata from photographs on upload, and the perturbation lives in exactly the fine detail that compression discards. This is a known limitation of the whole category rather than a weakness of any one tool, and it is the one that gets mentioned least.

One clean copy undoes the work. If the unprotected original is published anywhere — an older profile, a press page, a colleague’s post — an indexer has an uncloaked reference and the cloaked version does not help.

And none of it is permanent. Detection is plausible in principle, because the perturbations follow patterns a system expecting them can look for, and reversal is an active area of research. The honest framing, which is the one the researchers who built these tools use themselves, is that cloaking raises the cost and unreliability of matching rather than guaranteeing anything.

Choosing, in practice

If you are protecting a professional headshot and the image has to look untouched, the lower protection modes of Fawkes are the conventional answer, and they are what this service runs.

If you are comfortable in a terminal and have more than a couple of photographs to handle, run Fawkes yourself. It is free, it is from the researchers who invented the technique, and your photo never leaves your computer — which on the privacy axis specifically is strictly better than any hosted service, including this one. Paying for a browser upload makes sense when you want one photo handled in about a minute without installing a Python environment and downloading model weights.

If you are an artist protecting a style rather than a face, the tool is Glaze, and it is not ours.

Guide

Work out which problem you have first

1

Name the thing you are protecting

A face that a search engine should not match, or an artistic style a generator should not learn. Different problems, different tools, no overlap.

2

Deal with what is already indexed

If copies of your face are already in a face-search engine, no cloaking tool reaches them. That is an opt-out and removal job, and it runs on a timescale of weeks.

3

Cloak the file you publish next

Protection applies going forward, to the specific file you protect. Keep the unprotected original somewhere private rather than published alongside it.

FAQ

Frequently asked questions

Is LowKey better than Fawkes?

There is no general answer, because the two are not ranked on a single axis. The commonly reported tradeoff is that LowKey alters the image more visibly, which buys protection at the cost of how untouched the photo looks. If the photo is a professional headshot that is usually the wrong trade; if it is not, it may be the right one.

Can I use Glaze on my profile photo?

You can run it, and it will alter the file, but it is not designed to disrupt face matching and should not be expected to. Glaze targets image-generation models learning an artistic style. Using it on a headshot to avoid a face-search engine is using the wrong tool for the problem.

Do I have to pick one?

For a single headshot, the choice between Fawkes and LowKey matters far less than whether the unprotected original is still published somewhere. One clean public copy defeats either of them, so that is the question worth answering first.

Is any of this free?

Fawkes is free and open source from the University of Chicago SAND Lab, and running it locally costs nothing but time and a reasonably patient CPU — cloaking is compute-bound, so expect minutes per image rather than seconds. This site charges for doing the same work in a browser in about a minute, on a machine that is not yours to configure.