Face Blur

Boxes you draw, blur you set — check every face yourself, then share the photo.

Checked in a browser on 2026-11-19 · how these tools are tested · runs on your device

You draw the boxes

Automatic face detection misses faces — turned heads, sunglasses, a face at the edge of the frame — and a tool that misses one is worse than a tool that makes you look. Dragging a box over each face takes ten seconds and cannot fail silently.

The blur is applied to the pixels underneath, so the file that leaves this page no longer contains the face. A box drawn over the top would not do that.

    Before you share

    Check the result at full size: a blur that looks convincing in a thumbnail can still leave features readable. If the face must be truly unrecognisable, increase the strength and make the box larger than the face.

      What this page does not do

      The boxes are rectangular, so a face at an angle needs a larger box than the face itself. The blur is applied at full resolution, which means it is still reversible in theory if the original is published alongside it — never publish both.

        How Face Blur works

        Drag a box over each face and blur it before a photo leaves your device. Nothing is detected automatically, so nothing is missed silently. The method behind Face Blur is the single-purpose logic inside wave53.js, and this page shows the result with its assumptions in the open.

        • Open Face Blur and provide face blur — the page accepts it in the field it shows.
        • For Face Blur, the image is decoded into a canvas, processed pixel by pixel, and re-encoded by the browser's own codec.
        • The Face Blur output appears on the page and can be copied or downloaded in the format it offers; nothing is kept afterwards.

        A worked example for Face Blur

        A typical run of Face Blur starts with face blur and ends with the result shown above; the page reports what it did in plain words so the output can be checked against a known-good case before it matters.

        Compare the before/after byte counts the page shows — if the file barely moved, the photo was already compressed and the honest answer is that nothing more can be saved. That check applies directly to Face Blur with face blur.

          When to use Face Blur — and when not to

          Reasonable uses: Preparing photos for a web upload; Fixing orientation or exposure in a hurry; Meeting a file-size limit on a form. Face Blur is deliberately narrow: it does one job and states its assumptions instead of hiding them.

          Desktop editors do more, but they cost money, install updates and still re-encode on export. For a single resize or format change, the page is the shorter path. The honest ceiling for Face Blur: for Face Blur, the browser's codecs decide the quality ceiling.

          • Best case for Face Blur: Preparing photos for a web upload
          • Also fine with Face Blur: Fixing orientation or exposure in a hurry
          • Not what Face Blur is for: for Face Blur, the browser's codecs decide the quality ceiling.

          Reading the Face Blur result

          Dimensions and bytes are different things, and Face Blur reports both so the trade-off is visible rather than silent.

            Accuracy and limits of Face Blur

            The method is the single-purpose logic inside wave53.js. Face Blur prints results at the precision its inputs justify, and the limits below are the honest ones:

            • Face Blur: For Face Blur, the browser's codecs decide the quality ceiling.
            • For Face Blur, very large images are limited by device memory.

            Privacy and speed on the Face Blur page

            The Face Blur page is a static file plus wave53.js; there is no upload endpoint behind it, so your input cannot be stored or logged. Closing the tab discards the work.

            Speed follows the build: Face Blur loads one stylesheet and one script, with no framework, no web font and no tracker. That is why the tool responds as you type instead of waiting on a round trip.

              What you get from Face Blur

              The output of Face Blur appears on this page and can be copied or downloaded in the format the page offers. Nothing is queued, nothing is emailed, and there is no usage counter — the image work finishes the moment the numbers are in.

              Because Face Blur is built from wave53.js rather than a server call, the practical ceiling is your device: memory for large inputs, and CPU for anything that loops over pixels or pages. On a normal laptop that ceiling sits far above everyday use; on an old phone it arrives sooner, and the page tells you when a job is too big instead of failing silently.

                Face Blur is one of the pages that contacts an outside service: cdn.jsdelivr.net for the media engine (loaded once, first time you use a media tool). The request is sent only when you press the button, it carries no personal data, and the page says so in its own text.

                Questions

                What does Face Blur do?

                Drag a box over each face and blur it before a photo leaves your device. Nothing is detected automatically, so nothing is missed silently. Everything runs in your browser; nothing is uploaded.

                How accurate is Face Blur?

                The method is the single-purpose logic inside wave53.js. For Face Blur, the browser's codecs decide the quality ceiling.

                What are the limits of Face Blur?

                For Face Blur, very large images are limited by device memory.

                Is anything uploaded when I use Face Blur?

                No. Face Blur runs entirely in the browser tab; nothing is uploaded, stored or logged.

                Can I use Face Blur offline?

                Yes — Face Blur keeps working offline once the page has loaded; the whole tool is a local script.

                Keep going

                More image tools