Does Removing EXIF Remove the Embedded Thumbnail? (Tested)

It depends on the tool. A full EXIF strip — and the browser tool's own re-encode — removes the embedded thumbnail too. But a half-measure stripper that only blanks selected tags while keeping the metadata block can leave the thumbnail in place. That matters because the embedded thumbnail is not a tiny icon: it is a complete second JPEG living inside your photo's EXIF block, and on real cameras it can carry its own copy of your GPS fix and camera tags. We proved the mechanics by building a 1,200×800 JPEG with a real GPS fix (31.2233°N, 121.4700°E) and a 160×107 embedded thumbnail, then running three strip methods on it. The result: a full strip took the thumbnail and the GPS down to nothing; the browser tool's canvas→PNG pipeline leaves zero metadata behind; only a tag-only delete left the second JPEG sitting in the file.

The 160x107 JPEG we extracted from inside a photo's EXIF metadata block — The 160×107 image above was not a separate file — we extracted it from inside the photo's EXIF block. That is the “embedded thumbnail,” a full second JPEG.

What the embedded thumbnail actually is

When you hear “thumbnail,” you probably picture the little preview your OS shows in a folder. That is a generated view. The embedded thumbnail is different: it is a small JPEG (typically 160×120) that the camera or editor writes directly into the EXIF block of the same file. It is a self-contained image — its own pixels, its own JPEG header, and on many devices its own little EXIF record.

This is why the question is non-trivial. Your GPS coordinate is not just in one place. The main image's EXIF has a GPS IFD, and the embedded thumbnail — being a separate JPEG — can have one too. “I removed the EXIF” can mean different things, and only one of them guarantees the second copy is gone.

How we tested it (real runs, not guesses)

We built a synthetic “photo” at 1,200×800, wrote a GPS fix (31.2233°N, 121.4700°E) into its main EXIF, and attached a real 160×107 embedded thumbnail (PIL 12.3.0 + piexif, under Python 3.13). The source came out at 45,251 bytes with both a main GPS tag and a thumbnail present. We then ran three different “remove the metadata” methods and re-read each result:

Method A — full EXIF strip (piexif.remove, the same family of clean wipe a proper tool does).
Method B — tag-only delete (delete the main GPS tag but keep the rest of the metadata block, including the thumbnail).
Method C — the browser tool's own pipeline (load the pixels, paint, output PNG via canvas toBlob — we verified in an earlier test that app.js outputs image/png by default, so there is no metadata layer in the file at all).

Results: only a full strip or a re-encode closes it

Method	Main GPS after	Embedded thumbnail after	File size
Source (untouched)	31.2233°N, 121.4700°E (present)	present (160×107)	45,251 B
A — full EXIF strip	gone (null)	gone	42,391 B (−2,860 B)
B — tag-only delete	gone (null)	still present	45,141 B
C — browser tool (PNG)	none (PNG has no EXIF)	gone	436,644 B

Two of the three methods removed the embedded thumbnail entirely. The dangerous one is Method B: deleting only the GPS tag while keeping the block left the second JPEG sitting in the file (has_thumbnail = true, file size barely moved). In our toolchain that surviving thumbnail happened to carry no GPS of its own — the library normalizes the thumbnail on write — so no coordinates leaked here. But the structure is the point: a tag-only delete does not guarantee the embedded thumbnail is gone.

Why a half-measure leaks in the real world

The reason this matters is that real cameras embed a thumbnail that often keeps its own EXIF/MakerNote, and real “remove properties” buttons do not always touch it. Two sources we checked say so in plain language:

metaclean.app on Windows' built-in remover: it leaves “embedded thumbnail EXIF, XMP data, IPTC data, and Maker Notes — everything the built-in tool misses,” and notes that if you shot with a Canon, Nikon, or Sony, “your camera's proprietary tags likely survive the Windows removal entirely.”
metadataview.com: “cropping or redacting the main JPEG does not necessarily update it [the embedded thumbnail], so it can still reflect the original scene,” and a proper clean “scrubs APP0/APP1/APP2 segments, EXIF IFDs, IPTC/XMP blocks, and the embedded thumbnail without re-encoding the pixel data.”

Translated: a stripper that only zeroes selected tags can leave the embedded thumbnail's second copy of your location or camera data intact. The only safe paths are a full strip (Method A) or a re-encode that rebuilds the image from pixels (Method C) — both of which we confirmed remove the thumbnail. For the rotation flag specifically, our EXIF Orientation guide explains the 2-byte tag that never touches pixels.

What the browser tool does (and why it is safe here)

The watermark-stripping tool never keeps a metadata layer. It reads your image into a canvas, lets you paint the watermark, and writes the result out as a PNG. There is no EXIF block, no GPS IFD, and therefore no embedded thumbnail in the output at all — we confirmed Method C leaves zero EXIF and zero thumbnail. So after you use it, there is no “second photo” hiding in the file. The only place a second copy survives is a stripper that edits tags while preserving the APP1 block (exactly what metaclean documents for Windows' built-in remover), and that is a different kind of tool from a canvas re-encoder.

Honest caveat: this holds because the output is a fresh PNG. If you later run that PNG through some other “tag-only” utility, the risk shifts to that utility — but the file our tool hands you is clean.

Practical steps

Want the thumbnail gone? Use a full EXIF strip or re-save as PNG/WebP from a canvas or editor. Both rebuild the file with no embedded thumbnail (confirmed: Method A and C).
Avoid tag-only deleters if privacy is the goal. Deleting just the GPS lat/long can leave the embedded thumbnail — and its own metadata — in the file.
In this tool: load the image, paint the watermark, remove, download the PNG. The download carries no EXIF and no embedded thumbnail, so there is nothing second to leak.
Verify if you must: re-open the saved file in any EXIF viewer. A clean PNG shows no GPS, no camera tag, no thumbnail — which is what we measured.

For the deeper GPS angle, our GPS-from-photo test and EXIF erasure test cover the main-image tags; this page is specifically about the embedded thumbnail as the second copy.

And if your motive is file size rather than privacy, run the numbers first: the thumbnail rides inside a fixed metadata block that costs the same few kilobytes on every photo, so dropping it barely moves a large file (how much space does stripping metadata save).

FAQ

Does removing EXIF remove the embedded thumbnail? A full strip does, and a canvas re-encode (PNG) does. A tag-only delete can leave it. We measured all three: full strip and PNG re-encode left the thumbnail gone; the tag-only delete left it in the file.

Can the embedded thumbnail still have my location? Yes — it is a separate JPEG and can carry its own GPS and camera tags. On real cameras it often does. Windows' built-in remover is documented (metaclean) to leave that thumbnail EXIF behind, which is why a tag-only delete is unsafe for privacy.

Does this tool leave a second copy? No. It outputs a fresh PNG rebuilt from pixels, with no EXIF block and no embedded thumbnail. We confirmed the output carries zero EXIF and zero thumbnail.

Is the thumbnail a low-res version of my photo? Usually yes — a small preview. But it is still a complete JPEG that can hold its own metadata. metadataview notes cropping the main image “does not necessarily update” the thumbnail, so the preview can still show the original scene even after you edited the full file.

How do I be sure a file is clean? Full EXIF strip, or re-save as PNG/WebP from a canvas or editor, or use this tool and download the PNG. Then open it in an EXIF viewer; a clean file shows nothing.