Blur Part of an Image

Blur or pixelate a face, license plate or private detail in a JPG, PNG or WebP photo in your browser. Free, private, batch support.

🌐 Español

Drop your files here (.jpg, .jpeg, .png, .webp)

🔒 Private by design: your files are processed locally in your browser and never uploaded to any server.

A 3x3 grid instead of a drag rectangle

The area control here is not a selection you draw. The image is divided into three columns and three rows, and you choose one of those nine cells, or Whole image to cover the lot. The dividing lines are computed from the photo’s own pixel dimensions and rounded so that the three cells always add back up to the exact width and height, with no seam and no overlap, whatever the size of the source.

A cell is therefore about a third of the frame in each direction, give or take a pixel of rounding, which is generous. A face in the top right of a group shot, a plate in a bottom corner, a monitor behind someone in the middle of the frame: all of those are covered comfortably. The case where this design shows its limits is a small detail sitting across the boundary between two cells, and the honest fix is either to take the redaction up to Whole image or to use a tool with a real drag rectangle.

Soft haze or hard mosaic, and what the strength number means

Effect picks between Blur (soft) and Pixelate (mosaic/censor blocks), and Strength (blur radius / mosaic block size in px) means something different to each, which is why the label carries both names. It accepts 2 to 50 and starts at 15.

Because that number is in source pixels, the same setting is not equally strong on every photo. Fifteen pixels of blur across a 4000 pixel wide camera file covers far less of a face than fifteen pixels across a 600 pixel wide screenshot. Check the output at full size rather than trusting the default, and raise the strength if any structure is still legible.

The blur is produced by blurring a copy of the entire image on a scratch canvas and then pasting back only the cell you selected. That detail is visible in the result: the blur samples real neighbouring pixels from outside the cell, so the redacted area does not fade towards an empty edge the way a blur computed on an isolated rectangle would.

The redaction is permanent, and the format survives

Both effects overwrite pixels. Blur replaces the region with smeared values, pixelate replaces it with flat tiles, and in each case the original detail is gone from the output file. That is unlike drawing a black rectangle in a document or a slide, where the covering shape is a separate object anyone can drag aside. Nothing is layered here, and nothing is recoverable from the download.

The file you started with is not modified. The tool reads it, works on a canvas in memory and hands you a new file named after the original with -blurred before the extension, so keeping or deleting the unredacted original is a decision you make deliberately.

The output keeps its source format, so a JPG comes back JPG, a PNG comes back PNG and a WebP comes back WebP. No quality value is passed to the encoder, which means the browser’s own default applies for the lossy formats. And because the whole image is re-encoded from canvas pixels, there is nothing in this path that copies the source file’s metadata block across. If the metadata is the thing you are worried about rather than the picture, the EXIF remover does that job on JPG and PNG files, and the EXIF viewer shows you what a photo is carrying before you decide.

Redacting a batch, cell by cell

  1. Drop your JPG, PNG or WebP photos into the box, or click Choose files. A batch is fine.
  2. Pick the cell under Area to blur, or choose Whole image.
  3. Pick the Effect, then set the strength.
  4. Click Blur Part of an Image and download each result.

One run applies one cell, one effect and one strength to everything in the batch, so a set of photos where the sensitive detail sits in different places needs one run per group. Files dropped in after a run has finished are ignored until you click Process another, which clears the list.

Where the grid is the wrong shape for the job

Two cases fall outside what a single cell can express: a detail straddling a boundary, and several separate details scattered around the frame that you would rather not cover with a whole-image blur. For both, the screenshot annotator is the better fit, because it lets you drag blur or pixelate boxes exactly where you want them, as many as you need, on top of the same redaction code this page uses. The rest of the image tools cover the ordinary crops and conversions around a redaction.

See it in action

Screenshot of the Blur Part of an Image tool with sysfenix-sample.png (466 KB) loaded, Area to blur set to Center, Effect set to Blur (soft)
Blur Part of an Image mid-process: sysfenix-sample.png (466 KB) loaded, Area to blur set to Center, Effect set to Blur (soft).
Screenshot of the Blur Part of an Image result screen showing sysfenix-sample-blurred.png ready to download (428 KB, 8% smaller)
The finished result: sysfenix-sample-blurred.png ready to download (428 KB, 8% smaller). The download link is a local blob URL — the file never leaves your device.

Frequently asked questions

Can I blur two different corners of the same photo in one run?

Not in a single run, because a run applies one cell to every file in the batch. You can run the same photo twice, feeding the output of the first pass back in as the input to the second, since a redacted file is still an ordinary JPG, PNG or WebP. Each pass re-encodes the whole image, so on a JPG that is a second generation of loss across the parts you did not touch.

Does the strength number mean the same thing for blur and for pixelate?

No, which is why the field names both. For blur it is a radius in pixels, and raising it spreads each pixel's influence further so the area becomes a smoother wash. For pixelate it is the width of one mosaic tile, so raising it produces fewer and larger blocks. A radius of 15 and a block size of 15 do not obscure the same amount of detail, and a small block size can leave a face readable in a way the same number as a blur radius would not.

What happens to a batch if one of the photos will not open?

The run stops there. Each file is processed in sequence with no individual safety net, so a corrupt or truncated image ends the whole run and leaves nothing to download, including the files that had already been redacted. Remove the suspect file and run the rest again. Cancelling mid-run also keeps nothing.

Can a pixelated face be reconstructed by software?

The pixel data is genuinely gone from the file, so nothing can be read back out of it. What is not impossible is a guess from outside. Someone who already holds a short list of candidate faces or plates can pixelate each candidate the same way and compare the results, which is a matching attack against a known shortlist rather than a recovery of your image. A larger block size, or covering more of the surrounding area, makes that far less useful.

Does the redacted file keep the original dimensions?

Yes. Nothing is scaled, cropped or resized. The canvas is created at the source image's own pixel dimensions, the entire photo is drawn onto it, and only the chosen region is overwritten. The byte size can still differ from the original in either direction, because the file is written fresh by the browser's encoder rather than patched in place.

Which effect is less conspicuous in a photo I am publishing?

Blur, generally. It reads as an out-of-focus patch and draws less attention, which suits a bystander's face in a travel photo or an incidental detail behind a product. Pixelate reads as a deliberate censor mark, which is exactly what you want when the point is to show that something has been withheld, as in a news image or a screenshot of a document. Both remove the detail; they differ in how loudly they announce it.

Related tools