METADATA
Change the date, camera, credit and location stored in a photo — without touching a single pixel of the image itself.
Up to 50 MB — it never leaves your device
Preview
Metadata in this file
This photo has no EXIF block yet. Fill the form and one will be created.
metadata, not pixels
Every photo out of a camera or a phone carries a block of EXIF metadata: when the shutter opened, which body and lens took it, the exposure settings, often the exact coordinates. Software leans on it constantly. Photo libraries sort by the date taken, not the file date; maps place pictures by their coordinates; galleries turn images upright based on a single orientation flag rather than the stored pixels.
Which means a wrong value has real consequences. A camera with a dead clock stamps every shot with the wrong year and your library files them in the wrong decade. A scan of an old print gets today's date. A photo you are about to publish still knows the street it was taken on. This tool edits those values directly in the file, replacing only the metadata block and leaving the compressed image data byte for byte identical.
three steps
Its metadata block is parsed in your browser and the form is filled with what is already there. A photo with no EXIF at all is fine — one gets created.
Empty a field to delete that tag rather than store a blank one. Coordinates are decimal degrees; clearing them strips the location block completely.
You get the same JPEG back with a new metadata block. The image data is untouched, so saving repeatedly costs no quality at all.
quick answers
No, and that is the whole design. A JPEG is a series of segments, and the metadata lives in one of them near the front. This tool replaces that one segment and copies everything from the start-of-scan marker onwards unchanged, so the compressed image data comes out byte for byte identical. You can edit and save the same file a hundred times without softening it. Tools that strip metadata by redrawing the image to a canvas cannot make that promise — they re-encode every time.
EXIF can be carried by PNG and WebP too, but in completely different containers: a PNG stores it in an eXIf chunk and a WebP in a RIFF chunk. A writer for one does not transfer to the others. Accepting those files and silently doing nothing, or quietly converting them to JPEG, would both be worse than saying no.
Two things, and the tool says so above the save button. The maker note — a vendor-specific blob holding lens corrections and shooting modes — is dropped, along with the small embedded thumbnail. Both contain byte offsets measured from the start of the metadata block, and rebuilding that block leaves those offsets pointing at the wrong place. Carrying them across would produce data that looks valid and is not, which some viewers crash on. Everything else, including tags this form does not show, is preserved exactly.
Yes, that is the most common reason people come here. Set the date and time you want and it is written to all three date tags at once, because different applications read different ones. Clearing the field removes all three rather than leaving a blank string behind.
Press Clear location, then save. That removes the whole GPS block: coordinates, hemisphere references and anything else stored alongside them. If you want to erase every trace of metadata instead of editing it, use the remove EXIF tool, which strips the lot.
It is a single number telling viewers how to turn the picture before showing it, which is how a phone held sideways still displays the right way up. Changing it here rotates nothing — the pixels stay exactly as they were, and only the instruction changes. If a photo shows up rotated in one app and correct in another, this flag is usually why.
No. The file is read into memory by JavaScript on this page, the metadata block is rebuilt locally, and the download is produced from bytes that never left your device. That includes the coordinates, which is the part people most often want to keep off a server.
