Image Compressor

Compress images to a smaller size using quality presets, target size, or a specific file size—while keeping results compatible with your chosen format.

Initializing... drag & drop files here

Supports: 3FR, ARW, AVIF, BMP, CR2, CR3 +30 more

OptionsAdvanced Options - Our defaults are optimized for the best results. We recommend you keeping the defaults unless you have a specific need.
Image File Extension
Selecting a specific extension ensures all advanced options are compatible with your output. If 'Same as source' is used, settings that don't apply to your original file format will be automatically ignored during processing.
Image Compression
File size (%)
1
80
100
If your file is 10 MB, then selecting 80 will produce a 8 MB file. If you make the output file size too small, then output video quality may suffer.
Auto Scale
[Smart Scaling Active] We will automatically adjust the image dimensions to maximize quality while hitting your target file size. Manual resolution settings are hidden to prevent pixelation.

How to Compress Images Online

  1. Upload Your Images: Drag and drop or click "Add Files" to add JPG, PNG, WebP, HEIC, AVIF, GIF, BMP, TIFF, ICO, PPM, EPS, and RAW camera files (CR2, NEF, DNG, ARW, ORF, RAF, RW2). Batch is supported — drop dozens at once.
  2. Choose the Image File Extension: Leave it on "Same as source" to compress in place, or switch to JPG, WebP, AVIF, PNG, or HEIC to combine compression with format conversion. WebP and AVIF typically shave another 25-50% off a JPEG-quality baseline.
  3. Set the Image Compression Mode (Optional): Pick "Target file size (%)" to shrink by a ratio (e.g. 50% of original), "Specific file size" to hit an exact KB/MB target like 1 MB for Gmail, or "Image Quality (%)" to dial quality directly (75-85 is the web sweet spot). Auto Scale is on by default and quietly downsizes dimensions when needed so the target size stays sharp instead of muddy.
  4. Compress and Download: Click "Compress" and grab the files individually or as a ZIP. Everything runs on our servers — no sign-up, no watermark, no email gate.

Why Compress Images?

Unoptimized images are the single biggest reason web pages feel slow. Google's Lighthouse "Improve image delivery" audit (formerly "Serve images in modern formats") flags any image where modern compression would save 8 KiB or more, and those savings directly affect Largest Contentful Paint — one of the Core Web Vitals that influences search ranking. Compressing also makes uploads, emails, and chat shares finish in seconds instead of minutes.

  • Speed up websites and pass Core Web Vitals — Google's web.dev measurements show WebP delivers 25-35% smaller files than JPEG and roughly 80% smaller than PNG at equivalent quality, which is why Facebook and YouTube adopted it for thumbnails.
  • Fit email and chat caps without blur — Gmail allows 25 MB per message but starts auto-uploading to Drive past that threshold, and WhatsApp may compress photos above a certain size threshold (historically around 16 MB) down to ~1600 px at quality 75 — check WhatsApp's current limits as these change. Compressing first keeps the result you choose, not the result the platform forces.
  • Save phone and cloud storage — A 12 MP iPhone shot in HEIC is roughly 2-3 MB; the same scene as a maximum-quality JPEG can run 5-8 MB. Compressing camera roll exports before they hit Drive, iCloud, or Dropbox frees real gigabytes.
  • Slim Shopify, WordPress, and Etsy listings — Stores often cap product images at 5-20 MB but penalize slow pages. Dropping JPEGs to 200-500 KB at quality 80 hits both bars without visible loss.
  • Cut hosting bandwidth and CDN egress — If a marketing page ships 20 hero/product images at 4 MB each, recompressing to 400 KB saves 72 MB per visitor.
  • Send photo batches over flaky mobile data — Travelers, real-estate agents, and field crews can push a 50-photo upload over LTE in a fraction of the time.

Compression Ratios by Source Format

Source format Typical reduction Lossless option Best target format
JPG / JPEG 30-70% No (already lossy) JPG or WebP
PNG (photo) 60-85% Yes (PNG optimize) WebP or JPG
PNG (logo / UI) 40-70% Yes PNG or WebP
HEIC / HEIF 20-40% No HEIC or WebP
WebP 10-30% Yes (lossless WebP) WebP
TIFF 70-95% Yes (LZW / Deflate) JPG or WebP
BMP 80-95% No (BMP is uncompressed) JPG, PNG, or WebP
RAW (CR2, NEF, DNG, ARW) 85-98% No JPG or WebP
GIF 20-50% Yes (palette / dither) WebP or GIF

Ratios depend on the image — busy photos compress less than flat graphics, and a noisy night shot resists JPEG quantization more than a clean studio portrait.

JPG vs PNG vs WebP vs AVIF — Which to Pick for the Web

