2Pick your effects — grayscale, sepia, invert, blur, sharpen, brightness, contrast and saturation — and set the strength of each.
3Apply them all in a single pass rather than running the tool repeatedly, which is what accumulates visible damage.
4Download the filtered Image file, and keep your original: it is the only undo you have.
Image Filters FAQ
Anything specific to Image to keep in mind?
+
Yes — the pipeline reads the real format from the file header rather than the extension, so a mislabelled upload still works. That is often the difference between an effect looking clean and looking banded.
Can I apply the same look to a whole set?
+
Yes. One filter configuration is applied across the batch, which is how you get a visually consistent gallery rather than a set of individually-tweaked images that almost match.
How does Image Filters apply an effect?
+
Concretely, the filter is applied per file with the right decoder for each format, so a mixed batch comes out with one consistent look. You pick the effect and its strength and the transform is applied to the whole file at once.
Which effects are available?
+
Grayscale, sepia, invert, blur, sharpen, and brightness, contrast and saturation adjustment. They can be combined, and combining them in one pass is better than running the tool repeatedly.
Does Image Filters cost anything?
+
No. Image Filters 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 Filters 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 Filters?
+
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 Filters?
+
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 Filters 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 Filters 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 Filters rather than before means the encode happens once, on the file you actually settled on, instead of twice.
Is Image Filters 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.
