When this workflow helps
Image compression is useful for product listings, website pages, email attachments, forms and social content. It works best when you know the display size and the minimum acceptable quality before adjusting the output.
A step-by-step workflow
A guide to reducing JPG, PNG and WebP image file sizes using a preview-led workflow while preserving details important to the final use. Use the following sequence as a checklist; exact controls and supported formats are shown in the live tool.
Set a practical target
Start with the target’s pixel dimensions or upload limit. A 4000-pixel photo used as a 500-pixel thumbnail usually does not need to retain all of its original dimensions.
Select a suitable output format
JPG can be effective for photographic content, PNG is often valuable for sharp graphics or transparency, and WebP may offer an efficient alternative. Check whether the destination accepts the chosen format.
Compare preview and file size
Use the live preview to inspect textures, text, edges and gradients. A modest file-size reduction with clean detail may be a better result than an aggressive reduction with obvious artifacts.
Save and test the output
Reopen the compressed file, confirm the file size and dimensions, and inspect the image at its real display size. If it is a website asset, test it in the actual layout before replacing the original.
Settings, quality and privacy checks
Transparent PNG assets can behave differently from photographs when compressed or converted. Fine lettering and logos reveal artifacts quickly, so avoid evaluating only smooth photographic areas. Retain an original file if the asset may be edited later.
Before using any browser tool with confidential material, check what the specific studio says about local processing, model downloads, external services and supported formats. Do not assume that every app has the same storage or network behaviour simply because it is linked from RuntimeHub.
Common mistakes to avoid
- Compressing a large source without first choosing a suitable display size.
- Ignoring artifacts around text, sharp edges and transparent borders.
- Replacing the original before checking whether the compressed file looks acceptable in context.
A useful final habit is to keep the original input until you have opened the output and confirmed that it fits the intended destination. When the result will be submitted, published or used as evidence, inspect it in the actual application that will receive it.
Frequently asked questions
Should I use JPG or PNG for a logo?
The answer depends on whether transparency and crisp edges are required. PNG is commonly useful for transparent graphics; JPG does not preserve alpha transparency.
How small should an image be?
Follow the destination’s limits and display needs. There is no single ideal file size for all images; inspect the result at its intended dimensions.
Put the workflow into practice
Use Squeezy to work through the ideas in this guide. Keep the source available, make the changes you need, and check the result before saving or sharing it.
- Start with the file or information you want to work on.
- Use the available controls to shape the result.
- Preview the output before saving or sharing it.