Free face blur
Blur every face in a photo — proposed, then checked
Drop a photograph and the page marks an oval over every head it can find, then asks you to correct the list before it will give you the file: drop the ovals that landed on a hand, drag boxes over the people it walked past, and set how hard each face is covered. It is free, wants no account, and the photograph is decoded in the tab rather than uploaded. The finder is a color-and-shape pass rather than a face model, so it is wrong in both directions and the page is built around that fact instead of hiding it — which is why the download unlocks only when you say you have looked at the frame yourself.
- 100% free
- No signup
- Finds faces itself
- Oval, not a rectangle
- Up to 24 at once
Press Ctrl+V anywhere on the page to drop in a photo copied out of a message thread — no need to click the field first.
How to cover the faces in a photo before it goes up
Detection hands you a draft; correcting it is yours, and no setting on the page does it for you.
Drop the photo and read what came back
The finder runs the moment the picture decodes and numbers every oval it proposes, up to twenty-four. It is looking for connected regions whose color sits in the chrominance window skin occupies and whose bounding box has roughly the proportions of a head — not for eyes, not for a face model. Treat the numbered ovals as a first draft written by something that has never seen a face, because that is what they are.
Correct the draft in both directions
Over-reach is the easy half: an oval on a bare forearm, a wooden door or a terracotta pot gets dropped from the list in one click. The half that matters is what is missing — a head turned away, someone in sunglasses, a child low in the frame, the two people at the back whose faces merged into one blob. Drag a box over each of those and it joins the list as yours. Bigger and Smaller resize a proposal by a quarter and a fifth around its own center when the crop is close but wrong.
Set the strength, then unlock the download
The blur deviation, or the block size, is each face's shorter side divided by the number on the slider, so a head 40 pixels across in the background gets proportionally the same treatment as one 300 pixels across at the front. The download is disabled until the line under the picture is ticked, and ticking it is undone by any later change to the list, the strength or the photo. That is deliberate: an automatic finder that misses somebody is only safe if a person looks afterwards.
Technical specifications
| Finder | A 192-cell-wide grid averaged in linear light, then a skin chrominance window of Cb 77–127 and Cr 133–173 with a luma floor of 40, then connected regions |
|---|---|
| Shape tests | Bounding-box aspect 0.55–1.65, region filling at least 45% of its box, width under 92% of the frame |
| Proposals returned | Up to 24, largest first |
| Browser detector | The Shape Detection API's FaceDetector is used where a browser exposes it, which today is almost nowhere; the shape pass is the fallback that actually runs |
| Covering | An ellipse inscribed in each box, blurred by five box passes per axis or filled with blocks |
| Strength | Face's shorter side divided by 4 to 20, default 8, shown as a deviation in pixels per face |
| Ovals left alone | Any whose shorter side is under 12 pixels; they are named in the table rather than silently covered |
| Photo capped at | 2,048 pixels on the long side, the size a social network stores anyway |
Frequently asked questions
Why did it miss one of the faces?
Most likely because the face broke one of the three shape tests rather than because it was not detected as skin. A head turned to profile against a bare shoulder joins that shoulder into one blob whose proportions are no longer head-shaped; sunglasses or a heavy beard split the skin region in two so neither half fills enough of its own bounding box; two people standing cheek to cheek merge into a single wide region and are rejected for being too wide. Small faces are dropped on purpose, because a region under about a sixth of a percent of the frame is more often a hand than a head. All four are why the list is a proposal and the download needs a tick.
Why is there an oval on someone's hand?
Because a hand is made of skin and a cupped hand is roughly as tall as it is wide, which is the whole of what the finder tests. The same goes for a forearm at the right angle, a terracotta pot, a varnished wooden door, a slice of ham and a great deal of desert. This is the known cost of chrominance-based skin detection and it is the safe direction to be wrong in — an extra oval is one click to remove, whereas a missing one is only found by the person in the photograph.
Does blurring a face make somebody unidentifiable?
No — it makes the face unreadable, which is a smaller claim. Identity in a photograph is carried by a great deal besides the face: build, hair, posture, clothing, a tattoo, a walking stick, the room, the other people present and whatever the caption says. Recognition systems also do measurably better than chance on blurred faces, because a blur removes high-frequency detail and leaves the coarse geometry the model actually leans on. If the requirement is that a person cannot be placed at all, a blurred face in a photograph that names the venue and the date does not meet it.
Why an oval instead of a rectangle?
Because a head is closer to an ellipse than to a box, and the corners of the box are where the background lives. Filling a rectangle takes out the wall, the shoulder and the hair behind the ear along with the face, which is both uglier and more obvious. The ellipse is inscribed in the box you see, so growing the box grows the oval, and the blur inside it samples only from within that box — the covered region is computed from itself rather than from the photograph around it, which keeps a hard, visible boundary instead of a soft halo that makes it unclear what was treated.
Can a blurred face be sharpened back?
A blur is a convolution, and convolutions are in principle invertible, so the honest answer is that recovery is limited by noise rather than forbidden by mathematics. In practice it depends entirely on strength: at a deviation of a twentieth of the face there is plenty of structure left and a sharpening pass gets a usable amount of it back, while at a quarter the detail has fallen under what an 8-bit channel can still represent and there is nothing to amplify but rounding error. The slider on this page runs across that whole range on purpose, which is why the number it shows is a real deviation in pixels rather than a word like medium.
Why must I tick a box before I can download?
Because the failure mode of an automatic face blur is silent and one-sided. A tool that covers four faces out of five in a group shot produces a picture that looks handled, and nobody counts. The tick is the page declining to let the finder be the last thing that looked at the photograph, and it clears itself whenever the list, the strength or the picture changes, so it can never be a stale confirmation of an older set of ovals.
Does the finder work as well on every skin tone?
No, and the shortfall is in the method rather than in this implementation. The chrominance window it uses was published in 1999 from a limited set of subjects, and windows of that kind are known to under-detect very dark skin, which sits below the brightness floor, and very light skin under warm indoor light, which drifts out of the red-difference band. Anything strongly colored by the lighting — a stage wash, a sunset, a screen lighting a face blue — moves a face out of the window as well. Assume the proposals will be least complete exactly where it matters most, and drag the boxes yourself.
About automatic face finding, and why it proposes rather than decides
There are two honest ways to build this page and a dishonest one. The dishonest one is to run a weak detector, cover what it finds, and hand back a file as though the job were done — which produces a picture that looks handled and has a stranger’s child still legible at the edge of it. The first honest option is to ship a trained face model, and it is a real option, but it costs a megabyte or two of weights downloaded to a page whose entire promise is that the photograph never goes anywhere, and it would still miss people; every published face detector has a false-negative rate, and the ones that perform worst are the crowded, badly lit, obliquely angled photographs that people actually want anonymized. The second is what this page does: run something cheap and transparent, say plainly what it is, and make a person sign off the result. A finder that is honest about being incomplete is safer than one that is quietly incomplete, because only the first one prompts anybody to look.
What runs is a classical pass, and knowing its shape tells you where it will fail. The picture is averaged down to a grid 192 cells across, each cell is converted to luma and the two chrominance channels, and cells landing inside a published window for skin — blue-difference 77 to 127, red-difference 133 to 173 — are marked. Marked cells that touch are joined into regions, and a region survives only if it is large enough, if its bounding box is between roughly square and clearly taller than wide, and if it fills at least 45% of that box. That last test is what a pair of sunglasses breaks, by splitting one region into two sparse ones. Two faces pressed together break the aspect test by becoming one wide region. A profile against a bare shoulder breaks both. And the window itself was published in 1999 from a limited set of subjects: it under-detects very dark skin, which falls under the luma floor, and skin under strongly colored light, which drifts out of the band altogether. Those are not this implementation’s bugs to fix — they are the method, and the reason the tick exists.
One thing worth saying about what blurring a face buys you, since the query that brings people here is usually about safety. Covering a face removes the face; it does not remove the person. Clothing, build, hair, the room, the other people in the shot and the caption underneath all survive, and recognition systems do considerably better than chance on blurred faces because a blur strips fine detail and leaves the coarse geometry those systems weight most heavily. For a short high-contrast subject the arithmetic is sharper still and there is a page for it: the license plate tool works out the minimum strength from the size of what is being covered and refuses anything weaker. If what you want is a covering that provably keeps nothing at all, use a solid fill on the redaction page, which also flattens the result into the exported pixels. And if the whole frame is the subject rather than the people in it, pixelating it gives you the block size directly, while dithering and the ASCII generator abstract a picture without pretending to conceal anything in it.
Product and company names shown here are the trademarks of their respective owners. Photo2Pattern is an independent tool and is not affiliated with, sponsored by or endorsed by any of them.
Where the photograph and the ovals live
Your picture is opened by JavaScript running in the tab you are reading this in. It is never uploaded, never sent to a server and never stored anywhere — there is no upload step to undo, because there is no upload. Close the tab and nothing of it remains.
The finder runs on the same decoded pixels, in the same tab, and the boxes it proposes are ordinary state — there is nothing to opt out of, because there is nothing collecting faces to opt out of.