Photoshop can read EXIF metadata from a JPEG but has no built-in dialog for rewriting the three standard credit fields — Description, Artist, and Copyright — which is why most people who search for an in-app solution end up on a dedicated EXIF editor instead. Photoshop's File > File Info panel exposes title, description, and copyright through the IPTC and XMP schemas, and on save those are written into the file as XMP and IPTC blocks rather than touching the original EXIF APP1 segment. The camera-original EXIF IFD0 text fields — Description (tag 0x010E), Artist (0x013B), and Copyright (0x8298) — stay exactly as the camera wrote them. If your destination application, stock submission portal, or internal archival workflow specifically reads those IFD0 EXIF tags, Photoshop is the wrong hammer. The cleanest path for the three standard EXIF credit fields is a small browser-based EXIF editor that rewrites only the EXIF APP1 segment and copies the compressed JPEG image scan without re-encoding it. That is a different tool from Photoshop with a different trade-off, and the rest of this article walks through exactly what it does, what it does not do, and how to run it on a JPEG without leaving your browser.
What Photoshop Actually Does With EXIF Data
Photoshop treats EXIF as read-only metadata. When you open a JPEG, Photoshop parses the EXIF APP1 segment to populate fields it shows in File > File Info > Camera Data (or in the older Camera Data panel). What you can edit sits in a separate IPTC and XMP layer: Document Title, Description, Instructions, Author, Copyright Notice, and a few more. Those edits are written back into the file as XMP (an APP1 segment with the "http://ns.adobe.com/xap/1.0/" namespace) and IPTC (an APP13 segment with the IIM record), not into the original EXIF IFD0. On Save As or Export, the camera EXIF block is left intact. Some workflows — like the legacy "Save for Web" dialog — strip or reduce metadata entirely, but none of them target the three EXIF IFD0 text fields for editing.
The practical consequence is that any consumer of your JPEG that only reads the EXIF IFD0 tags will not see your edits. Older stock portals, certain digital asset management systems, and any application that ignores XMP fall into that bucket. If you need those specific IFD0 fields populated, you have to edit the EXIF APP1 segment directly — which Photoshop does not offer a dialog for.
Why a Browser-Based EXIF Editor Handles Credits Better
The EXIF Editor is built for exactly that job: rewriting the three IFD0 text fields in a JPEG without touching the image pixels. The whole operation runs inside the current browser tab. The selected JPEG is read locally, the page parses the EXIF APP1 segment to show any values already in those three fields, and a new EXIF block is written from your typed input. Nothing is uploaded to a server, queued in a remote job, or stored in an account.
The trade-off is deliberate and stated up front: the tool replaces the existing EXIF block with a new one that contains only Description, Artist, and Copyright. It does not merge or preserve GPS, camera settings, capture dates, embedded thumbnails, MakerNote records, or any other EXIF field. The compressed JPEG image bytes after the metadata headers are copied without canvas decoding, so the pixels are not re-encoded or resized. If you need to keep the full camera EXIF block intact, a specialist archival workflow is the right place to do it. If you need the three standard credit fields rewritten cleanly with a transparent, inspectable tool, the EXIF Editor is purpose-built for that.
Write Description, Artist, and Copyright Into a JPEG
- Open the EXIF Editor page in your browser to read the JPEG locally in the current tab.
- Click the file picker and choose one JPEG file up to 25 MiB. PNG, WebP, HEIC, TIFF, RAW, and other non-JPEG formats are outside scope — pick a real JPEG, not a file that has simply been renamed with a .jpg extension.
- Wait for the page to finish parsing. Any existing values it finds in the Description, Artist, and Copyright fields are displayed so you can see what is currently in the file.
- Type replacement text into any combination of the three fields. Use printable ASCII only. Names with accents, non-Latin text, control characters, or emoji will be rejected by design so the editor does not silently guess a character encoding.
- Trim leading and trailing spaces by hand before you write. The editor trims them too, but checking first prevents surprise redactions.
- Make sure at least one of the three fields contains text. Empty submissions are blocked.
- Click Write EXIF text. The page constructs a new EXIF APP1 segment with the TIFF byte order and NUL-terminated ASCII values for the three IFD0 tags, replaces earlier EXIF APP1 segments to avoid two conflicting sets of fields, retains the JFIF APP0 segment if present, and copies the image scan bytes verbatim.
- Download the resulting JPEG. The file is a real JPEG with a standard APP1 EXIF block, not a screenshot, a metadata sidecar, or a browser-only preview.
What the Editor Removes and What It Keeps
The editor is intentionally narrow. Before you write, here is the precise contract for the three supported fields:
| Field | EXIF tag | Typical use | Length cap |
|---|---|---|---|
| Description | 0x010E | Short factual note about the image | 120 bytes |
| Artist | 0x013B | Creator name or credit line | 120 bytes |
| Copyright | 0x8298 | Year and rights holder, e.g. "2026 Jane Doe" | 120 bytes |
The 120-byte limit applies to each field independently and is a deliberate constraint. The TIFF ASCII writer used by the editor produces a deterministic byte representation that standard EXIF readers can parse unambiguously; longer or non-ASCII strings would force a guess at character encoding, and the editor refuses to guess.
What gets replaced: every existing EXIF APP1 segment in the source file is removed. That includes GPS coordinates, camera make and model, lens, capture date and time, ISO, shutter speed, aperture, embedded thumbnails, MakerNote blocks, and any unknown or vendor-specific EXIF records.
What gets kept: the JFIF APP0 segment (when present), the compressed JPEG image scan bytes, and any non-EXIF JPEG application segments. The image is not decoded into a canvas, so there is no quality loss from re-encoding. For authoritative details on the EXIF specification, see the CIPA Exif standard. For the surrounding JPEG marker structure the editor preserves, see the W3C JFIF specification.
Verifying the New EXIF Block After Download
After the download, use a metadata reader such as the in-browser EXIF Viewer to open the new file and confirm the Description, Artist, and Copyright rows now show what you typed. A reader-friendly walkthrough of each EXIF field is available at How to View EXIF Data of a Photo and Read Each Field.
If a destination website strips or rewrites metadata on upload (most social platforms do), the EXIF credit fields will not survive. Check the exported JPEG in the destination application after upload, and keep a separate written record of authorship if licensing has legal importance. The EXIF copyright notice is descriptive metadata, not a licence, registration, watermark, or legal enforcement mechanism.
Related Browser-Based EXIF Tasks You Can Run Locally
If your real goal is to put your name on a JPEG and Photoshop's IPTC and XMP workflow is not what the destination needs, the EXIF Editor is the closest match. For visible attribution that survives every metadata stripper, a watermark is a stronger choice — see How to Add a Photoshop-Style Watermark in Your Browser for a local, in-browser approach that produces a layered PNG overlay.
For the opposite task — cleaning a JPEG before you share it so GPS and camera details do not leak — an EXIF Remover rebuilds the file without the EXIF segment while leaving the compressed pixels intact. If you need to read the current values first, run the file through a metadata viewer, decide which fields you want to keep, and only then decide whether to edit, remove, or leave the metadata alone.