1Upload the 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 Image, or to a lossless format instead if you are still part-way through editing.
Image Editor FAQ
Is my file uploaded, or does editing happen locally?
+
Editing happens in your browser; the file goes to our workers only for the operations that genuinely need server-side processing, and it is deleted shortly afterwards.
What can I actually change?
+
Crop, rotate, flip, resize, draw, add text and shapes, and apply filters and colour adjustments. Everything is applied to a working copy, so the file you uploaded is never modified in place.
Does the file format limit what the editor can do?
+
It does. this format is read and written by the same streaming pipeline as everything else we support. What the format can represent bounds what any editor can preserve, here or on the desktop.
Anything specific to Image in the editor?
+
Yes — the pipeline reads the real format from the file header rather than the extension, so a mislabelled upload still works. Worth knowing before you export over your only copy.
Will Image Editor lower the quality of my images?
+
That depends on what you brought. A lossless source (PNG, BMP, TIFF) round-trips exactly; a lossy one (JPG, WebP, GIF) is already the product of one quantisation pass and only re-encodes if the operation genuinely requires it.
Can I run Image Editor on several images at once?
+
Yes, and mixing formats in the batch is fine — settings are applied per file with the right decoder for each. Free accounts run one file at a time; a pass removes that.
What happens to metadata and transparency?
+
EXIF and the ICC colour profile are carried across wherever the target format supports them, and an alpha channel survives into any format that has one. Transparency is only flattened when the destination format has no way to represent it.
Does Image Editor cost anything?
+
No. Image Editor is free without an account and adds no watermark. Uploads are deleted from the workers shortly after the job completes.
Why does a WebM site host Image Editor?
+
WEBM.to is built around the container the open web actually chose — VP9 or AV1 with Opus audio, decoded natively by every modern browser and needing no plugin, licence or player. Video is the case where extra round trips hurt most — the files are large and every upload costs real minutes. Running Image Editor on the same pipeline as the conversions means one upload covers the whole job instead of one upload per tool.
What should I do with the result once Image Editor is finished?
+
The converter on this site moves video between WebM, MP4, MKV, MOV and the rest, or pulls the soundtrack out entirely, without another upload. Sequencing it that way matters more for video than anywhere else: each re-encode is another generation, so the fewer of them stand between the source and the file you publish, the better it looks.
Is Image Editor here the same tool the sibling sites run?
+
The engines are shared — the same ffmpeg build with x264, x265 and libvpx, the same workers, the same limits. What a WebM site adds is a view on containers and codecs: which combinations play everywhere, which need a re-encode and which can simply be copied across. It also starts from one fact about the format this site is named after: WebM is VP9 or AV1 with Opus audio, which browsers decode natively but which most desktop editors still transcode on import.
Do I need an account, and does anything get kept?
+
No account, and nothing is kept: uploaded video is deleted from the workers shortly after the job finishes, nothing is watched and nothing is indexed. Free accounts exist for history and batch size, not for access.
