Image Metadata Editor — EXIF/IPTC/XMP
Configure image metadata fields including title, creator, copyright, description, and keywords.
About Image Metadata Editor
Configure image metadata fields including title, creator, copyright, description, and keywords.
EXIF editing happens entirely inside your browser using piexifjs. Pixel data is left untouched — only the small EXIF block in the JPEG header is rewritten. Your file is never uploaded.
Editing is currently limited to JPEG because EXIF is JPEG-native; PNG and WebP use different metadata standards. To edit metadata in those formats, convert to JPEG first or use the Image Metadata Editor for IPTC/XMP fields.
Related tools
About Image Metadata Editor
Image Metadata Editor is a free, in-browser image tool. Configure image metadata fields including title, creator, copyright, description, and keywords. The page exposes a small surface — input, controls, output — so a first-time visitor can complete the job without reading documentation.
Behind the controls you see, standard browser APIs is doing the actual image editing and conversion. Formats are detected on load and the engine produces a deterministic output for any given input + options combination — useful when you need to re-run a job and expect identical results.
Image Metadata Editor runs the entire transformation inside your browser. The file is read by JavaScript running in the page, processed in-memory by standard browser APIs, and written back as a download. The browser is the runtime; the page is the interface. You can confirm what the tool does by opening the developer-tools Network tab during a run — the only requests are for the page's own static assets.
If you fit any of these descriptions, Image Metadata Editor should slot cleanly into your workflow: bloggers preparing hero images; photographers exporting deliverables; developers preparing UI screenshots. The tool keeps the controls focused on what matters for each of these use cases.
Image Metadata Editor is shaped for the gap between "I'll do it by hand" and "I'll script it." When the job is small enough that automating it would take longer than doing it, but annoying enough to want a focused tool — that is the situation this page is built for.
The 0 MB ceiling on input size is the only fixed limit. Output files are produced in standard formats that every common viewer recognises, and the tool runs the same way regardless of how many times you have used it during the session.
Even on its own, Image Metadata Editor composes well with the rest of your toolkit. The output is a standard image file that opens in any program that handles the format, so the result of one run can become the input to whatever step you use next.
Some notes on the design of Image Metadata Editor. The page is intentionally narrow: one input, the controls relevant to the task, and one output. Adding unrelated features would make the common case slower for the majority of users, so the surface is held to what people actually use.
Image Metadata Editor returns the result as a download. If you are running multiple jobs, the output names will not collide as long as the input names differ. You can re-run with different settings as many times as you like; each run produces a fresh file with no caching trickery in between.
Some background on the design choices behind Image Metadata Editor: every option you see on the page is there because a real workflow needs it, and every option that is not shown has been deliberately omitted to keep the common case fast. The bias is toward minimal-but-complete.
Image Metadata Editor produces deterministic output: the same input plus the same options always produces the same result. That predictability matters when the result has to match an upstream specification or be reproducible later.
Tips from users who reach for Image Metadata Editor regularly: process one input first to confirm the settings produce what you expect before committing to a batch; treat the page as the working surface and avoid leaving large jobs running in a backgrounded tab where the browser may throttle JavaScript; and if a particular file fails, check whether the source is intact by opening it in its native viewer — most "tool errors" are actually input errors.
If Image Metadata Editor appears to hang, the engine is almost certainly still working — large inputs simply take longer to process inside a browser than they would on a server with multi-core scheduling. For inputs near the 0 MB cap, give it up to a minute on a typical laptop before assuming something is stuck.
Image Metadata Editor is one of many single-purpose tools in the catalog. Each is built around the same single-page model. Use this one, close the tab, and come back the next time you need the same job done. None of the tools require prior knowledge of the others — each page is self-contained.
How it works
- 1Reach the Image Metadata Editor page in your browser to begin.
- 2Select the image file you want to process — drag-and-drop and the file picker both work.
- 3Tweak the controls if the defaults are not quite right for your input. The options are kept short and labelled in plain language.
- 4Click to start the job. The engine (standard browser APIs) processes the input in the page; you can watch the progress indicator until it completes.
- 5Save the output when it is ready.
- 6Repeat the process for additional inputs whenever you need to. The page stays loaded, so subsequent runs are quick.
Common use cases
- Generate a square thumbnail from a wide marketing photo using Image Metadata Editor.
- Optimise a product photo so it loads quickly on a slow connection.
- Convert a batch of camera files into web-friendly formats.
- Sharpen a slightly soft photo before sending it to print.
- Convert a phone screenshot into a CMS-friendly format.
- Resize a hero image for a landing page without losing crispness.
- Apply a quick filter for a social-media post.
- Produce a printable poster from a single source image.
- Prepare a transparent logo for use over different backgrounds.
FAQ
Which metadata standards are supported?
EXIF (camera/photo metadata), IPTC (news-photo legacy fields), and XMP (XMP standard XML packets) are all visible. Editable fields focus on the EXIF IFD0 string tags — title, artist, copyright, description, software — because those are the tags that round-trip cleanly across desktop apps without re-encoding pixels.
What about IPTC keywords for SEO?
Major image search engines (Google Images, stock photo platforms, DAMs) read IPTC keywords and XMP subject tags when indexing. Adding 5–10 descriptive comma-separated keywords helps your photos surface in image search results.
Will the editor preserve my colour profile?
Yes. The ICC profile chunk and JFIF container blocks are kept intact. Only the EXIF segment inside the JPEG file is rewritten.
Why does this only edit JPEG?
JPEG's APP1 marker can be safely re-written without touching pixel data. PNG/WebP/HEIC need a full re-encode to update metadata, so we read those formats but only edit JPEG to guarantee a lossless round-trip.
Where do edits show up?
Title and description appear under "Subject" / "Comments" in Windows file properties, "Description" in macOS Preview, and the "Title" / "Caption" / "Creator" fields in DAM/photo-management apps that read XMP metadata.
Why is in-browser metadata processing slower than online tools?
Server-side editors run native binaries (ExifTool, libexif) compiled to machine code on dedicated hardware. Our engine uses exifr for parsing and piexifjs for editing, both pure JavaScript libraries running single-threaded inside your browser tab. That's typically 2–5× slower than a backend pipeline. The trade-off is total privacy: your image and its embedded GPS coordinates, camera serials, and other personal metadata never leave your device. The whole point of metadata tools is privacy, and a few extra milliseconds is a fair price to pay for keeping that data on your machine.
Is my image uploaded to a server?
No. exifr parses the file header in your browser memory, and piexifjs writes any changes locally. The processed file is offered as a direct download. Nothing is transmitted, no account is required, and closing the tab discards every byte from memory immediately.
Which image formats are supported?
Reading metadata works on JPEG, PNG, WebP, AVIF, HEIC, TIFF, GIF, and most other formats exifr supports. Editing and removing EXIF tags is fully supported on JPEG (the most common camera format). For PNG/WebP/etc., the remover re-encodes the image through canvas, which strips all embedded metadata as a side effect.
Which metadata fields can I see or edit?
Viewing surfaces all standard EXIF tags (camera make/model, lens, aperture, ISO, shutter speed, focal length), GPS coordinates, IPTC photo metadata (title, caption, keywords, copyright), XMP packets, ICC colour profile info, and JFIF container fields. Editing focuses on the human-readable string tags inside the IFD0 block — title, artist, copyright, description, software — which are the fields most authoring tools respect.
Does editing or removing metadata change the pixels?
No, JPEG metadata edits are byte-level container rewrites that leave the compressed image data untouched. There is zero pixel re-encoding and zero quality loss. For non-JPEG formats the metadata remover does re-encode pixels through a canvas, which strips every embedded tag at the cost of a small re-compression pass.
Which browsers are supported?
Recent Chrome, Edge, Firefox, Safari, and other Chromium-based browsers all work. The tool only relies on standard ArrayBuffer, FileReader, and Canvas APIs that have been universally supported for over a decade.
Is there a watermark or sign-up wall?
No. The tool is completely free, requires no account, attaches no watermark, and shows no popup ads on your output. A small fair-use throttle runs in the background to discourage automated abuse, but it does not affect normal one-off use. The downloaded file is exactly what your browser produced — nothing more, nothing less.
Are jobs run with Image Metadata Editor stored anywhere?
Favtoo keeps no copy of your file because Favtoo never receives your file. Image Metadata Editor runs entirely in your browser, the input is held only in your tab's memory, and closing the tab discards it. There is no opt-in cloud history, no "recent jobs" panel synced to an account, and no server-side retention to configure — the architecture simply has nowhere for your file to be stored.
How many times per day can I use Image Metadata Editor?
Inputs are capped at 0 MB per file, which keeps memory usage stable across phones, tablets and older laptops. You can run Image Metadata Editor as often as you need; every run produces a full-quality result.
Does Image Metadata Editor support batch processing?
Image Metadata Editor processes one input at a time by design — it keeps memory usage predictable on lower-end devices and makes results easier to verify. To handle a folder, run the tool once per file; the page stays loaded between runs and remembers your last-used settings, so the second run is essentially instant.
Why is my browser prompting me when I open Image Metadata Editor?
Image Metadata Editor only needs the standard web platform — file picker access for the inputs you choose to load, and optionally clipboard access if you copy the result rather than downloading it. There is no microphone, camera, geolocation or background-permission request, because none of those are needed for the work the tool does.
Why did Image Metadata Editor reject my input?
Failures usually fall into one of three buckets: the input is in an unsupported format, the input is over the size cap, or the input is structurally malformed (a truncated download, a partial export, or a stream the engine does not recognise). The first two are easy to confirm — check that your file is in a supported format and that it is below 0 MB. For the third, opening the file in its native viewer first is the fastest way to confirm the source is intact.
Will Image Metadata Editor ask me to pay to download the result?
Image Metadata Editor is free to use. The processing runs in your browser, which keeps the per-user cost low enough that the tool can be offered openly. The download is the same file the engine produced — you can use it for as many runs as you need.
Can I use Image Metadata Editor on documents that contain personal data?
Your file is processed inside your browser by standard browser APIs. The engine reads the file's bytes from your tab's memory, computes the result, and writes the result back into the tab. You can confirm what the page does by opening developer tools and watching the Network tab during a run — the requests you see are for the tool's static assets only.
Are there any restrictions on using Image Metadata Editor at work?
Image Metadata Editor can be used for personal and commercial work alike — there is no separate "business" licence to purchase. The output you generate is yours to use however you want, including in client deliverables, internal documents, or commercial products. Favtoo's only ask is fair, individual use; the tool is not designed to be embedded as a backend service or wrapped behind an API for resale.