1Upload the JPEG images you want to work on; the file opens in an editable view in your browser with nothing installed.
2Make your changes — crop, rotate, resize, draw and recolour on an image; rewrite the words and restyle headings, lists and tables in a document — and every one of them lands on a working copy, never on your upload.
3Preview the result at full size before you commit to it.
4Export back to JPEG, or to a format that re-compresses nothing if you are still part-way through editing.
JPEG 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?
+
Whatever the format itself can carry. On an image that is crop, rotate, flip, resize, drawing, text and shapes, filters and colour; in a document it is the wording, the headings, the lists and the tables. 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. JPEG is the same codec as JPG under a longer extension — identical DCT pipeline, identical quantisation tables, nothing about the pixels changes with the filename. What the format can represent bounds what any editor can preserve, here or on the desktop.
Anything specific to JPEG in the editor?
+
Yes — the .jpeg and .jpg extensions are the same bitstream, so nothing here behaves differently from a .jpg — only the filename changes. Worth knowing before you export over your only copy.
Will JPEG Editor lower the quality of my JPEG 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.
Can I run JPEG Editor on several JPEG 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.
Does JPEG Editor cost anything?
+
No. JPEG Editor is free with no account, no watermark on the output and no signup wall in front of the download. Uploads are deleted automatically a short time after the job finishes.
Why does a WebM site host JPEG 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 JPEG 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 JPEG 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 JPEG 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.
