Compress Photo Online
Cut the size of JPG, PNG and WebP by 3-5x with no visible quality loss. Processed on our server, your photos never go to the cloud.
Which preset to choose
Amazon and eBay
Marketplaces allow up to 10 MB per photo, but the real sweet spot is 300-800 KB. Anything larger is pointless: a product feed with heavy images loads slowly. The preset scales down to 1500 px on the long side and JPG quality 85.
Etsy and Shopify
The limit is 25 MB, but 200-500 KB is optimal. Preset: 1280 px, JPG 82.
Website
For blogs, portfolios and pages with heavy images. 1920 px, JPG 82, optimized for fast loading.
Email and messengers
The most aggressive preset: 1280 px, JPG 75. Great for forwarding without losing readability.
Custom
Set the maximum size and quality yourself if you want precise control.
What "without quality loss" means
Truly lossless compression usually gives only a modest gain (10-20%). Lossy compression with a well-chosen quality (80-90 for JPG), on the other hand, shrinks the size 3-5x while the difference stays invisible to the eye. That is exactly how our tool works: it balances file size against visual sharpness.
How to use it
- Drag a photo into the upload area
- Pick a preset or set the parameters by hand
- Click Compress
- Get the compressed file and see how much you saved
FAQ
Can I upload several files at once?
For now, one at a time. For batch processing of catalogs of 50-200 photos, message us in chat and we will set up batch processing.
Is the metadata (EXIF) kept?
No, we strip all metadata during compression: GPS, camera model, capture date. That both saves size and protects privacy. If you need to keep EXIF, tick the box in the widget.
Can a PNG with transparency be compressed?
Yes. A PNG is compressed to PNG (lossless) and transparency is preserved. If the PNG has no transparency, you can switch the output to JPG, which is usually 5-10x smaller.
Is WebP supported?
Yes, both as input and output. WebP is usually smaller than JPG at the same quality. We recommend it for websites, where browser support is now almost universal.
Limits?
Up to 25 MB per file, 30 files per minute per IP, 200 per day.
Related tools
- Prepare for a marketplace, resize and crop in one pass
- HEIC to JPG, iPhone photo converter
- Upscale a photo, AI upscale if your source is too small instead
How to get the best result
- Upload the original, not a recompressed file. Every extra JPEG pass adds artifacts: a camera original or an export from your editor comes out cleaner at the same weight.
- Resize in pixels first, compress second. A 6000 px photo is overkill for a product card or a web page: scaling down to 1500-2500 px saves more than any quality slider.
- Match the format to the content: photos as JPEG or WebP, graphics with transparency or text as PNG.
- Crop before compressing: margins and empty background weigh as much as the subject itself.
- Compare at 100% zoom. Artifacts show up on edges and small text; if you see none at full size, you can lower the quality further.
For a batch of files, keep the same settings so every image looks consistent.
Which format to pick: JPEG, PNG, WebP or AVIF
The container matters more than the quality slider. Picking the wrong format easily produces a file five times heavier than it needs to be, and no compression setting will rescue it.
- JPEG is the default for photographs: smooth gradients, skin, fabric, metal. It has no transparency. Quality 80-85 covers almost any product listing.
- PNG belongs only where you need transparency, or where the image is made of flat fills and hard edges: logos, icons, diagrams, interface screenshots. For an ordinary photograph PNG is wasteful and weighs 5-10x more than JPEG at the same visual result.
- WebP is the workhorse of a modern site. It runs roughly 25-35% lighter than JPEG at comparable quality, supports transparency and replaces both older formats at once. Browser support is effectively universal.
- AVIF is the most efficient mainstream option: 40-50% below JPEG, excellent on gradients and dark scenes. It encodes slowly, so it suits static site assets rather than a same-day catalogue export.
Graphics with text are a separate case: infographics, size charts, composition tables burned into the image. Small letters are the first thing lossy compression damages, and a halo appears around the strokes. Use PNG, JPEG at quality 90-92, or WebP in lossless mode.
For marketplaces, JPEG remains the safe answer. Amazon, eBay, Etsy and Shopify accept it without question, while WebP and AVIF support depends on the platform and on where in the listing the image sits.
How image weight affects site speed and rankings
Images typically account for 50-70% of page weight, so they decide how fast a page actually feels. Google grades pages on Core Web Vitals, and the headline metric, LCP, is almost always measured on the largest image above the fold. If that photo weighs 2 MB, LCP on a mobile connection drifts past 4 seconds and the page lands in the slow bucket.
Weight targets worth holding to:
- Catalogue thumbnail: 30-80 KB.
- Main product photo, 1200-1500 px on the long side: 150-350 KB.
- Wide banner or cover, 1920 px: 200-400 KB as JPEG, 120-250 KB as WebP.
- The whole page: keep total image payload under 1.5-2 MB, including everything below the fold.
Markup matters as much as bytes. Set explicit width and height on every image, otherwise the layout jumps as pictures arrive and your CLS rises. Give the hero image fetchpriority="high" and never lazy-load it, then apply loading="lazy" to everything else.
File weight is not a ranking factor on its own, but speed feeds into page assessment and engagement signals degrade directly: every extra second of waiting raises the bounce rate. On product pages that shows up in conversion within days.
Batch compressing a catalogue without ruining hundreds of files
With two hundred files instead of two, the goal changes: you no longer tune each frame, you need a predictable result across the whole export.
- One setting per series. A single preset for the entire catalogue: the same long side and the same quality everywhere. Mixed dimensions break the grid layout and force the browser to recalculate the page.
- Sample-based quality control. Do not inspect everything. Take the 5-7 hardest frames: a dark background, a smooth gradient, fur, jewellery highlights, finely striped fabric. If those are clean, the rest of the series is safe. Compare at 100% zoom, never in a shrunken preview.
- Watch the difficult zones. Look at flat backgrounds, where blockiness appears, and at the edges of high contrast objects, where a halo shows up. If you spot either, raise quality by 5 points and rebuild the series from the originals.
- Files that were already compressed. Recompressing lossy files stacks artefacts: each pass adds to the last, and there is no way back. If the originals are gone and you must work from finished JPEGs, do not go below quality 85 and do not downscale a second time. The better route is to return to the shoot archive and rebuild everything in a single pass.
Always keep an untouched archive of full quality originals. Platform requirements change, and rebuilding an export from source takes an hour, while rebuilding it from recompressed copies is simply not possible.