How Much Space Does Stripping Metadata Actually Save? We Measured Real Photos
Removing metadata saves a fixed few kilobytes - not a percentage of your photo. In our own tests, an EXIF + GPS + embedded-thumbnail block of 3.4 KB was stripped identically from a 52 KB photo, a 174 KB photo, and a 630 KB photo - recovering 6.1%, 1.9%, and 0.5% of each file respectively. The space you get back did not grow with the picture. Only when a file also carried a large XMP edit-history packet did the saving reach ~33 KB. So the "5–50 KB" figure some tools advertise is real, but it only shows up at the top end; for ordinary photos the bytes you recover are tiny, and the real reason to strip metadata is privacy, not storage. We also confirmed the pixels are never touched - the decoded image before and after stripping was bit-for-bit identical (maximum channel difference = 0).
What we actually tested (our own machine, not a guess)
This is a controlled local experiment, the same method we used in Does Watermark Removal Keep EXIF Data? and Erase EXIF Data, Tested. Using Pillow 12.3.0 and piexif 1.1.3, we built three JPEGs at different resolutions, then wrote a real EXIF block into each - GPS (6 fields, decoding to 31.2231°N, 121.4697°E), camera make/model/lens, timestamps, and an embedded thumbnail. We added the block with piexif.insert and removed it with piexif.remove, which touches only the metadata segments and never re-encodes the image scan data. For each photo we recorded the byte size with metadata, after stripping, and the difference. We then repeated the whole thing with an extra 30 KB XMP packet (the kind Lightroom writes as edit history) on a medium-sized photo.
To be certain the image itself was untouched, we decoded both copies and compared every 7th pixel: the maximum channel difference was 0 in every case. Stripping changed the file size; it did not change a single pixel.
The numbers: metadata is fixed overhead
| Photo (pixels) | With metadata | After strip | Saved | % of file |
|---|---|---|---|---|
| 800×600 | 55.2 KB | 51.8 KB | 3.4 KB | 6.1% |
| 1920×1080 | 177.0 KB | 173.7 KB | 3.4 KB | 1.9% |
| 4000×3000 | 632.9 KB | 629.5 KB | 3.4 KB | 0.5% |
| 1920×1080 + 30 KB XMP | 211.3 KB | 177.9 KB | 33.5 KB | 15.8% |
The first three rows are the key result: the same 3.4 KB came out of every photo, whether it was a 52 KB snapshot or a 630 KB shot. The metadata block is a fixed-size annex bolted onto the image; it does not scale with how many pixels the photo has.
Why the saving doesn't scale with the photo
A JPEG's metadata is a small set of structured blocks: the EXIF IFD (camera settings, timestamps), a GPS sub-block, and usually an embedded thumbnail of the full frame. On our test photos that whole annex measured 3,436 bytes (3.4 KB). None of it depends on image resolution - a 4-megapixel phone photo and a 12-megapixel one carry essentially the same EXIF. So the absolute saving is the same, and its percentage shrinks as the photo gets bigger, which is exactly what the table shows (6.1% → 1.9% → 0.5%).
The one thing that does scale is XMP - the XML edit-history sidecar that apps like Lightroom bake into the file. A 30 KB XMP packet took the recovered space from 3.4 KB to 33.5 KB in our test. That is where the upper half of the "5–50 KB" range comes from.
The "5–50 KB" claim, checked against our results
Several metadata-removal tools advertise a fixed space saving. Compresto's guide "How to Remove Metadata From a Photo" (compresto.app/blog/remove-metadata-from-photo, published 2026-05-01 by Hieu Dinh) states plainly: "Stripping it changes the file size by 5–50 KB but leaves the actual image bits untouched." Our measurements line up with that range at the edges but not in the middle:
- Our common case (small embedded thumbnail): 3.4 KB - slightly under their 5 KB floor. A minimal-EXIF photo simply does not carry 5 KB of metadata.
- With a fatter thumbnail (many phones embed 5–20 KB previews), the common-case saving moves up into their 5–50 KB band.
- With a large XMP packet: 33.5 KB - squarely inside their range, and the realistic ceiling for most consumer photos.
Transparency note: the 5–50 KB wording is Compresto's, quoted from their published page; we did not independently re-derive their exact figure this run beyond fetching that page. Our own measurements above are the source for every number we state as ours.
Does stripping change image quality?
No. Metadata lives in separate segments from the pixel scan data, so removing it cannot alter the picture - and we verified it: decoding both the with-metadata and stripped copies and comparing every 7th pixel gave a maximum channel difference of 0. This matches what we found earlier in Does Watermark Removal Keep EXIF Data? (the export path drops the APP1 block entirely) and Erase EXIF Data, Tested. If your file got smaller and the image looked different, something re-encoded the photo - that is a compression change, not a metadata strip.
When stripping metadata actually matters
For storage, the effect is minor: a few KB per photo, a fraction of a percent on large files. The reason to strip is privacy:
- The GPS block can drop a map pin on your home or routine (How to Find Out Where a Photo Was Taken).
- The camera serial number ties photos across accounts to one device.
- An embedded thumbnail can leak the uncropped original you thought you had deleted.
If you want the GPS gone before a photo ever leaves your device, see Clear Metadata From a Photo (the 18 fields a phone writes, with the GPS decoded and removed) and Turn Off Camera Location. Our own tool processes the image entirely in your browser and never uploads it, so the original-with-coordinates never touches a server - and the export keeps your pixels exactly as they were.
FAQ
How much space does removing EXIF save? On typical photos, a few KB - our test saved 3.4 KB regardless of image size. Only files with a large XMP edit-history packet reach the 30–50 KB end of the range.
Is the "5–50 KB" claim true? The upper part is, when a big XMP packet is present. For a normal photo with a small thumbnail, the real saving is closer to 3–10 KB. The claim is a range, not a guarantee per photo.
Does stripping metadata shrink a 4 MB photo much? No - the same ~3.4 KB comes off, which is under 0.1% of a 4 MB file. Strip for privacy, not for space.
Will I lose image quality? No. Metadata is separate from pixels; we measured a maximum pixel difference of 0 after stripping.
Do social platforms strip it for me? Mostly yes on the public copy (see Does Facebook Remove EXIF Data?), but copies you email or message keep it, and the platform may still hold your original. Strip before sharing for real control.
Related reading
If you are deciding what to strip and why, these are the next reads:
- Does removing EXIF remove the embedded thumbnail? — the second copy hiding inside the same block, and why a half-strip leaks.
- Erasing EXIF data: six deletion paths, scored — which method actually removes the bytes, measured on a 34-field test photo.
- Clear metadata from a photo — the 18 fields a phone writes, with the GPS block decoded and removed.
- Do screenshots have EXIF data? — the other kind of image people strip, and what it carries instead.