Compress an image with SizeFix
What actually makes an image file smaller?
Image file size is mainly affected by pixel dimensions, format, image complexity and compression level. A large camera photo contains far more pixels than most websites need. Reducing unnecessary dimensions can therefore save substantial space before aggressive quality reduction is required.
Which format should you use?
For photographs, JPG is widely compatible and usually compresses efficiently. WebP can often produce smaller web images at similar visual quality when the destination accepts it. PNG is useful for screenshots, graphics and transparency, but photographic PNG files can be much larger.
What should you change first?
If a portal gives an exact maximum such as 100KB or 200KB, start with that requirement. Do not resize randomly. If the dimensions are already reasonable, reduce encoding quality gradually. If the source is a very large camera image, reducing dimensions first can preserve more visible quality than forcing an extremely low JPG quality setting.
How do you know when compression has gone too far?
Inspect the parts that matter: faces, small text, signatures, logos, document numbers and sharp edges. Blockiness, smeared detail or unreadable text means the compression is too aggressive. Return to the original rather than repeatedly compressing an already degraded copy.
Can an image always be compressed to any target?
No. Some combinations of exact dimensions, format and tiny file-size limits cannot be achieved without noticeable quality loss. A trustworthy converter should report the actual result rather than claim that every target is possible.
Common upload targets
SizeFix provides direct workflows for 50KB, 100KB, 200KB, 500KB and 1MB. Use the target specified by the destination site rather than choosing one arbitrarily.