Regional Image Privacy Editor
Draw rectangles or brush strokes to cover, pixelate or blur selected image regions, adjust size, undo edits and export a PNG.
About this regional image privacy editor
Draw rectangles or brush strokes to cover, pixelate or blur selected image regions, adjust size, undo edits and export a PNG Processes media assets directly in the browser using HTML5 Canvas and WebAssembly decoders, ensuring zero file uploads.
Image processing & canvas pipeline
Applies 2D image convolution filters, pixelation, and EXIF metadata sanitization directly to raw RGBA ImageData buffers. Privacy tools apply Gaussian blur kernels or block pixelation to obscure sensitive areas (faces, license plates, credentials). EXIF metadata scrubbing parses TIFF/JPEG binary application segments (APP1, markers 0xFFE1), stripping GPS latitude/longitude, camera serial numbers, device models, and timestamps while preserving image pixel data intact. Generates ISO/IEC 18004 QR codes.
Worked image transformation example
Scenario: Blur a 12×9 test PNG with the fixed filter.
Sample input:
Processing: Canvas draws the full image with blur(12px).
Illustrative output:
Resolution, dimension & memory limits
Operational constraints and validation boundaries: Local PNG/JPEG/WebP smaller than 30 MB; each side at most 4096px and total at most 8,388,608 pixels. Block size/blur radius integer 2–80px; brush width 4–160px; 3/6-digit HEX. At most 50 edits and 256 points per stroke; long strokes are approximated. Rectangle edges use whole pixels; brush uses a binary pixel-center mask. Blur and mosaic do not guarantee that information is unrecognizable or irreversible. Opaque cover removes selected original pixels from the exported PNG, but cannot hide missed areas or contextual clues and is not cryptographic erasure of the source or undo memory. Review the downloaded image before sharing. No automatic face/text detection, metadata preservation, remote URL, SVG, animation preservation or forensic certification. Near-limit memory stress, physical touch, other browsers and native-language review remain unverified.
Regional Image Privacy Editor image operations execute in client memory via HTML5 Canvas and browser decoders. Inspect output previews before replacing source assets.
In-memory image processing boundary
File buffers and document assets in Regional Image Privacy Editor are processed in-memory via local browser APIs with zero file uploads to CZOA servers.
Image format & W3C Canvas standards
W3C Canvas 2D context specifications and standard image container formats:
- WHATWG Canvas 2D
- PNG (ISO/IEC 15948)
Regional Image Privacy Editor verification · Audit standards
How to use it
- Enter, paste, or select your input data into the Regional Image Privacy Editor workspace controls.
Frequently asked questions
Which effect actually replaces the selected source pixels?+
Operational requirements for "Which effect actually replaces the selected source pixels?" are verified in local memory during execution of Regional Image Privacy Editor.
What controls does Whole-Image Blur Filter provide?+
Choose a local image, effect and selection shape. Drag on the preview to mark a rectangle or paint a stroke. Opaque cover replaces every selected pixel with the chosen solid color and full opacity, without blending original pixels. Mosaic averages image-aligned blocks; blur uses the browser Canvas filter. Set block size/blur radius and brush width before the next stroke. Undo removes the latest complete edit; Clear restores the source. Example: cover x10–29 and y10–29 in a 40×40 image: exactly 400 output pixels become the cover color. The source and undo history remain in this page until replacement or close. The original whole-image blur stays below.
What limits apply to whole-image blur?+
Local PNG/JPEG/WebP smaller than 30 MB; each side at most 4096px and total at most 8,388,608 pixels.
What does the generated PNG establish about privacy?+
Original whole-image blur: The source applies Canvas blur(12px) to the whole decoded image and exports a PNG. That transformation alone does not prove sensitive details cannot be recovered or identified. It also does not establish what ordinary site requests, extensions, or other software do.