Property JPG PNG WebP AVIF
Best for Photos, social uploads Logos, screenshots, UI Photos and graphics on the web Hero photos where size matters most
Compression vs JPG baseline ~30% larger 25-35% smaller 40-50% smaller
Transparency (alpha) No Yes Yes Yes
Animation No APNG only Yes Yes
Lossless mode No Yes Yes Yes
Browser support Universal Universal Chrome, Firefox, Edge, Safari 14+ Chrome 85+, Firefox 93+, Safari 16.4+, Edge 121+ (~94% global)
Encode/decode speed Very fast Fast Fast Slower to encode
When to default to it Camera photos, email attachments Anything with sharp edges or transparency Web pages, ecommerce, blog images Top-of-page hero images served via <picture> with WebP fallback

Quality Preset Cheat Sheet

Image Quality (%) Visual result Typical use
95-100 Indistinguishable from original Print masters, archival, design handoffs
85-94 Very close — fine detail intact Photography portfolios, ecommerce hero shots
75-84 Web sweet spot — invisible artifacts at normal viewing distance Blog images, product galleries, social posts
60-74 Light banding on gradients, slight softness Thumbnails, list views, lazy-loaded grids
40-59 Visible blockiness in flat areas Preview-only, low-bandwidth fallbacks
Below 40 Heavy artifacts, posterized skies Avoid for anything customer-facing

Pair the quality slider with Auto Scale on so the encoder isn't forced to choke a 6000 px source down to 100 KB — dropping to 1600-2000 px first preserves perceived sharpness.

Frequently Asked Questions

Which is better for the web — WebP, AVIF, or sticking with JPG?

For most pages, WebP is the safest default in 2026: Google's own data shows 25-35% smaller files than JPG at the same quality, and it's supported by every modern browser including Safari 16+ (with partial support since Safari 14). AVIF compresses tighter again (40-50% smaller than JPG) but is slower to encode and lands at ~94% global support, so it's best served via a <picture> element with a WebP fallback. JPG is still fine when you need maximum compatibility with old email clients or legacy CMS plugins.

How much can I shrink a JPEG without it looking worse?

For a photo at quality 95, you can usually drop to quality 80 with zero visible difference on a normal screen, which typically saves 40-60% of the file size. Quality 75 is the long-standing web standard (it's what WhatsApp uses for chat photos) — below 70 you start seeing soft edges and block patterns in skies and gradients. If you also enable Auto Scale to downsize the dimensions, a 5 MB JPEG often becomes a 300-500 KB file that looks identical at typical viewing sizes.

Can I compress a PNG without losing quality at all?

Yes. Pick PNG as the output format and keep "Image Quality" at 100, or switch to lossless WebP — both rewrite the file using better entropy coding and palette optimization rather than discarding pixels. Lossless reductions of 20-40% are typical for screenshots and UI graphics, and Google measured 80% size cuts for some PNG-to-WebP lossless conversions. If your PNG is actually a photo, converting to lossy JPG or WebP at quality 85 will shrink it far more (often 60-85%).

Why does my compressed image still look pixelated?

Usually because the encoder was given an impossible target — for example, asking for 50 KB from a 24-megapixel photo. The fix is to leave Auto Scale on so the dimensions drop first (say, from 6000 px to 1920 px wide), then quality is applied to the smaller version. You can also try the same target size in WebP instead of JPG — WebP holds detail better at low bitrates.

What's the best size for email and WhatsApp?

Gmail allows up to 25 MB per message before it auto-uploads attachments to Drive; Outlook caps at 20 MB. For inline previews and chat use, aim for 1-2 MB per image at 1600-2000 px wide. WhatsApp automatically recompresses photos above a certain size threshold (historically around 16 MB) and resizes chat photos to 1600 px at quality 75, so pre-compressing to 1280-1600 px at quality 80 means your quality choice is what arrives rather than WhatsApp's.

Can I batch compress hundreds of images with the same settings?

Yes — upload as many files as you want in one session and the same Image Compression and Image Quality settings apply to every file. Downloads come either as individual files or one ZIP. Photographers cleaning up a shoot and ecommerce teams updating a catalog typically batch in groups of 50-200 at a time.

JPEG and HEIC compression typically discards EXIF, GPS, and color profile metadata to maximize size savings — useful for privacy when sharing publicly, but watch out if you rely on EXIF for cataloging. If you need metadata preserved, choose lossless PNG or lossless WebP as the output, which leaves ancillary chunks intact.

Is there a file size limit per upload?

Free users can compress images up to 300 MB each, with no cap on how many files you process per session. That's roughly 6x what TinyPNG's free tier allows (5 MB per image, 20 images per batch) and covers RAW camera files, multi-layer TIFFs, and HEIC bursts straight off a phone.

Are my uploads private?

Yes. Uploads use TLS in transit and files are deleted from our servers shortly after processing. We don't store, share, or look at your images, and no account is required — useful when compressing IDs, contracts, or product shots under embargo.

Rate Image Compressor Tool

Rating: 4.7 / 5 - 38248 reviews