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 WebP file, and keep your original: it is the only undo you have.
WebP Filters FAQ
How does WebP Filters apply an effect?
+
Concretely, the filter is a per-pixel transform applied to the decoded image, so the file is necessarily re-encoded once — apply every filter you want in a single pass rather than stacking runs. 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 the source format change how a filter looks?
+
It can. 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. Colour depth and the palette model in particular decide how smoothly a gradient or a blur can be represented.
Anything specific to WebP to keep in mind?
+
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. That is often the difference between an effect looking clean and looking banded.
Can I undo a filter after downloading?
+
No — the effect is baked into the output pixels, which is the point of applying it. Keep the original file; that is your undo. Grayscale and blur in particular discard information that genuinely cannot be recovered.
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.
What can I upload to WebP Filters?
+
Anything in the lossy raster family — JPG, JPEG, JFIF and WebP — plus the lossless formats (PNG, BMP, TIFF) if you want to mix them in one batch. The format is read from the file header, not the extension, so a photo saved with the wrong suffix still goes through.
Is there a file size limit on WebP Filters?
+
Yes: free accounts process images up to 25 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 Filters 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.
Can I run WebP Filters 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.
Does WebP Filters cost anything?
+
No. WebP Filters 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.
