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
Does the source format change how a filter looks?
+
It can. this format is read and written by the same streaming pipeline as everything else we support. Colour depth and the palette model in particular decide how smoothly a gradient or a blur can be represented.
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 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.
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.
Can I run Image Filters 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.
Is there a file size limit on Image Filters?
+
Yes: free accounts process images up to 5 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.
Will Image Filters 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.
Why does a Word site host Image Filters?
+
WORD.to is built around the editable end of a document's life — the DOCX that is still being written, still being styled and still being argued over, before anyone flattens it for sending. Office files are containers full of other people's media — images, embedded audio, fonts — so the work people need on them is usually the work they would need on those contents anyway. Image Filters shares the upload, the caps and the account with the conversions for that reason.
What should I do with the result once Image Filters is finished?
+
The converter on this site takes documents out to PDF for sending, to images for embedding and to plain text for anything that has to read them programmatically, and back the other way. Doing that afterwards keeps the editable original around, which is the part you cannot get back once it has been flattened.
Is Image Filters here the same tool the sibling sites run?
+
The engines are shared — the same document toolchain, the same workers, the same limits. What a Word site adds is a view on what survives leaving the Office format and what does not, which is the question every one of these jobs actually turns on. It also starts from one fact about the format this site is named after: the document is a zip of XML, so text edits are cheap and the weight is almost always the embedded images.
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 read and nothing is indexed. Free accounts exist for history and batch size, not for access.
