exif editor — Edit EXIF, IPTC & XMP Metadata Online Free

An exif editor is a tool that rewrites the metadata segments embedded in your photos without touching a single pixel. Your camera first writes EXIF 2.32 (make, model, exposure, aperture, ISO, focal length, orientation, timestamps, GPS). You then add IPTC Core 2024.1 (copyright, creator, credit, keywords, caption, location) and XMP (modern mirror of both, plus C2PA assertions). exif editor rewrites any of those segments surgically: only metadata bytes move, the picture stays byte-identical on the pixel side. No JPEG recompression, no loss. That is foundational for trust: a photo whose EXIF was edited stays forensically identical, only its descriptive envelope changes.

Why edit? Five reasons cover 95% of cases. 1) Clock drift: you crossed eight time zones, the camera stayed on Paris time; every timestamp is off by 7 hours, chronological sorting breaks and the Lightroom timeline lies. 2) Sensitive GPS: you shot at home, the body geotagged your house to the meter; publishing raw exposes your address. 3) Empty or stale attribution: copyright year 2022 on 2025 images, or empty Creator — near-certain stock rejection. 4) Empty IPTC: 40% of stock submissions are rejected for insufficient keywords; Google Images ignores images with no structured caption. 5) Broken DPI/orientation: a 72 DPI image printed at 300 DPI looks fuzzy, an uncorrected orientation 6 displays sideways on the web. exif editor fixes all five in under a minute, single file or 500 at once via the same engine.

Technically, exif editor manipulates three distinct containers. EXIF lives in APP1 (JPEG) or IFD0/ExifIFD/GPSIFD (TIFF). IPTC IIM lives in APP13 Photoshop IRB 8BIM 0x0404, and its modern XMP counterpart lives in APP1 XMP (RDF/XML). Our exif editor reads all three, merges the view, lets you edit field by field, then rewrites each container in place without shifting image offsets. Validation is done against ExifTool 13.x: every tag (DateTimeOriginal 0x9003, GPSLatitude 0x0002, IPTC:Keywords 2#025, XMP:Subject, etc.) is written with the correct type (ASCII, Rational, Undefined) and cardinality. Outputs pass the IPTC Photo Metadata 2024.1 validator and remain readable by Shutterstock, Adobe Stock, Getty, Google Images, Apple Photos, Lightroom and any DAM. See specs: exiftool.org/TagNames/EXIF GPS iptc.org/photo-metadata c2pa.org.

Unlike cleaners that wipe everything, exif editor edits selectively: you can keep copyright and keywords but erase only GPS, or shift dates without touching camera model. Unlike ExifTool CLI that requires memorizing exiftool -DateTimeOriginal+='7:0:0 0' -overwrite_original, exif editor exposes a date picker, a clickable map and text fields with live preview. Unlike Lightroom that edits via catalog and bills $11.99/mo, exif editor works directly on the file, in the browser, free for one file, with bulk 500 and AI in Pro. It is the fastest editor to fix a single field as well as to inject 30 IPTC keywords on the fly.

The core promise of exif editor is lossless rewriting. Concretely, a JPEG is made of markers: SOI, APP0 (JFIF), APP1 (EXIF), APP13 (IPTC), APP1 (XMP), DQT, DHT, SOF, SOS, then compressed DCT stream, then EOI. exif editor never decodes the DCT stream. It parses markers, isolates metadata segments, deserializes them (TIFF IFD for EXIF, IRB for IPTC, RDF/XML for XMP), applies your edits in memory, reserializes with correct length and padding (even alignment), then reassembles the file by copying other segments identically. Result: the image data checksum (hash of SOS stream) is unchanged before/after. You can verify: exiftool -b -JpgFromRaw file.jpg | sha256sum does not change after an exif editor pass, while Photoshop 'Save As' recompresses and changes the hash even at quality 100.

Why is it critical? 1) Quality: each JPEG recompression adds block artifacts, even imperceptible they accumulate over 10 saves. exif editor avoids any generation loss. 2) Forensics: an image whose pixels were recompressed can no longer prove authenticity; an exif editor image stays bit-identical. 3) Performance: not decoding/recompressing makes the operation instant (ms per file) even on mobile. 4) C2PA: C2PA manifests sign the pixel hash; if you recompress, the signature breaks. exif editor keeps the hash valid and adds a 'metadata edited' assertion without invalidating provenance. That is the only correct way to edit metadata per C2PA 2.1 spec (c2pa.org/specifications/2.1).

