The EXIF Editor is a browser-based tool that adds or replaces three standard EXIF text fields—Description, Artist, and Copyright—inside a JPEG file. Everything happens locally: the JPEG is read in your browser tab, a new EXIF block is written, and a modified file is offered as a download. No file is uploaded, stored in an account, or placed in a remote processing queue. The compressed image scan is copied unchanged, so pixels are not re-encoded, resized, or recompressed.
This focused approach works well for a specific kind of task: updating the three text fields that credit or describe an image before sharing or publishing it. Photographers exporting from Lightroom Classic, contributors preparing images for a stock library, or anyone correcting an attribution line on a finished JPEG can use the tool to set the EXIF fields they actually want published. The trade-off, stated up front, is that the existing EXIF block is replaced—GPS, camera settings, capture dates, embedded thumbnails, and unknown EXIF fields are removed—while non-EXIF segments such as JFIF are preserved.

What the EXIF Editor Does
The tool performs one narrow job: it inserts a single EXIF APP1 segment into a JPEG that contains three IFD0 text tags. The tags follow the standard TIFF byte order and use NUL-terminated ASCII values, which means standard metadata readers (including Lightroom Classic, Windows Explorer, and macOS Preview) can read them back without special handling. The implementation reads the three supported fields dynamically after file selection, then constructs a new EXIF block. Earlier EXIF APP1 segments are removed to avoid two conflicting sets of fields. The JFIF APP0 segment, when present, is kept, and the compressed scan bytes after the metadata headers are copied without canvas decoding.
| Property | Behavior in the EXIF Editor |
|---|---|
| File input | One JPEG up to 25 MiB, selected in the browser |
| Processing location | Local browser tab; no upload, no account, no server queue |
| Editable fields | Description (0x010E), Artist (0x013B), Copyright (0x8298) only |
| Text encoding | Printable ASCII, up to 120 bytes per field, leading and trailing space trimmed |
| Other EXIF data | Replaced entirely—GPS, camera settings, dates, thumbnails, MakerNote, and unknown fields are removed |
| Non-EXIF JPEG data | JFIF APP0 segment preserved; compressed image scan copied unchanged |
| Image pixels | Not re-encoded, not resized, not recompressed |
| Output | A real JPEG file with a standard APP1 EXIF block, offered as a local download |
Why a Focused EXIF Editor Exists
JPEG metadata can hold GPS coordinates, camera serial details, MakerNote records, thumbnails, editing history, copyright fields, and application-specific blocks. Editing every vendor extension safely requires a format-aware merge policy for each kind of record. A general-purpose metadata editor may preserve all of that, but it also brings complexity and, in some cases, the need to install software or upload files. The EXIF Editor takes the opposite route: a transparent, inspectable local operation that creates a new EXIF block containing only the three documented IFD0 text fields. Anyone who needs to preserve GPS, camera settings, or capture dates should keep the original file or use a specialist archival workflow.
For many common tasks—setting a copyright year, correcting an artist name, or adding a short factual description—these three fields are enough. The tool accepts printable ASCII text only and limits each field to 120 bytes. That restriction is intentional: the generated TIFF ASCII values have a deterministic byte representation across the standard readers the tool targets. Names with accents, non-Latin text, control characters, emoji, or a long legal notice should be saved in another workflow; the page shows an error rather than guessing a character encoding. At least one of the three fields must contain text before an output is created.
Set the Three EXIF Fields: Step-by-Step
The verified operating steps fit inside a single browser tab:
- Choose one JPEG up to 25 MiB. The page reads the three supported EXIF text fields locally after selection. If the file is not a valid JPEG, is larger than 25 MiB, or has a truncated marker segment, the page shows an error rather than producing output. The local writer validates the JPEG marker stream before it constructs the download and leaves no stale link after a failed selection.
- Enter a Description, Artist, Copyright notice, or any combination of the three using printable ASCII text. Leading and trailing space is trimmed so accidental padding is not written into the record. Duplicate the original file first and select that copy, fill only the credit fields you can verify, and keep the original whenever other metadata matters.
- Select Write EXIF text, download the new JPEG, and reopen it in a metadata viewer to confirm the fields read back exactly what was typed. A damaged input or a non-JPEG file renamed with a JPEG extension cannot be repaired by metadata editing.
Using This Tool After Exporting from Lightroom Classic
Lightroom Classic stores EXIF metadata in a read-only catalog during normal editing and only writes metadata back to files at export. The Export dialog can include or strip metadata as a whole, but it does not let you edit the three IFD0 text fields in isolation. Photographers who need to add a copyright line, correct an Artist credit, or write a short Description without touching the rest of the catalog can export the JPEG, run it through the EXIF Editor, and re-import the modified file.
A typical workflow looks like this: select the image in the Library module, choose File > Export, pick JPEG as the file format, and set Quality to 100 to avoid recompression. Under Metadata, choose All Metadata so the exported file contains the existing EXIF data, then save the export to an accessible folder. Open the EXIF Editor, select the exported JPEG, review the current values for the three fields, enter the replacements, and download the result with a distinct filename so the original export stays intact.
Re-import the modified JPEG into Lightroom Classic or open it in a metadata viewer such as the EXIF Viewer to confirm the displayed Description, Artist, and Copyright match what was typed. If the source held GPS or camera fields that are still needed, keep the original export as the authoritative copy and use a specialist archival workflow for those records.
What Happens to Other Metadata
The new EXIF block contains only the three documented IFD0 text fields. Everything else in the original EXIF block is removed:
- GPS coordinates are dropped. The modified file will not contain location data.
- Camera settings such as aperture, shutter speed, ISO, and focal length are removed from the JPEG itself. Lightroom Classic's catalog retains this information separately, but it will not be visible in the modified file.
- Capture dates (DateTimeOriginal, DateTimeDigitized, DateTime) are removed. If a date matters for the destination, include it in the Description field.
- Embedded thumbnails and any MakerNote or vendor-specific blocks are removed because they live inside the EXIF APP1 segment that gets replaced.
- JFIF APP0 is preserved when present, and the compressed scan bytes after the metadata headers are copied without canvas decoding.
The image scan is not re-encoded. This is not a quality-changing image export; it is a metadata edit. The page also limits uploads to 25 MiB and treats truncated marker segments as an error, because malformed headers can point outside a file or claim an unrealistic length. Metadata is a compact header, but it can still break a file when it is wrong, which is why the local writer validates the marker stream before constructing the download.
Limits Worth Knowing Before You Start
Several interacting limits change whether the tool can complete the task. Knowing them up front avoids surprises:
- 120 bytes per field, printable ASCII only. The byte limit is the storage size, not a character count. The page rejects non-ASCII characters rather than guessing an encoding, so accents, emoji, control characters, and non-Latin scripts need another workflow.
- 25 MiB maximum file size. Larger JPEGs cannot be processed by the page.
- JPEG only. PNG, WebP, HEIC, TIFF, RAW, phone live photos, and images embedded in documents are out of scope.
- One file at a time. There is no batch mode, GPS editor, date editor, orientation editor, image conversion, OCR, or external lookup.
- At least one field must contain text. An empty form produces no output.
What the EXIF Fields Can and Cannot Do
Description is useful for a short factual note about the image. Artist is a creator or credit line. Copyright is a notice such as a year and rights holder. These fields are not a licence enforcement system and cannot prove authorship, prevent copying, or force a platform to display the information. The EXIF Editor does not create a Creative Commons licence, register a work, add a visible watermark, or provide legal advice.
Some websites strip or rewrite metadata during upload, so the exported JPEG still needs a normal review: check it in the destination application and keep a separate rights record if attribution or licensing has legal importance. Treat the Copyright field as a credit line carried inside the file, not as a guarantee.
Pitfalls to Watch For
Small oversights can cost time or data. Here are the pitfalls that come up most often:
- Assuming all metadata is preserved. The tool replaces the existing EXIF block, so GPS, camera settings, and capture dates are removed. Always keep the original file if those details matter. Use a viewer like the EXIF Viewer to inspect the source first.
- Using non-ASCII characters. Accents, emoji, and non-Latin scripts trigger an error. If those characters are required, add them as a visible watermark in another tool rather than relying on metadata.
- Overwriting the original export. Save the modified JPEG with a new filename so the original export stays recoverable.
- Skipping verification. After download, reopen the file in a metadata viewer and confirm the three fields read back exactly what was entered. Some platforms strip or rewrite metadata during upload, so a final check in the destination application is worth the few seconds it takes.
- Editing a non-JPEG file. If the source is PNG, WebP, HEIC, TIFF, or RAW, convert to JPEG first—using something like PNG to JPG or WebP Converter—but be aware that format conversion can introduce compression artifacts or alter transparency.
Alternatives for More Granular Metadata Editing
The EXIF Editor is deliberately small. Tools and workflows that cover a wider scope are appropriate when more than three text fields need attention:
- Lightroom Classic's Metadata panel and presets: Good for editing IPTC fields (keywords, captions, copyright status, contact details) and for applying metadata templates across many images. EXIF text fields remain effectively read-only in this workflow.
- ExifTool (command line): A powerful, open-source utility that reads and writes metadata across many formats and supports selective field updates and batch processing. It requires technical comfort and is not beginner-friendly.
- Adobe Photoshop's File Info dialog: Allows editing of EXIF and IPTC fields, including Description, Artist, and Copyright. Reachable from Lightroom Classic via Edit In > Edit in Adobe Photoshop. May recompress the image depending on the save options chosen.
- Dedicated metadata editors such as Exif Pilot, PhotoME, or GeoSetter: Offer granular control over EXIF, IPTC, and GPS data. Typically require installation and may not process files purely locally.
For the narrow job of writing Description, Artist, and Copyright into a JPEG without uploading, recompressing, or installing software, the EXIF Editor is the right size of tool. Keep the original file whenever GPS, camera settings, capture dates, embedded thumbnails, or vendor-specific records still matter, and treat the EXIF copyright field as a credit line rather than a license or legal enforcement mechanism.