Title
A short display title written as Dublin Core XMP.
Private, local XMP editing
Image metadata editor
Inspect an image, edit a small set of portable metadata fields, and download a newly re-encoded copy. The browser re-scans every written field and never overwrites your original.
Local image metadata editor
Write a fresh, verified metadata set
Existing metadata is inspected first. The new copy is re-encoded, receives only the fields you enter below, and is scanned again before download.
Drop one image here
Choose a JPEG, PNG, or static WebP. The file stays on this device while the browser reads, rewrites, and verifies its metadata.
JPEG, PNG, static WebPOne file, up to 25 MB
On-device
No processing upload
New copy
Original stays unchanged
Re-scanned
Written fields verified
Editable XMP fields
Five portable fields, with a narrow promise
The editor deliberately avoids GPS, device serial numbers, AI workflow parameters, timestamps, and provenance claims. Those fields need different intent and stronger validation.
Description
A caption or context note stored in a portable XMP description field.
Creator
A person or organization name chosen by the user; authorship is not verified.
Copyright
A rights notice written exactly as entered, without validating ownership.
Keywords
A small Dublin Core subject list for cataloging and retrieval.
Inspect → write → verify
Editing remains an evidence-first workflow
The tool does not show a success toast immediately after writing bytes. It checks the new file and only enables download after the requested fields are found again.
- 01
Inspect the original
Validate the real file signature, apply the same safety limits, and load supported existing values into the form.
- 02
Create a fresh copy
Re-encode visible pixels, discard the original metadata container, and write only the chosen XMP fields.
- 03
Re-scan every field
Read the output with the same scanner, confirm the requested values, and provide a share-safe report without those values.
Important limits
This editor favors a predictable privacy boundary
It is not a lossless EXIF patcher or a provenance authoring system. The behavior below is part of the product, not fine print.
The image is re-encoded
Compression, file size, color profiles, and subtle pixel values may change even when dimensions and visible content remain the same.
Old metadata is not preserved
GPS, device, timestamps, AI workflow, thumbnails, and unsupported proprietary fields are not copied to the edited output.
No C2PA authoring
Possible markers require explicit removal consent. The tool cannot validate a signature or create replacement Content Credentials.
Images only
The V1 editor supports JPEG, PNG, and static WebP. PDF, HEIC, RAW, animation, audio, video, and Office documents remain outside this page.
Metadata editor questions
Know what will change before creating a copy
These answers separate portable XMP editing from EXIF patching, provenance authoring, and lossless container changes.
Does the image leave my device?
No. Inspection, re-encoding, XMP writing, verification, and download run in your browser. The tool does not send the image, filename, metadata values, or file hash to a processing API.
Which metadata fields can I edit?
The V1 editor writes title, description, creator, copyright, and keywords in a fresh Dublin Core XMP packet. Empty fields are omitted.
Does it edit every EXIF field?
No. GPS, camera details, serial numbers, dates, orientation, thumbnails, MakerNotes, AI workflow parameters, and proprietary fields are not editable here. The old metadata is discarded rather than patched in place.
Will image quality or file size change?
Yes, they can. The browser re-encodes visible pixels before writing the fresh XMP packet. The report shows the output format, dimensions, and input-to-output size, but file size is not a metadata verification signal.
Can it create or preserve Content Credentials?
No. C2PA support is conservative marker detection only. If a marker is found, creating an edited copy requires explicit consent because re-encoding removes or detaches it; the tool does not validate or forge credentials.
Which formats are supported?
One JPEG, PNG, or static WebP up to 25 MB. Animated WebP, APNG, multi-asset JPEG, HEIC, RAW, malformed files, and formats without the tested browser encoder path are rejected.
Only need to inspect?
Open the read-only Metadata Viewer to see supported fields without re-encoding or writing a new file.
Open Metadata ViewerWant a metadata-cleaned copy?
Use AI Metadata Remover when you want to discard supported file-level metadata without adding a fresh authoring set.
Open AI Metadata Remover