File Privacy

Private Image Optimizer

Compress images, convert formats and remove hidden metadata entirely on your device.

Processing capacity depends on image dimensions, browser support and available device memory.

PRIVATE IMAGE OPTIMIZER

Local image optimisation with privacy evidence

LOCAL PROCESSINGCLOUD: DISABLED

Images are decoded, inspected and processed locally in your browser. They are not uploaded to MicroIntent.

How local processing works

Selected files remain in this browser session. Metadata inspection, canvas re-encoding, verification, ZIP creation, and report export use browser APIs only. Network transfer is not required.

Output settings

FormatA new file is produced so supported metadata can be removed. This does not preserve the original bytes.Quality: 80%Lower quality usually means smaller lossy files; results vary by image.ResizeKeep the original when optimisation produces a larger fileEnabled by default. It never overrides supported privacy-sensitive metadata removal; a larger sanitised output is kept when privacy cleaning is required.Filename suffix

Metadata: All supported non-essential metadata is removed through clean re-encoding. Orientation is applied to pixels first.

Safety limit: 40 MB compressed per file. Pixel and memory estimates are checked before decoding. Two images process at a time.

This browser uses the bounded main-thread fallback. Canvas encoding uses the browser main-thread fallback.

Drop images or choose filesJPEG, PNG, WebP. Multiple files supported. Files never leave this device.Choose images

Batch results

0 files

Add images to inspect hidden GPS, camera, timestamp, XMP, text, and profile metadata before processing.

How local image privacy processing works

The tool checks common JPEG, PNG, and WebP metadata containers in this browser, decodes pixels, applies supported orientation, and generates a fresh image without copying inspected metadata. It then inspects the generated output again.

What metadata can reveal

Photos can contain GPS coordinates, camera model, capture time, editor details, comments, XMP, and author fields. The original file can reveal this information even when it is not visible in the image.

Supported formats and limitations

JPEG/JPG, PNG, and WebP can be inspected and output. AVIF appears only after this browser proves it can return an AVIF Blob. Browser re-encoding can slightly change specialised colour profiles. Inspection covers common supported containers, not every proprietary or unknown metadata structure.

Common uses

Prepare property photos, marketplace listings, work images, screenshots, or family photos before sharing. Review the before-and-after evidence and preview rather than assuming a file is clean.

Questions

Are my images uploaded?

No. This tool does not need a file upload endpoint or image-processing service. Your selected files remain in this browser session.

Does “verified removed” mean no unknown data can exist?

No. It means the output parser found the supported metadata containers absent. The report always states parser coverage and limitations.

Why can the output be larger?

The original may already be optimised, the chosen format may be lossless, or a small image may not benefit from re-encoding. The dashboard reports the actual result.