This page can write Description, Artist, and Copyright fields into one JPEG locally in your browser while leaving the compressed image pixels unchanged. The EXIF Editor tool does this by reading the selected file in the current browser tab, creating a focused standard EXIF block, and offering a new JPEG for download. Nothing is uploaded to a conversion server, stored in an account, or placed in a remote processing queue. It is useful when you need a short factual note, creator credit, or rights notice inside a JPEG, but it is deliberately narrow: it edits three text fields rather than the full camera metadata set. Before using it, make a duplicate of the original because the tool replaces existing EXIF, including GPS, camera settings, capture dates, thumbnails, and unknown fields. The compressed image scan is copied rather than re-encoded, so the visible JPEG pixels are not resized or recompressed. Android phone and file-picker compatibility have not been verified; treat any Android-specific instructions below as conditional on your browser supporting local file selection and downloads.

What this Android browser workflow can edit
On Android, online EXIF editing can mean a browser page that operates on a local copy rather than an installed photo-editing app. EXIF Editor follows that model. After you select a JPEG, the page reads the three supported EXIF text fields so you can review their current values before replacing them. You may fill any combination of the fields, but at least one must contain text before the editor creates an output.
| Field | What to enter | Important boundary |
|---|---|---|
| Description | A short factual note about the image | It is stored as metadata, not printed over the picture |
| Artist | A creator name or credit line | It does not prove who created the image |
| Copyright | A notice such as a year and rights holder | It is not a licence or enforcement mechanism |
Each field accepts printable ASCII text and is limited to 120 bytes. Leading and trailing spaces are trimmed. Accented names, non-Latin text, control characters, emoji, and long legal notices fall outside the writer's safe input range; the page shows an error instead of guessing a character encoding. Keep a separate rights record when multilingual attribution, exact legal wording, or a complete licence notice matters.
Edit JPEG credit fields on Android
Use this sequence when the source is a valid JPEG, your browser can select and download local files, and replacing its EXIF block is acceptable. The browser handles the file locally.
- Duplicate the source file. Save a working copy in Files or your gallery and keep the untouched original. Confirm that the working JPEG is no larger than 25 MiB.
- Open EXIF Editor in your Android browser. When you are ready, use the browser's file picker to choose the single JPEG from local storage. The selected file is read in the current tab and is not uploaded.
- Review the detected values. The page reads any existing Description, Artist, and Copyright entries. These are the only three original EXIF text fields included in the focused editing workflow.
- Enter the text you want to publish. Update one field or any combination of the three. Use printable ASCII only, keep each field within 120 bytes, and ensure at least one field is populated. A field you leave empty will not receive a replacement value.
- Select Write EXIF text. The editor validates the JPEG marker stream, removes any earlier EXIF APP1 segment, inserts a new focused EXIF block, and prepares the updated JPEG for download. The result is a real JPEG file with a standard APP1 EXIF block, not a screenshot, metadata sidecar, or browser-only preview.
- Download and save the new JPEG. Accept the browser's download prompt and keep both files until verification is complete. If Android settings block the download, review the browser's download permissions; metadata editing cannot repair a browser-level download block.
- Reopen the downloaded copy in a metadata viewer. Check that the displayed Description, Artist, and Copyright match what you entered after leading and trailing spaces are trimmed. Always inspect the exported file rather than assuming the original was changed.
What the local JPEG rewrite changes
A JPEG can contain several application segments before its compressed image scan. EXIF Editor validates the bounded JPEG marker stream, retains the JFIF APP0 segment when present, removes earlier EXIF APP1 segments to prevent conflicting field sets, and inserts one EXIF APP1 segment. The new block uses a little-endian TIFF IFD0 structure, standard directory entries, and NUL-terminated ASCII values intended for compatible metadata readers.
The image scan bytes after the metadata headers are copied without canvas decoding. Existing non-EXIF JPEG data and the compressed image pixels are not re-encoded or resized. This is therefore a metadata-header rewrite rather than a quality-changing image export. For background on the relevant structures, consult the CIPA Exif Version 3.1 standard and the W3C JPEG File Interchange Format 1.02 specification.
Check what a new EXIF block will replace
This editor does not merge every existing camera record into a new block. It creates a new EXIF block containing only Description, Artist, and Copyright. The previous EXIF block is replaced, so this approach trades broad metadata retention for a small, inspectable credit-record update.
| Part of the JPEG | Result after editing |
|---|---|
| Compressed image scan | Copied without re-encoding or resizing |
| JFIF APP0 segment | Kept when present |
| Existing EXIF block | Replaced with a new block containing the three supported text fields |
| GPS, camera settings, capture dates, orientation, and embedded thumbnail | Removed with the old EXIF block |
| MakerNote and unknown or vendor-specific EXIF fields | Removed with the old EXIF block |
| Existing non-EXIF JPEG data | Retained |
If the original GPS information, camera settings, capture dates, or another EXIF field is important, use a specialist archival workflow instead. The three editable fields are also not a visible watermark, licence, registration, proof of authorship, or way to prevent copying. Some websites strip or rewrite metadata during upload, and the editor cannot make a platform display the fields. Keep a separate rights record when attribution or licensing has legal importance; the tool does not provide legal advice.
Limits and failures to handle on Android
- One file at a time: The page accepts one JPEG up to 25 MiB and has no batch mode.
- JPEG only: PNG, WebP, HEIC, TIFF, RAW, phone live photos, and images embedded in documents are outside the tool's scope. Renaming a file with a .jpg extension does not make an unsupported format into a valid JPEG.
- Valid JPEG structure required: Malformed or truncated marker streams cause an error. Damaged inputs and non-JPEG files renamed as JPEGs cannot be repaired by metadata editing. The tool validates the marker stream before constructing an output and cannot repair a corrupt source.
- Strict text input: Every field must use printable ASCII, contain no more than 120 bytes, and remain within the three supported fields. At least one field must contain text.
- Focused feature set: There is no GPS editor, date editor, orientation editor, image conversion, OCR, or external lookup.
- Normal browser responsibility: A download blocked by local Android or browser settings is outside what the editor can repair, so review the browser's download configuration before trying another workflow.
Verify the download before sharing it
Reopen the downloaded JPEG in a metadata viewer to confirm the fields. Also confirm that the downloaded file opens normally as a JPEG and that the visible image still looks correct.
Metadata verification should happen again in the destination application when the image will be uploaded, because that service may remove or rewrite metadata during processing. If the credit needs to remain visible regardless of metadata support, use a visible overlay instead of relying on EXIF alone. If ownership or licence terms must remain enforceable or easy to reference, retain a separate rights record alongside the exported JPEG.
For a deeper look, see EXIF Viewer: Read JPEG Data and GPS.