WEBP Metadata Editor

Edit the title, author, copyright, camera and date fields embedded in a photo, then export it as WEBP with your changes written into the file.

How to Edit Metadata in a WEBP Image

Upload a photo, fill in the fields you want written, save the metadata, then download the file with those values embedded inside it.

Step 1

Upload your photo

Drop a single image into the box or browse for it, and the file loads into the editor panel.

Step 2

Fill in the fields

Type the title, author, copyright, software, camera or date values you want the file to carry.

Step 3

Save and download

Press Save Metadata, choose WEBP as the output format, then download the file with the values written in.

Why Editing Embedded Metadata Beats Keeping a Separate Spreadsheet Record

Copyright lines, authorship and capture dates are the sort of details that matter enormously on the rare occasion they are needed, and are almost impossible to reconstruct after the fact. A photograph published three years ago with no embedded credit is a photograph whose ownership has to be argued from emails and file names. Writing the details into the file at the point of export takes a minute and removes that argument permanently.

The reason embedding works where a separate record fails is that the data travels with the image. A spreadsheet of credits lives in one place and goes stale the moment a file is copied, renamed, handed to a client or pulled into a different content system. Metadata embedded in the file survives all of it, because it is part of the file rather than a note about it, and it can be read years later by anyone who opens the image with software that cares.

This editor writes the fields that carry the most practical weight. Title and author identify the work and its creator, copyright states the ownership claim in the place where people actually look for it, and software records what produced the file. The camera make and model let you correct a mislabelled body or fill in a value that was never written. Three separate date fields cover the moments that get confused with one another: when the file was last modified, when the photograph was actually taken, and when the original was digitised.

The rule for blank fields is the one worth remembering, because it behaves differently from most forms. Leaving a field empty does not mean leave it alone; it means remove that value from the file. That is deliberate and useful, since it gives you a way to delete a stale credit or an unwanted software tag without needing a separate stripping tool. Fill in only what you want written, and leave the rest empty if you would rather they were gone.

WEBP is handled properly rather than ignored. Writing metadata into WEBP is not the same job as writing it into JPEG, because the container is built from chunks and needs a specific extended header to declare that an EXIF block is present. The writer adds that header, inserts the EXIF chunk, and rewrites the container size accordingly, so the values you typed genuinely survive into the exported WEBP file instead of being silently dropped at the last step.

Editing is separate from exporting, which keeps things predictable. Nothing is written until you press Save Metadata, so you can review the fields before committing, and the changes are applied when the file is produced. Output starts on Keep Original, so choose WEBP when you want a compact web friendly result carrying the values you just set. The whole job runs in your browser, so the photograph is never uploaded anywhere.

Nine Practical Fields

Title, author, copyright, software, camera make and model, plus three separate date fields are all editable.

Blank Means Remove

Leaving a field empty deletes that value from the file, which is how you drop a stale credit or software tag.

Real WEBP Writing

The WEBP container gets its extended header and EXIF chunk written properly, so your values survive the export.

Review Before Commit

Nothing is applied until you press Save Metadata, so every field can be checked before the file is produced.

Three Distinct Dates

Modified, taken and digitised are separate fields, which stops the moments that are usually confused from colliding.

Stays on Your Device

Reading and writing happen locally in your browser, so unpublished photographs are never uploaded to any server.

FAQ

Frequently Asked Questions

Nine of them: title, author, copyright, software, camera make, camera model, and three separate date fields covering when the file was modified, when the photo was taken and when it was digitised.

The value is removed from the file rather than left untouched. That is deliberate, and it is the easiest way to delete a stale credit or an unwanted software tag without reaching for a separate stripping tool.

Yes. WEBP needs a specific extended header to declare that an EXIF block is present, and the writer adds that header, inserts the chunk and rewrites the container size so your values are not dropped.

Yes, Keep Original is the default and it preserves what you uploaded. You can also switch the output to JPG, PNG or WEBP if you want the edited file delivered in a different format.

When you download. Nothing is written until you press Save Metadata, so you can review every field first, and the values are then embedded in the file that gets produced.

No. The editor works on one image at a time, because each file has its own set of values to fill in. Work through them one by one and download each finished file before loading the next.

No. Only the metadata blocks are written. The pixel data of your photograph is carried through untouched, so the image looks exactly as it did before you edited the descriptive fields.

Because the moments are genuinely different and constantly confused: when the file was last saved, when the photograph was actually captured, and when an original was first scanned or digitised from film.

No. The editor runs entirely in your browser, so there is nothing to install, no account to create and no plugin to configure at all before you can start editing metadata.

No. Reading the existing values and writing the new ones both happen locally on your own device, so nothing is transferred or stored anywhere else, which keeps unpublished client work completely private.