Edit and modify EXIF metadata fields in photos before sharing.
Every photo taken on a phone or camera carries a hidden block of EXIF metadata alongside its pixels: the date it was taken, the camera make and model, lens, focal length, shutter speed, ISO, and often the GPS location. This tool parses that block, presents the fields as editable form entries, and writes your changes back into the image file you download and share. The pixels themselves are never touched. The usual surprise is that editing EXIF does not anonymize a photo: dozens of tags remain, and many platforms strip or re-stamp metadata anyway, so the edit is not always visible to recipients.
A concrete input and expected output from the current implementation.
Input
2024-03-02 10:15:30, entered as the new Date taken for a loaded JPEG
Expected output
A download of the same JPEG whose DateTimeOriginal tag now reads 2024:03:02 10:15:30, with camera model, lens, ISO, and GPS tags unchanged and the photo rendering exactly as before.
The EXIF specification stores date tags as fixed 19-character ASCII strings in the form YYYY:MM:DD HH:MM:SS, so a compliant writer records the value with colons, not dashes. Metadata is stored apart from pixel data, which is why the picture itself is unaffected.
A photo's EXIF data lives in a structured block near the start of the file, stored separately from the pixel data. The tool decodes that block into readable tags and presents them as a form: date taken, camera model, lens, focal length, aperture, shutter speed, ISO, and GPS coordinates when present. Cameras write only a subset of all possible tags, so most photos show a small handful of fields.
Changing a value and exporting rewrites that tag and returns a download of the edited image; processing stays in your browser. Pixel data is not resampled or compressed, only the tags change. Untouched fields stay exactly as the camera wrote them, including tags the form does not show. If a viewer later disagrees with what you set, the exported file is authoritative; verify it with a separate reader.
No. In formats like JPEG, EXIF occupies its own block, and text tags can be rewritten without touching the pixels, so the image renders identically. If the exported file is much larger or smaller than the original, it may have been re-encoded, which can cost quality; compare the two before sharing.
Usually, by clearing the GPS fields, though some tools write an empty tag rather than deleting the block, and viewers may then show no location at all. There is no way to guarantee removal short of stripping all metadata, so verify the exported file with a separate reader before relying on it, and remember the platform you share to may add or strip its own data.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Convert between bytes, KB, MB, GB, and TB with precise binary and decimal calculations.
Open, view, and edit CSV files in a spreadsheet-style table with sorting and filtering.
Visualize JSON data as a collapsible tree with syntax highlighting and search.
Generate Code 128, EAN, UPC, and other barcode formats with customizable size and labels.
Convert images to Base64 data URLs and decode Base64 strings back to images.
Generate Apache .htaccess redirect rules for 301, 302, and rewrite configurations.