Skip to content
Delete Image Metadata

Image Metadata Remover

A metadata remover for images that shows its work: full field list first, removal second, verification third. JPG, PNG and WebP, processed in your browser.

  • .jpg
  • .jpeg
  • .png
  • .webp
Free
No account, no limit on files
0
Files uploaded — processing is local
4 formats
Lossless — pixels never re-encoded
Processed in your browser
Ready

Inspect before you strip

Most metadata removers are a black box: a file goes in, a file comes out, and you take the result on faith. That is a poor fit for a privacy tool, because the interesting question is usually not 'is it gone now' but 'what was in there in the first place'.

This remover reads the file first and lists every field it can decode, grouped by what the field reveals. Coordinates and device identifiers appear at the top and are marked as sensitive. Only then does the removal step become available.

How the parser reads a file

The format is identified from the file's magic bytes, not its extension — a file named photo.jpg that is really a PNG is treated as a PNG. Two passes then run over it. A container pass walks the physical structure and records each metadata block with its size. A tag pass decodes the contents of those blocks into named fields.

Both numbers are shown because they answer different questions. The block sizes tell you how many bytes of metadata the file carries. The field list tells you what those bytes say.

Everything the tool displays is sanitised

Metadata values are untrusted text that came from a file you did not write. Before anything is displayed it is stripped of control characters and bidirectional overrides, collapsed to a single line and length-limited. Values are rendered as text, never interpreted as markup, so a crafted field cannot execute anything in your browser.

What this tool does

  • Complete field listing before removal, not just a count
  • Sensitive fields flagged rather than buried in a long table
  • Format detected from file contents, not from the filename

What it does not do

  • Fields inside proprietary maker-note blocks are removed but not individually decoded
  • Compressed PNG text chunks are removed without being decompressed for display

Image Metadata Remover

A metadata remover for images that shows its work: full field list first, removal second, verification third. JPG, PNG and WebP, processed in your browser.

Open the tool

Reviewed and updated . Behaviour described on this page is covered by the project’s automated tests.

Frequently asked questions

What does the field count actually count?

Each decoded metadata value the parser can name — one row per field. Blocks that are removed but not decoded, such as vendor maker notes, are counted in the bytes figure rather than as individual fields.

Why does the field count sometimes differ from another tool's?

Different parsers decode different tag sets and some collapse duplicates that appear in both EXIF and XMP. The byte figures are the more reliable comparison.

Can it show me GPS coordinates from my photo?

Yes, when the photo has them. Latitude and longitude are shown as decimal degrees so you can see exactly what a recipient of the file would be able to read.

Is any of this sent anywhere?

No. Field values are never included in analytics, never placed in the URL and never logged. They exist only in the page while the tab is open.

Can I see the metadata without removing it?

Yes. The analysis runs first and removal is a separate, explicit step, so you can inspect a file and simply not clean it.

What does the byte count next to each block mean?

How much space that metadata block occupies in the file. It is the more reliable comparison between tools, because different parsers name and count fields differently.

Why are some fields marked as sensitive?

Those are the ones that identify a person, a device or a place: GPS coordinates, serial numbers, owner names, timestamps. They are flagged so you do not have to read the whole table to spot them.

Does it decode manufacturer maker notes?

No. Vendor maker-note blocks are removed, but their proprietary contents are not decoded for display.