Image Compressor — Compress JPG, PNG & WebP Images
Part of Image tools: See all Image tools.
What is Image Compressor?
This free Image Compressor shrinks JPEG, PNG, and WebP files so they fit email caps, load faster on product pages, and upload cleanly to forms that reject oversized photos. You upload over HTTPS; the server encodes the image for that request and discards the original when the download is ready. There is no account, no watermark, and no permanent archive of your file. Use the quality slider and optional max dimension together: quality controls encoding aggressiveness, while max size in pixels stops a 6000px phone photo from staying huge even at a high quality setting.
How to use Image Compressor
- Open the Image Compressor and drop in a JPEG, PNG, or WebP image, or switch Mode to Bulk to pick several images.
- Set Quality (try 80–85 first for web/email). Lower numbers shrink more; raise toward 90–95 only if you will print or pixel-peep at 100% zoom.
- Optionally set a maximum dimension (for example 1920px). This resizes the long edge before encoding — often the biggest win for DSLR and phone originals.
- Click Compress & Download, check the size of the downloaded file, and open it at 100% zoom. If it is still over your limit, lower quality by 5–10 points or reduce the max size, and run it again.
Why use this tool?
Oversized images are the most common reason a form upload fails, a Gmail draft will not send, or a Shopify category page crawls on mobile. Compressing after you already have the final crop keeps the master file untouched while producing a publishable copy. This tool is built for that last mile: an honest server-side encode, immediate discard, and two settings that are easy to reason about. Pair it with Resize when you need exact social dimensions, or Background Remover when the subject needs a transparent PNG before you compress.
Quality is a dial: Use the quality slider like a trade-off between size and clarity. For most website graphics and logos, 70-85% often looks sharp while still shrinking the file a lot.
After downloading, quickly re-check the output - if it's for email or forms with strict limits, compress again with a slightly lower quality.
Image Compressor — In-Depth Guide
A typical run: a phone photo of roughly 8–12 MB, quality around 82 and max size 1920 px. Compress, then open the download next to the original at 100% zoom on a detailed area such as hair, fabric, or text on a sign. If the first pass is still above your limit, lower quality to about 75 and run again. Keep the original as your master copy.
Realistic size examples (order-of-magnitude, not a guarantee — results depend on content): a 12 MP phone JPEG at ~10 MB often lands near 1–2 MB at quality 80 with a 1920px cap; a 24 MP JPEG at ~18 MB often lands near 1.5–3 MB with the same settings; a PNG screenshot of a UI may only drop 10–30% as JPEG-style lossy encode is the wrong tool — keep PNG or convert thoughtfully. A logo with flat colors should stay PNG or lossless WebP; forcing JPEG introduces fringe around text. Use these as starting hypotheses, then verify on your file.
Email and upload limits in practice: Gmail and Yahoo commonly allow ~25 MB for the whole message (all attachments plus body). Outlook.com is often cited around 20 MB. Many government and university portals accept 2–10 MB per file. If you must send five photos, compress each toward 500 KB–1.5 MB rather than attaching five 8 MB originals. For a single PDF-heavy email, prefer the PDF Compress tool; for photo-only threads, this Image Compressor is the right first stop.
Quality ladder for decisions under time pressure: 95 = almost archival copy for screen, rarely worth the bytes; 90 = print-ish / client review; 85 = default web hero; 80 = balanced product grid; 75 = mobile-heavy pages and stubborn email caps; 70 = thumbnails and previews; below 65 expect visible mush on faces and gradients. Move in steps of five, and stop when the file clears your limit and still looks acceptable at the size it will actually be displayed — not at a zoomed crop your audience will never see.
Troubleshooting checklist: (1) Still too big → lower max dimension before lowering quality. (2) Blurry colored edges on a logo → you probably saved a graphic as JPEG; switch to PNG. (3) Muddy faces after social upload → pre-compress at 80–85 and correct pixel width for the platform so their second encode is gentler. (4) Upload errors on our side → retry a smaller max dimension; very large RAW-derived JPEGs benefit from resizing first. (5) Need transparency → do not flatten to JPEG; use PNG/WebP, and consider Background Remover before compress.
How this fits a sane workflow: shoot or export the master → crop/resize for the channel → compress here → optional EXIF strip → upload. Reversing that order (compress a huge uncropped original, then resize) wastes bytes and can stack artefacts. For marketplaces, confirm minimum pixel rules (for example zoom thresholds) before you crush dimensions. For blogs, compress heroes aggressively enough that LCP is not image-bound, but keep a higher-quality variant only if you offer a lightbox. The compressor is a publishing tool, not a substitute for keeping originals.
Pick the right format before you pick the quality
The biggest single lever in image compression is not the quality slider — it is the format. JPEG, PNG, and WebP compress the same pixels in very different ways, and using the wrong one can mean your 4 MB input produces a 3 MB output when a different format would have produced 400 kilobytes with equal or better visual quality.
JPEG uses lossy compression tuned for photographic content. It works by splitting the image into 8×8 blocks, applying a discrete cosine transform, and quantising the result. It handles smooth gradients, skin tones, and natural scenes beautifully. It falls apart on line art, screenshots, and text — where sharp high-contrast edges produce visible ringing artefacts. PNG uses lossless compression that recognises horizontal runs of identical pixels and palette-friendly patterns. It is ideal for screenshots, UI mockups, logos, and anything with large flat colour regions. It is terrible for photographs, where every pixel is slightly different from its neighbours and the lossless encoding has nothing to compress. WebP is Google's hybrid format. It supports both lossy and lossless modes and, in most cases, produces a smaller file than JPEG or PNG at equivalent quality.
A rough guide to when each format wins
If your input is a photograph (camera output, Unsplash stock, e-commerce product shots in natural lighting), JPEG at quality 80 is the classic answer. WebP lossy at quality 75 will usually land 25–35% smaller with no perceptible difference. For the few users who still have an older Safari or Edge version that does not display WebP, JPEG remains the safe choice.
If your input is a screenshot, a software UI capture, a flat logo, or line art, PNG is almost always correct. WebP lossless also works but with less ecosystem support. Converting a PNG screenshot to JPEG is nearly always a mistake — the resulting file is often larger and always has visible artefacts around text edges.
If your input is a photo with transparency — a product shot with a transparent background — use PNG (lossless, keeps alpha) or WebP (both modes support alpha). JPEG has no transparency channel, and because this compressor always saves JPEG it fills transparent areas with white; for a transparent logo or product cut-out, use Convert Image Format to PNG or WebP instead. Saving a transparent PNG as JPEG will fill the transparent pixels with white or black, and it is surprisingly easy to do this by accident.
The quality slider, demystified
JPEG quality is a number from 1 to 100, but the scale is not linear. Below 40, artefacts are severe and visible even to casual viewers. From 40 to 70, artefacts are visible on close inspection, particularly around sharp edges and on large flat regions. From 70 to 85, artefacts are usually invisible at 100% zoom on typical displays. From 85 to 95, size increases rapidly while visible quality stays roughly flat. From 95 to 100, file size balloons with almost no perceptible gain — 100 often doubles the size of 95 for no visible reason.
For web display, 75 to 85 is the sweet spot for almost every photograph. For printing, 90 is conservative and 95 is overkill. For archival storage, keep the original uncompressed and compress only the copies you actually publish. The compressor's default setting aims at the web-display sweet spot; reach for the slider only when you have a specific reason.
Chroma subsampling and the 4:2:0 surprise
Here is a detail that trips up a lot of people: JPEG separates an image into luminance (brightness) and chrominance (colour) channels, and by default stores colour at half the resolution of brightness — a scheme called 4:2:0 chroma subsampling. The human eye is much less sensitive to colour detail than to brightness detail, so this trick saves significant space with no visible loss on photos. On images where colour detail is the point — a colour gradient, red text on a blue background, bright logos — 4:2:0 can cause a distinctly blurry appearance, which looks like "fringing" or "bleeding" on coloured edges.
If a JPEG of a logo comes out looking smeared where the colours meet, the fix is not to increase quality — the fix is to switch to PNG or WebP lossless, where chroma is full resolution. This is the most common reason graphic designers avoid JPEG for anything except photographs.
E-commerce workflows and platform-specific needs
For Shopify, Amazon Seller Central, Etsy, and eBay product listings, the critical constraints are file size limits and minimum dimensions. Amazon expects product images to be at least 1000 pixels on the long side for zoom to function, and rejects uploads above 10 MB. Etsy permits up to 20 MB. Shopify has no hard file limit but throttles display at anything above about 4 MB.
The practical workflow: export your source photo at 2000×2000 or larger (so zoom looks sharp), run it through this compressor at JPEG quality around 82 (this compressor always saves JPEG; if a marketplace wants WebP, use Convert Image Format instead), and confirm the output is under 2 MB. That gives you a file that loads fast on a phone over cellular, displays sharp on a desktop Retina screen, and leaves headroom for the marketplace's own re-encoding. For lifestyle product shots, test on both a bright phone in sunlight and a low-brightness laptop — the quality ceiling on a dim screen is much lower than you think.
Privacy posture for image uploads
Image uploads go to server RAM, get encoded, and ship back to your browser. The original and the compressed copy are both discarded when the response completes. Nothing hits persistent storage. If your image contains EXIF metadata — GPS coordinates from a phone, camera serial number, editing software tags — this compressor does not copy it into the output. The download is re-encoded as a fresh JPEG, so GPS coordinates, camera serial numbers, and editing-software tags are left out. That is a good default for anything posted publicly, because phone GPS tags routinely leak home addresses in ways people do not anticipate. If you need to keep EXIF (for a photo archive, for example), keep your original file as the master copy.
Batch workflows and sensible defaults
Most people compress images one at a time because the use case arrives one at a time — a single product photo, a single avatar, a single blog post hero. But there is a class of task where batch compression matters: migrating a website, preparing a photo gallery, processing a month of Instagram posts in one sitting. The compressor accepts multi-file uploads and processes them in parallel, returning a ZIP of the compressed outputs with the original filenames preserved. Quality settings apply uniformly across the batch, so pick the right setting for the worst-case member of the set (the photo with the finest detail) rather than the best case.
Sensible defaults for common scenarios: web thumbnail (300×300 or smaller), JPEG quality 78, WebP quality 72. Web hero image (1600×900 or similar), JPEG quality 82, WebP quality 76. Email attachment where size matters, JPEG quality 70 at 1200 pixels wide. Archival scan or photo library, PNG lossless (avoid recompression of already-compressed JPEG sources — you lose quality every round, and you cannot recover it). Print-destined photography, always start from a lossless source and compress only the copies going to screens.
One small ritual worth adopting: after compressing, actually open the output and scroll around at 100% zoom. The compressed image is what your audience sees, and a five-second inspection catches artefacts that a glance at a thumbnail misses.
Side-by-side targets for common jobs
Blog hero (desktop + mobile): long edge 1600–2000px, JPEG ~82 or WebP ~76, usually under 300–500 KB for photographic heroes after a sensible resize. Product card / category thumb: 800–1200px, JPEG ~78–82. Avatar / profile: 400–800px, JPEG ~80. Email inline photo: 1200px, JPEG ~70–78 so five images do not blow a 25 MB message. Client proof on screen: 2000px, JPEG ~88–92. Treat these as starting points; always judge the actual pixels you will show.
Frequently asked questions
- Is my image uploaded?
- Yes. Compression runs on the server so large phone and camera photos work reliably. The image is sent over HTTPS, compressed in memory for that request, returned as a download, and discarded. There is no account and no permanent archive.
- What format is the compressed file?
- Always JPEG. PNG and WebP inputs are re-encoded as JPEG, and transparent areas become white. To keep transparency or get WebP output, use Convert Image Format instead.
- What quality setting should I use?
- Start at 80–85 for websites and most email. Use 70–78 when a portal caps you at a few megabytes. Use 90–95 for print proofs or portfolio crops. Always open the result at 100% zoom before you publish.
- Why is my file still large after compressing?
- Quality alone cannot shrink a 6000px image enough. Lower the max size (for example 1600–1920px) and compress again. Flat graphics such as logos and screenshots often compress poorly as JPEG; keep those as PNG with Convert Image Format.
- Can I compress several images at once?
- Yes. Switch Mode to Bulk, select multiple images, and you get one ZIP with every image compressed at the same quality and max-size settings.
Step-by-step guides
Also try
Related tools that work well with this one: