1Upload the WebP images you want to work on; the file opens on an editable canvas in your browser with nothing installed.
2Crop, rotate, resize, draw, add text and shapes, or adjust colour — every change lands on a working copy, never on your upload.
3Preview the result at full size before you commit to it.
4Export back to WebP, or to a lossless format instead if you are still part-way through editing.
WebP Editor FAQ
Does the file format limit what the editor can do?
+
It does. WebP carries both a lossy VP8 mode and a lossless mode plus full alpha, typically landing 25-35% under a JPG of matching visual quality. What the format can represent bounds what any editor can preserve, here or on the desktop.
Anything specific to WebP in the editor?
+
Yes — the same .webp extension can hold a lossy VP8 frame, a lossless one, or an animation, so the sensible processing path is decided per file rather than per extension. Worth knowing before you export over your only copy.
Is anything lost when I export?
+
Only what the export format cannot represent. Choose a lossless output while you are still iterating and a compressed one when you are finished — exporting to a lossy format between edit sessions is what accumulates damage.
How does WebP Editor let me edit without installing anything?
+
Concretely, the JPEG is decoded once into an RGB canvas, every change you make lands on that canvas rather than on the file, and the quantiser runs exactly once when you export — which is why editing here does not compound generation loss the way ten edit-and-resave cycles in a desktop app do. The editing surface is the browser, so there is nothing to install and no licence to hold.
Can I run WebP Editor on several WebP images at once?
+
Yes. Drop the whole set into the upload area and they queue in parallel with identical settings — that is the main reason to do this in a browser rather than one file at a time in an editor. Free accounts run one file per batch; a pass lifts that.
What happens to EXIF and colour profile data?
+
Camera EXIF (ISO, shutter, lens, GPS) and the embedded ICC profile are carried across by default, because dropping the profile is what makes colours shift on re-import. Use the privacy option to strip metadata before download if you are about to publish the file.
Is there a file size limit on WebP Editor?
+
Yes: free accounts process images up to 5 MB each, which covers essentially every camera JPG and phone photo; the work is done by libjpeg-turbo and libwebp, the same libraries a desktop editor links against. Larger files are the one thing the free tier will stop you on, and the limit is per file rather than per batch.
Will WebP Editor lower the quality of my WebP images?
+
A lossy source is already the result of one quantisation pass, and any operation that has to re-encode adds a second. Where the job can be done without touching the pixel data we do that instead, and where it cannot you choose the quality factor yourself rather than getting a fixed default.
Why does a Word site host WebP Editor?
+
WORD.to is built around the editable end of a document's life — the DOCX that is still being written, still being styled and still being argued over, before anyone flattens it for sending. Office files are containers full of other people's media — images, embedded audio, fonts — so the work people need on them is usually the work they would need on those contents anyway. WebP Editor shares the upload, the caps and the account with the conversions for that reason.
What should I do with the result once WebP Editor is finished?
+
The converter on this site takes documents out to PDF for sending, to images for embedding and to plain text for anything that has to read them programmatically, and back the other way. Doing that afterwards keeps the editable original around, which is the part you cannot get back once it has been flattened.
Is WebP Editor here the same tool the sibling sites run?
+
The engines are shared — the same document toolchain, the same workers, the same limits. What a Word site adds is a view on what survives leaving the Office format and what does not, which is the question every one of these jobs actually turns on. It also starts from one fact about the format this site is named after: the document is a zip of XML, so text edits are cheap and the weight is almost always the embedded images.
Do I need an account, and does anything get kept?
+
No account, and nothing is kept: uploads are deleted from the workers shortly after the job finishes, nothing is read and nothing is indexed. Free accounts exist for history and batch size, not for access.