Edge cases: PNG and WebP historically carry no native EXIF but exif editor writes XMP and, since 2017, eXIf chunk (PNG) and EXIF chunk (WebP). Modern readers (Chrome, macOS Preview, ExifTool) read them. If you inject GPS into a PNG, exif editor writes it as XMP exif:GPSLatitude/GPSLongitude and as eXIf for max compatibility. For TIFF, all is native IFD: exif editor rewrites IFD0 without moving image strips. In all cases, exiftool -G1 -a -s file | wc -l before/after shows only tags you touched.

GPS EXIF is stored as rational degrees/minutes/seconds: GPSLatitude (0x0002) + GPSLatitudeRef (N/S), GPSLongitude (0x0004) + GPSLongitudeRef (E/W), GPSAltitude (0x0006) + GPSAltitudeRef (0=above sea level). exif editor lets you enter decimal (48.8566, 2.3522) or DMS (48°51'23.76"N), or click on the map. It converts to EXIF rationals and also writes XMP exif:GPSLatitude for modern readers. Precision is 1/1000 arc-second (~3 cm), more than enough. For WebP/PNG, exif editor writes same values as XMP and eXIf chunk.

When to add? Travel, mapping, real estate, reportage: precise GPS lets you display photos on a map (Lightroom Map, Google Photos, Pic2Map) and boosts local SEO. When to strip? Privacy: a photo taken at home geotags your house to 5 meters; publishing on Instagram without stripping GPS exposes your address (Instagram strips GPS on display but keeps it internally). GDPR and CNIL recommend minimization: publish only needed GPS. exif editor offers 'Strip GPS only' which erases GPSLatitude/GPSLongitude/GPSAltitude/GPSDateStamp but keeps copyright and keywords. That is finer than cleaners that wipe everything.

Do not confuse GPS with IPTC Location. GPS = geographic coordinates (48.8566, 2.3522). IPTC Location = textual fields Country/City/Sublocation (2#101, 2#090, 2#092) describing place in words. exif editor handles both: you can geotag Paris via GPS while writing IPTC Country-PrimaryLocationName='France'. For stock, IPTC Location is often more useful than raw GPS, because buyers search 'Paris' not '48.85 2.35'. exif editor can generate IPTC Location from GPS via reverse geocoding (option). Verify after with exiftool -GPS* -IPTC:City -IPTC:Country* file.jpg and visualize on EXIF Viewer map.

The most profitable field is also the most time-consuming: IPTC:Keywords (2#025) + XMP:Subject carry the keywords that sell. Shutterstock requires 7–50 keywords, Adobe Stock recommends 15–35, Getty indexes up to 50. Filling 30 relevant keywords per image by hand takes 5–10 minutes. For 500 images, that is 40–80 hours. exif editor embeds a vision AI that analyzes each image (pixels, not filename) and generates 20–50 unique IPTC keywords per image, plus a Title (XMP:Title / IPTC:ObjectName) and Description (XMP:Description / IPTC:Caption-Abstract). Each image gets its own set, no copy-paste. You then edit: remove 'f/1.8' if stock rejects it, keep 'handmade pottery, teal glaze'.

How does exif editor AI choose? It detects main subject, material, color, style, composition, context, and generates buyer-intent descriptors, not camera specs. Example: for a teal ceramic mug photo, it proposes 'ceramic mug, handmade pottery, teal glaze, speckled ceramic, stoneware cup, artisan coffee mug, 12oz mug, kitchenware' but not 'Canon EOS R5, 50mm, ISO 100' (stock rejection). You can pick platform preset: 'Shutterstock strict' filters technical keywords and caps at 50, 'Google Images SEO' adds long-tail variants. Keywords are written to IPTC and XMP simultaneously, and exif editor validates length (IPTC 2024.1 caps each keyword at 64 characters).

Recommended exif editor flow: 1) Drop 1 or 500 images. 2) Toggle 'Generate AI keywords'. 3) Let AI analyze (10–15 min for 500). 4) Browse suggestions, remove off-topic with one click, add your business terms. 5) Apply copyright template at same time. 6) Download ZIP. 7) Verify a sample with exiftool -IPTC:Keywords -XMP:Subject -XMP:Title file.jpg. On stock, images with 25–35 relevant keywords appear 2–3x more often than those with 5 generic keywords, per contributor feedback; exif editor puts you in the right range without manual effort.

