Guide
Image workflow: resize, compress or convert — which should come first?
Resize, conversion and compression solve different image problems. Use the right order to avoid unnecessary re-encoding and quality loss.
“Make this image smaller” can mean at least three different things: reduce its pixel dimensions, reduce its file size, or change its file format. Those are separate operations, and the order matters.
What each operation changes
| Operation | Changes | Typical reason |
|---|---|---|
| Resize | Pixel width and height | The source is larger than the page or destination requires. |
| Convert | File format | You need WebP, JPEG or PNG for compatibility, transparency or workflow reasons. |
| Compress | Encoding/file weight | The final file is still heavier than necessary. |
A strong default order for web images
- Use Image Resizer if the original dimensions are excessive.
- Use Image Converter if the destination format needs to change.
- Use Image Compressor on the final format and inspect the visual result.
This order avoids spending bandwidth on pixels the user will never see and reduces the chance of repeatedly re-encoding a lossy file.
Important exceptions
- Do not convert a transparent logo to JPEG if transparency is required.
- Do not upscale a small source and expect new detail to appear.
- Do not assume one quality percentage is ideal for photographs, screenshots and graphics with text.
Use a workflow instead of memorising URLs
The Image Workflow exists to connect related utilities around the user task. That is a core Tools Brave product idea: tools should form a usable sequence rather than a directory of isolated buttons.