EXIF editing means rewriting the metadata block inside a JPEG so that fields like Description, Artist, and Copyright carry the credit text you actually want published. The EXIF Editor does this entirely in your browser, reads the current values from the three supported text fields, lets you type replacement values, and writes a fresh EXIF APP1 segment into a new JPEG file you download locally. The compressed image pixels are copied byte-for-byte rather than re-encoded, so picture quality is unaffected by the operation. The trade-off is that the old EXIF block is replaced rather than merged, which means GPS coordinates, camera settings, capture dates, embedded thumbnails, and unknown vendor fields are removed in the same step. That focused behavior is what makes the result predictable: you know exactly which three fields end up in the output, and you can verify them in a metadata viewer before publishing the image anywhere.
What EXIF Editing Actually Changes
A JPEG is not just a picture. It is a sequence of marker segments followed by a compressed image scan, and several of those segments can carry structured metadata. The most common metadata container is the EXIF APP1 segment, which holds a small TIFF directory describing the image. Editing EXIF, strictly speaking, means rewriting one or more values inside that TIFF directory while keeping the rest of the file intact.
A focused editor like the EXIF Editor is not trying to be a general metadata tool. It creates a brand new EXIF APP1 segment containing only three text fields, drops any earlier EXIF segments to prevent two conflicting sets of records, and copies the JFIF APP0 segment and the compressed scan bytes unchanged. The image scan is never decoded, so there is no resampling, no resizing, and no quality loss. The output is a real JPEG file with a standard EXIF block, not a screenshot, a metadata sidecar, or a browser preview that disappears when you close the tab.
The Three Credit Fields You Can Write
EXIF defines hundreds of tags, but the three written by this editor are the ones a general audience most often needs for attribution and rights notices.
| Field name | EXIF tag (hex) | Purpose | Byte limit |
|---|---|---|---|
| Description | 0x010E (ImageDescription) | Short factual note about the image | 120 bytes |
| Artist | 0x013B (Artist) | Creator or credit line | 120 bytes |
| Copyright | 0x8298 (Copyright) | Notice such as a year and rights holder | 120 bytes |
These are printable ASCII text values, which is why the editor rejects accented characters, non-Latin scripts, control characters, emoji, and long legal notices rather than silently mis-encoding them. The fields are not a license enforcement system: writing a Copyright string does not register a work, prove authorship, stop copying, or force any platform to display the text. If attribution has legal weight for you, keep a separate rights record in addition to whatever you embed in the image.
How to Edit EXIF Data in a JPEG
The whole workflow takes only a few clicks and runs on one file at a time, with the selected JPEG staying inside the current browser tab.
- Make a working copy of your original JPEG first, so the source is preserved if anything looks wrong later.
- Open the EXIF Editor and pick one JPEG up to 25 MiB from your device.
- Review any values already present in the three text fields so you know what is about to be replaced.
- Type the Description, Artist, Copyright, or any combination of the three using printable ASCII text only; leave the fields you do not want to change empty.
- Trim accidental leading or trailing spaces, double-check each value, and confirm that at least one of the three fields contains text.
- Click Write EXIF text, wait for the local validation step to finish, and download the new JPEG to your device.
- Reopen the downloaded file in a metadata viewer and confirm that Description, Artist, and Copyright match what you typed.
The page validates the JPEG marker stream before it builds the download, so a damaged input, a non-JPEG file renamed with a .jpg extension, or a browser download blocked by local settings is rejected with a clear error rather than producing a corrupt output. For a related workflow that focuses on stripping metadata instead of writing it, the guide to removing EXIF data from photos in your browser walks through the inverse case.
What Gets Removed When You Replace the EXIF Block
Because the editor rewrites only three text fields and discards the previous EXIF segment, several categories of metadata that a JPEG might carry are removed in the same step. This is intentional and is described up front so you can choose a different workflow when those details matter.
| Metadata category | Status after editing |
|---|---|
| Description, Artist, Copyright text fields | Replaced with your new values |
| JFIF APP0 segment | Kept when present |
| GPS coordinates | Removed (old block replaced) |
| Camera make, model, lens, exposure | Removed (old block replaced) |
| Capture date and time stamps | Removed (old block replaced) |
| Embedded preview thumbnail | Removed (old block replaced) |
| MakerNote or vendor extensions | Removed (old block replaced) |
| Other APP marker segments (for example IPTC, XMP) | Kept if present, since the editor only touches EXIF APP1 |
| Compressed image scan (pixels) | Copied unchanged, not re-encoded |
If the source held GPS data, a detailed camera profile, or a custom MakerNote block that you need to preserve, this focused editor is the wrong tool and a format-aware merge policy is required instead. The EXIF standard documented by the CIPA Exif Version 3.1 specification defines hundreds of tags with vendor extensions, and safely editing every one of them needs per-record rules that this single-page tool deliberately does not pretend to implement.
Field Limits, ASCII Rules, and File Constraints
The editor accepts printable ASCII text only, with each field capped at 120 bytes. That restriction is not arbitrary: the generated TIFF ASCII values have a deterministic byte representation across the standard readers this tool targets, which means a Description typed here will appear identically when you reopen the file in a third-party viewer. Names with accents, non-Latin text, control characters, or a long legal notice should be saved in another workflow rather than silently mis-encoded. The page surfaces an error instead of guessing a character encoding.
Other constraints worth knowing before you start: the upload limit is 25 MiB per file, truncated marker segments are treated as an error rather than silently repaired, at least one of the three fields must contain text before an output is created, and leading or trailing whitespace is trimmed so that accidental padding is not written into the record. Files outside this JPEG-only scope, including PNG, WebP, HEIC, TIFF, RAW formats, phone live photos, and images embedded in documents, are rejected outright. The JPEG file format itself is documented in the W3C JPEG File Interchange Format 1.02 reference, which is what allows the page to safely validate the marker stream before writing the new EXIF segment.
Verifying the Edited Metadata
Writing the fields is only half the workflow; confirming the result closes the loop. After the download finishes, reopen the new JPEG in any standard metadata viewer and check that the three text fields show exactly what you typed. The EXIF block in the output is a standard APP1 segment with little-endian TIFF byte order, NUL-terminated ASCII values, and the documented IFD0 entries for tags 0x010E, 0x013B, and 0x8298, so a wide range of viewers will read it without special handling.
If you also want a sanity check on the source file before editing it, a local EXIF inspection tool lets you read what is currently inside the JPEG. Readers who need that step can follow the guide to viewing EXIF data from any photo without uploading before deciding which fields to overwrite. Because some platforms strip or rewrite metadata at upload time, the same verification step is worth repeating in the destination application once the image is published, and a separate rights record is still the safer place to keep any legally important attribution.
When This Tool Is the Wrong Choice
This editor is built around a deliberately small contract: one JPEG, three text fields, no upload, no recompression. That focus is a strength when you want a predictable, inspectable result, but it rules out several real-world jobs. Editing GPS coordinates or orientation requires preserving and rewriting fields this tool removes. Batch processing dozens of files needs a script or a desktop client, since the page processes one image at a time. Changing a timestamp requires a tag this editor does not write. Adding a visible watermark or generating a license is outside its scope entirely. If any of those tasks is the real goal, the EXIF Editor is the wrong starting point and a more general metadata utility should be used instead.