Every exif editor output is validated against ExifTool, the open-source reference (exiftool.org). Here are the commands exif editor uses under the hood that you can replay. List dates: exiftool -DateTimeOriginal -CreateDate -ModifyDate -OffsetTimeOriginal -GPSDateStamp file.jpg. List GPS: exiftool -GPSLatitude -GPSLongitude -GPSAltitude -GPSLatitudeRef file.jpg. List IPTC/XMP: exiftool -IPTC:Keywords -XMP:Subject -XMP:Title -XMP:Description -IPTC:CopyrightNotice file.jpg. Compare before/after: exiftool -diff original.jpg edited.jpg (should list only modified tags). Verify lossless: exiftool -b -JpgFromRaw original.jpg | sha256sum vs edited.jpg (identical).

In exif editor, preview shows a colored diff: green = added, orange = modified, red = removed, grey = unchanged. You see exactly what will be written before download. For PNG/WebP, exiftool -a -G1 -s file.png lists XMP/IPTC/EXIF chunks; exif editor writes all. If a platform rejects your keywords, run exiftool -IPTC:Keywords -b file.jpg | tr ',' '\n' | wc -l to count; exif editor shows count live and warns beyond 50.

exif editor tip: after a 500 batch, pull 3 random samples and check them in EXIF Viewer (Date/GPS/IPTC tabs). If three are good, the batch is good. Do not check FileModifyDate (filesystem) but DateTimeOriginal (EXIF). And keep the original 24h while validating; exif editor deletes nothing server-side.

C2PA (Coalition for Content Provenance and Authenticity, c2pa.org) signs an image's history: who created it, with which tool, which edits. The C2PA manifest is a nested JUMBF with assertions and signature. exif editor preserves existing manifests (does not break them) and can add a 'metadata edited with exif editor on 2026-03-15' assertion with mini thumbprint. Verification is at contentcredentials.org/verify: drop the image, you see 'Edited with Exif Injector exif editor'. For press and brands, that is the difference between 'anonymous image' and 'traceable image'. exif editor does not invent capture: if you add GPS, it records 'GPS added', not 'Photo taken at 48.85 2.35'.

Why is exif editor C2PA-compatible without recompressing? Because C2PA signature covers the pixel hash, not metadata. By not touching pixels (lossless), exif editor keeps the hash valid. It only adds an entry to the manifest. Per C2PA 2.1 spec (c2pa.org/specifications/2.1), any metadata edit must be recorded as an 'assertion' without invalidating the chain. That is exactly what exif editor does. Tools that recompress break the chain and show 'Untrusted' on verifiers.

exif editor + C2PA flow: 1) Drop. 2) Edit dates/GPS/copyright. 3) Tick 'Preserve/Add C2PA'. 4) Download. 5) Verify at contentcredentials.org/verify. If you strip GPS for privacy, the manifest records 'GPS removed for privacy' — transparent and GDPR-compliant. exif editor is one of the few browser editors to handle C2PA without breaking the signature, because it does not recompress.

