Image tools workflow: compress, convert, clean and publish
Preparing images for the web is not one button. The best result usually comes from a short workflow: choose the right dimensions, pick the right format, compress carefully, remove private metadata when needed, and check whether the final image still looks right in context.
Start with the final use
A blog hero, product thumbnail, social preview and invoice attachment do not need the same image. Before changing anything, decide where the image will be used. Full-width website images often need more pixels than a product grid thumbnail. A screenshot with small text needs sharper edges than a lifestyle photo. A transparent logo needs a format that keeps transparency.
This first decision prevents the most common mistake: compressing a huge original file without resizing it. A 6000 pixel camera photo can remain too large even after quality compression. Resize first, then compress.
Image workflow checklist
| Step | Goal | Tool fit |
|---|---|---|
| Resize | Match the display size instead of shipping camera-size files. | ImageBloom |
| Convert | Use JPG for photos, PNG for transparency, WebP/AVIF for smaller modern web files. | Format guide |
| Compress | Reduce file size while checking the visible result. | ImageBloom |
| Clean metadata | Remove GPS, camera and hidden comments before public sharing. | MetaBloom |
| Check color | Pull palette ideas or verify contrast for text overlays. | ColorBloom |
Which format should you choose?
Use JPG when the image is a regular photo and broad compatibility matters. Use PNG when the image needs transparency, crisp UI edges or lossless screenshots. Use WebP when you want a strong default for modern websites: it supports transparency and often produces smaller files than JPG or PNG. Use AVIF when very small files matter and you have checked that your target browsers or platform support it.
A useful rule is to keep the original file somewhere safe, then export web-ready copies. Do not overwrite your only high-quality source.
Scenarios
Blog post image: resize to the maximum content width, export WebP or JPG, compare the result at the size it will actually appear, then remove metadata if the photo was taken on a phone.
Product image: keep dimensions consistent across the catalog, use a predictable background, compress carefully so edges and labels stay readable, and save naming conventions before upload.
Screenshot: avoid aggressive JPG compression. PNG or WebP usually keeps text and UI lines cleaner.
Privacy and quality tradeoffs
Smaller is not always better. Over-compression can create blurry labels, rough gradients and noisy edges. For public images, the goal is the smallest file that still communicates clearly. For private images, the goal also includes removing metadata that the viewer does not need.