Image compressor online

How to compress an image

1. Choose a JPG, PNG, or WebP image from your device.
2. Start with the default quality and max-width settings.
3. Compress the image and check the downloaded file size.
4. If the result is still too large, reduce max width or lower quality gradually.
5. Open the downloaded image once to confirm it is clear enough for your use.

For forms and portals, compare the final file with the official size, dimension, format, and readability rules before submitting.

What image compression is and how it works

Image compression reduces the number of bytes needed to store a picture. This tool uses lossy JPG encoding through your browser's canvas API: it redraws your selected image onto an in-memory canvas at the width you choose, then re-encodes that canvas as a JPG at the quality percentage you set. Lower quality tells the JPG encoder to group similar colors together and discard some of the fine color detail the human eye is least sensitive to, which shrinks the file. Reducing the width shrinks the file for a different reason: fewer pixels means fewer values to store in the first place, independent of quality.

The two controls interact. A very detailed 4000-pixel-wide photo at quality 90 can be larger than a 1200-pixel-wide version of the same photo at quality 90, because the second version simply has less pixel data to encode. This is why the guide below adjusts width before quality for large photos rather than dropping quality alone.

When to use the image compressor

Use this general compressor when you need a smaller image for email, a website, a profile upload, a document portal, or a form that gives a file-size limit but not a specific target page. It is a flexible starting point when you want to control both quality and maximum width directly, rather than following a fixed KB target.

Best practices for compressing images

• Start with width, not quality. If a phone photo is 3000px or wider, bring it down to 1200-1600px before touching quality. This alone often cuts file size by 60-80% with almost no visible loss.
• Lower quality in small steps. Move from 75% to 65% to 55% rather than jumping straight to 30%, and check the result each time so you can stop as soon as the file is small enough.
• Keep your original file. Compression is one-way. Always compress a copy and keep the source image in case you need a higher-quality version later.
• Check faces, text, and edges after compressing. These are where quality loss shows up first, especially in signatures, ID documents, and screenshots with small text.
• Match the target to the actual rule. If a portal states an exact KB limit, use a target page such as compress image to 50KB instead of guessing with the general compressor.

Common mistakes to avoid

• Dropping quality to the minimum first. This produces visible blotches and blurred text long before it's necessary. Reduce width first for large photos.
• Compressing a screenshot the same way as a photo. Screenshots and scanned documents have sharp edges and text; they often need higher quality settings than photos to stay readable at a similar file size.
• Ignoring the destination's dimension rules. A file can be small enough in KB but still fail a form that also requires specific pixel dimensions. Check both.
• Re-compressing an already-compressed JPG repeatedly. Each JPG re-encode loses a little more detail. Compress from the original source file whenever possible, not from a previously compressed copy.
• Assuming PNG will always look better. PNG is lossless but often produces a larger file than a well-compressed JPG for ordinary photos, which can work against a strict size limit.

Real-world use cases

• Email attachments: Many email providers slow down or reject attachments over a few megabytes; compressing a batch of photos before sending avoids bounced messages.
• Website and blog images: Large uncompressed photos are one of the most common causes of slow-loading web pages, which affects both visitors and search ranking.
• Job and school application portals: Many application systems cap photo or document uploads at 100KB-500KB and reject anything larger without a clear error message.
• Marketplace and classifieds listings: Faster-loading listing photos reduce abandonment on slow mobile connections.
• Government and account verification forms: ID and proof-of-address photos often need to fit a strict size limit while staying legible for manual review.

Supported formats and output

The compressor accepts JPG, PNG, and WebP as input, provided your browser can decode the file. Regardless of the input format, the compressed output is currently prepared as JPG, because JPG's lossy encoding produces smaller files for photographic content than PNG re-encoding does. If your destination specifically requires a PNG or WebP output file, use the image converter after compressing, or resize first with the image resizer if the file needs to shrink through dimensions rather than format.

Quality and readability tradeoffs

Lower quality usually reduces file size, but it can soften faces, document text, signatures, and small details. Reducing width first often gives a cleaner result for very large phone photos because the image has fewer pixels to store before quality is lowered.

For text-heavy screenshots or forms, check readability after compression. If the upload portal allows a larger file, use the least aggressive settings that meet the rule.

Worked example: compressing a 12MP phone photo for a 100KB form limit

Here is a typical sequence for a 4000x3000px, 4.8MB JPG straight from a phone camera, targeting a portal that requires the file to be under 100KB. Actual results vary by image content, so treat the numbers below as a realistic example rather than a guarantee.

Notice that step 1 alone removed most of the file size, and the last two steps made smaller, more careful adjustments to land under the 100KB target without over-compressing. This step-by-step approach usually preserves more visible quality than jumping straight to a low quality percentage on the full-size original.

Limitations of browser-based compression

This tool cannot promise a precise output size, because the final file size depends on the original image's resolution, level of visual detail, color range, and the browser's JPG encoder. Two images of the same pixel dimensions can compress to very different sizes if one has a busy, detailed background and the other has large flat-color areas. Extremely large source files (very high megapixel counts, or images many tens of megabytes in size) may take longer to process or may need more aggressive width reduction than a typical photo. The tool also cannot verify a specific portal's official rules; it only helps you produce a smaller file that you should compare against the destination's stated requirements.

Privacy: how your images are processed

Image compression runs using your browser's own canvas and file APIs. The selected file is read and redrawn locally by the page's JavaScript, and the compressed result is generated as a downloadable file in the same browser session. Keep the tab open until your download finishes. Analytics on this page record only non-identifying signals such as file-size buckets and processing outcomes, not file names, file content, or the image itself — see the privacy policy for full detail.

Troubleshooting compression results

• If the file is still too large, reduce max width before dropping quality too far.
• If the image looks blurry, try a higher quality setting or a larger size limit.
• If the portal asks for an exact limit, use a target page such as compress image to 50KB or compress image under 100KB.
• If dimensions matter, resize first with the image resizer.

Conclusion

The image compressor is the right starting point whenever you need a smaller file and want direct control over quality and width instead of following one fixed KB target. Reduce width first for large photos, lower quality gradually, and always check the result against the destination's real requirements before submitting it. If you already know the exact KB limit, jump straight to a target page like compress image to 20KB or compress image under 200KB for guidance tuned to that specific number.