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
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.
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.
How does Image Editor let me edit without installing anything?
+
Concretely, whatever you upload is decoded into one editable canvas, every change is composited on a working copy, and the format decision is deferred to the moment you export. The editing surface is the browser, so there is nothing to install and no licence to hold.
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 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.
Which image formats does Image Editor accept?
+
All of the common ones — JPG, JPEG, PNG, WebP, GIF, BMP, TIFF, SVG, ICO, PSD, JFIF and HEIC. You can mix formats freely in one batch; each file is identified from its header and routed to the right decoder.
Is there a file size limit on Image Editor?
+
Yes: free accounts process images up to 25 MB each regardless of which image format you brought; ImageMagick, libjpeg-turbo, libpng and libwebp do the actual work. The cap is per file, so a batch of twenty 5 MB photos is fine even though the total is well over the limit.
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.
Why does a MP3 site host Image Editor?
+
MP3.to is built around the format that made portable audio ordinary: universally playable, small enough to ignore, and lossy in a way that only matters if you keep re-encoding it. Audio jobs cluster: the same person who needs a format changed usually needs the file cut, levelled or made smaller in the same sitting. Putting Image Editor behind the same upload, the same caps and the same account is what turns three tabs into one.
What should I do with the result once Image Editor is finished?
+
The converter on this site moves audio between MP3, WAV, FLAC, M4A, OGG and Opus, so the output format is a decision you can leave until the end rather than commit to at the start. Doing that after Image Editor rather than before means the encode happens once, on the file you actually settled on, instead of twice.
Is Image Editor here the same tool the sibling sites run?
+
The engines are shared — the same ffmpeg build, the same workers, the same limits. What a MP3 site adds is a point of view about bitrates, about what survives an encode and about when a lossless intermediate is worth the upload time. It also starts from one fact about the format this site is named after: MP3 frames are fixed-size blocks, so a cut lands on a frame boundary and gapless playback markers do not survive a re-encode.
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 listened to and nothing is indexed. Free accounts exist for history and batch size, not for access.
