Pixelate or blur faces, documents and plates by selecting a region, all locally in the browser.
Hiding a face, a document or a license plate looks simple, but how you censor decides whether the information really disappears. A blackout replaces the region with a solid colour: no data from the original survives, and it is irreversible by construction. Pixelation and blur, by contrast, only transform the pixels mathematically, and transformations can be inverted: weak pixelation of text in a known font has been reversed in practice, and a light blur is partially recoverable. They are visual obstacles, not cryptography. One more thing matters about the final file: this tool re-encodes the image with the regions already processed, so the original content under the redaction is not embedded in the downloaded file, unlike a blur added as a layer on top in editors that keep layers. Everything happens in your browser; images with sensitive data never leave your device.
All three hide, but they protect very differently. A blackout paints the region with a solid colour: the original pixels stop existing in the file, and no algorithm recovers what is no longer there. It is the only option suited to genuinely sensitive data, faces, document numbers, license plates, and that is why it is the default.
Pixelation replaces the region with blocks of average colour, and blur spreads the pixels through a kernel. Both are deterministic transforms and therefore attackable: at low strength enough structure survives to reconstruct part of the content (depixelating text in a known font is a demonstrated case). Raising the strength helps, but neither offers the guarantee a blackout does.
Before sharing a screenshot of a conversation, a photo of a document or an image with bystanders in the background, censoring the identifiable parts avoids exposing personal data. Faces of people who did not consent, ID numbers, addresses, license plates and barcodes are the most common targets.
The key point is that censoring must happen before the file leaves your control. Because processing here is local and the export already bakes in the erased region, the image you share does not carry the hidden original, reducing the risk of a leak through reverse engineering.
On export, the tool "burns" the censor into the pixels: the processed region becomes part of the image itself, with no separate layer that could be removed. That differs from applying a blur as an overlay object in editors that save layers, in those cases, the original can remain in the file.
An extra precaution applies to metadata: re-encoding usually drops much of the EXIF, but if the photo had location (GPS) or other sensitive data, it is safest to also run it through the EXIF-removal tool. Censoring the visible content and clearing the metadata are complementary layers of protection.
Paste the code into your HTML and the tool shows up on your page, without J-Kit's navigation and ads. It still runs in the browser of whoever visits your site.
<iframe
src="https://jkit.tools/embed/en-US/censor-image"
width="100%"
height="600"
style="border:0"
loading="lazy"
title="Censor Image"
></iframe>Blackout is the only genuinely safe one: it replaces the region with a solid colour, destroying the pixels outright. Pixelation and blur merely scramble the information and, at low strength, can be partially reversed. For faces, documents and license plates, use blackout, which is why it is the tool's default.
Censoring is applied entirely in your browser. No image is sent to any server, essential for sensitive content.