Drop the image — Mochi will run Strip Metadata (EXIF / GPS).
↑↓ navigate↵ selectEsc close
Files stay on your device. Enter send · Esc close drawers
Strip Metadata (EXIF / GPS)
Remove camera info, location, timestamp — privacy first
File-size limits show up in email attachments, web upload forms, and document submission portals. Strip Metadata (EXIF / GPS) compresses the input below the cap while keeping the maximum quality the size budget allows. The preset outputs JPEG (re-encoded, no metadata).
Specifications
Output format
JPEG @ 95% quality
Processing
100% in your browser — no upload
Cost
Free, unlimited
When you'd run Strip Metadata (EXIF / GPS)
Attaching the file to an email when the provider caps individual attachments near a few MB.
Uploading to a contact form, ticket system, or government portal that rejects anything above the cap ceiling.
Sending the image over a slow connection — mobile data, satellite, in-flight Wi-Fi — where every kilobyte matters.
Posting to a forum, community, or low-quota web host with strict per-file size limits.
How Strip Metadata (EXIF / GPS) runs
This preset is a deterministic recipe — every step has fixed parameters
so the result is byte-identical across runs of the same input.
Compress to ≤ None as JPEG.
Where the work happens
The compression loop runs in your browser. The encoder binary-searches JPEG quality to find the highest setting that keeps the output below the cap, evaluating each candidate on the canvas without a network round-trip.
For inputs larger than the preset's max-width ceiling, the image is also down-sampled to the ceiling before compression so the file-size budget isn't spent on resolution that the final viewer wouldn't display anyway.
Common mistakes
Setting the target lower than the source can sustain. Strip Metadata (EXIF / GPS) compresses to ≤ the target, but a 12-megapixel photo squeezed below 100 KB will visibly soften — pair the limit with a maxWidth ceiling like this preset does.
Compressing then editing. Each save round-trip through JPEG compounds artefacts; do all your edits first, then run this preset as the final step.
Using a generic PDF compressor for image-heavy PDFs. If the original is a photo, compressing the image directly with this preset is faster and produces a smaller file than wrapping the result in a PDF.
Uploading sensitive images to a server-side tool. This preset runs entirely in your browser; the file never leaves your device. Verify this in your browser's network panel if working with confidential material.
FAQ
Why JPEG and not PNG?
The target accepts JPEG, and JPEG compresses photographic content 5-10× smaller than PNG with no visible difference at quality 95%. PNG is the right choice only when the image has hard edges or transparency — which photo-ID, social posts, and product photos don't.
Does my image get uploaded?
No. This preset runs entirely in your browser using WebAssembly + canvas APIs — no server round-trip. You can verify this in your browser's network panel: only static asset requests, no image upload. The file never leaves your device.