DPI (dots per inch) does not affect screen display but determines print size. A 3000x2000 image at 72 DPI prints at 105x70 cm (blurry), at 300 DPI at 25x17 cm (sharp). EXIF fields XResolution/YResolution (0x011A/0x011B) + ResolutionUnit (0x0128, 2=inches) carry this. exif editor edits them without recompressing: you flip 72 → 300 DPI in one click, the printer sees correct size, web ignores the value. Classic mistake: leaving 72 DPI on print-bound images, result = fuzzy prints because lab enlarges. Other mistake: setting 300 DPI on web images thinking it improves quality — DPI does not change pixels, only resolution (width x height) matters on screen. exif editor shows both: pixel resolution and print DPI, with cm/inches preview.

In exif editor, the DPI panel offers 72 (web), 150 (draft), 300 (standard print), 600 (fine art). You tick 'Apply to batch' for 500 print-catalog images. exif editor writes XResolution=300, YResolution=300, ResolutionUnit=2 and mirrors to XMP tiff:XResolution. ExifTool validation: exiftool -XResolution -YResolution -ResolutionUnit file.jpg should show 300 300 2. For PNG/WebP, exif editor writes same value to pHYs chunk (PNG) and XMP. E-commerce tip: if you deliver 1000 product images to a packaging printer, a 2x500 exif editor batch at 300 DPI avoids 1000 Photoshop opens. And if you need web + print, duplicate the batch: one at 72 DPI (web) + one at 300 DPI (print), same pixels, different metadata, no recompression.

exif editor pitfall: do not confuse DPI and resolution. Raising DPI does not make the image sharper, it only tells the printer to print smaller. To increase real sharpness, you need more pixels (upscale), not more DPI. exif editor refuses to write absurd DPI (>1200) and warns if XResolution/YResolution diverge (should be equal except anamorphic). Verify after with EXIF Viewer 'DPI/Print' tab.

exif editor handles JPEG, PNG, WebP, TIFF and HEIC (read-only for HEIC per browser). JPEG: native EXIF in APP1 + IPTC APP13 + XMP APP1, most complete. TIFF: all in IFD, ideal for print. PNG: historically no EXIF but exif editor writes XMP to iTXt and EXIF to eXIf chunk (since 2017) readable by Chrome/ExifTool. WebP: native EXIF/XMP chunks. AVIF/HEIC: XMP/IPTC per browser support. In all cases, exif editor preserves input format: JPEG stays JPEG, no conversion unless you request it. Rewriting stays lossless regardless of container, because exif editor never decodes pixels.

Limits per format: JPEG/TIFF carry all (EXIF+IPTC+XMP+GPS). PNG/WebP carry XMP/IPTC + GPS via XMP/eXIf, but some old tools only read JPEG EXIF and will ignore PNG GPS — test with exiftool. HEIC carries native EXIF but browser writing is limited; exif editor offers HEIC → JPEG conversion preserving metadata. For web, prefer JPEG for max metadata compatibility; for print, TIFF 300 DPI. exif editor shows a 'Format: JPEG – full EXIF' badge to guide.

exif editor parses first locally in your browser (FileReader API): the EXIF/IPTC preview never leaves your device. Only final processing (rewriting + optional AI) sends bytes to the server over HTTPS, processed in memory and deleted after download. No persistent storage, no data resale. For sensitive images (home, children, documents), use 'Strip GPS only' before any sharing and verify with exiftool -GPS*. GDPR minimization is natively supported: exif editor can selectively strip GPS, camera serial, thumbnail, while keeping copyright/keywords.

Unlike mobile apps that request full photo library access, exif editor only sees files you drop. No permission, no tracker SDK. And unlike cleaners that wipe all by default (losing copyright), exif editor edits selectively: you keep authorship while protecting privacy. That is the CNIL best practice: publish the minimum necessary, not the maximum available.

For pros, exif editor Pro encrypts transfers, logs processing (date, fields modified) and enables audit. And if you need to prove the processing chain, the C2PA manifest records each step. exif editor is built for photographers delivering to press: traceability without exposure.