Remove image metadata
Strip EXIF, GPS and XMP data from a photo before you share it. Files stay on your device.
How this works locally
- You choose a file; the page reads it from your device.
- The matching engine is loaded from fileslimmer.com and runs in a Web Worker.
- The result is written back to a location you choose on this device.
Before or choose files from your device
Original size —
Accepted formats
- Reads
- JPG · PNG · WebP
The output keeps the format of the file you chose. The pixels are copied across untouched — only the metadata segments are dropped. AVIF and HEIC are not accepted here: removing their metadata requires decoding and re-encoding the image, which the conversion tools do instead.
Estimated memory
Your browser reports only a coarse memory hint, so this figure is an estimate.
| Device profile | Largest file | Largest image | Files per batch |
|---|---|---|---|
| Minimal | 40 MiB | 32 megapixels | 50 |
| Low | 75 MiB | 50 megapixels | 100 |
| Balanced | 150 MiB | 90 megapixels | 250 |
| High | 250 MiB | 150 megapixels | 500 |
Your browser is placed in one of these profiles from the coarse hints it exposes. A file above the limit is refused before it is read, rather than after the tab has run out of memory.
Limitations
- Lossy compression discards detail permanently. Re-compressing a file that was already compressed removes more detail without recovering anything an earlier pass removed.
- An animated GIF, WebP or AVIF is not handled by the still-image engine. It is refused rather than quietly reduced to its first frame.
- The capture orientation is applied to the pixels rather than left in a tag, so the result is upright even in software that ignores rotation metadata.
- EXIF, GPS and XMP data are removed from the output. Anything visible in the picture itself — a street sign, a screen, a reflection — is untouched by that.
- An embedded colour profile is carried over so colours do not shift. A file with no profile is treated as sRGB, which is a guess the source did not make for you.