Image Optimizer
Compare 7 optimization recipes side-by-side and pick the smallest that still looks great. JPG, WebP, and lossless PNG variants, with file sizes and percentage-of-original. Runs in your browser.
Drop an image to compare 7 optimization recipes
JPG, PNG, WebP, GIF, AVIF · never uploaded
How image optimization works
ToolChop decodes your image once into a canvas, then re-encodes it seven times with different quality and format settings — three JPG, three WebP, and one lossless PNG. Each variant shows its file size, the percentage of the original size, and a preview thumbnail so you can spot quality issues immediately.
The smallest variant is highlighted in green. Use the previews to confirm the low-quality variants still look acceptable for your use case — sometimes the smallest variant is the right pick, sometimes you want the next-larger one for safety.
Why a local optimizer matters
Image optimization is almost always a pre-publication step: flattening client design work, shrinking screenshots for a support ticket, prepping product photos for a CMS upload. The originals are usually the highest-stakes version — full resolution, unwatermarked, no overlay. Uploading them to a third-party optimizer is the worst place in the workflow to do that. ToolChop keeps everything local.
Which recipe to pick
- WebP-92% — hero images, large product shots
- WebP-80% — body content, blog images
- WebP-65% — thumbnails, listing tiles
- JPG-92% — when you need broad compatibility but quality matters
- JPG-85% — everyday sharing, email attachments
- JPG-70% — when file size is tight and you can accept some compression
- PNG — screenshots with sharp text, UI mockups, icons, anything with transparency
Frequently asked questions
How do I optimize an image's file size online?
Drop your image. ToolChop generates 7 optimized variants (JPG ×3, WebP ×3, PNG) and shows each with its file size and a preview thumbnail. The smallest variant is highlighted. Visually compare to make sure quality is still acceptable, then click Download on the one you want. No account, no upload, no daily limit.
Does ToolChop upload my image?
No. The image is decoded into a canvas in your browser, and every variant is encoded locally using the browser's image encoder. None of the variants travel to a server. This matters because optimization is most often done to confidential design work or sensitive screenshots that should not be uploaded to a third-party site just to compare file sizes.
Why is the privacy story important for an image optimizer?
Image optimization is usually a pre-publication step — flattening client design work for upload to a CMS, shrinking screenshots for a confidential support ticket, preparing product photos for an e-commerce upload. The original images are typically the highest-stakes version (unflattened, unwatermarked, full resolution). Uploading them to a third-party optimizer is a needless data path. ToolChop keeps everything local.
What are the 7 recipes ToolChop generates?
JPG at 92%, 85%, and 70%; WebP at 92%, 80%, and 65%; and PNG (lossless). Three quality tiers per lossy format, plus a lossless reference. This spread covers the practical optimization space — from 'visually lossless' (92%) to 'aggressive compression for tiny thumbnails' (70% / 65%).
Which variant is best for the web?
Almost always WebP — it's typically 25–35% smaller than JPG at the same visual quality, and modern browsers (Chrome, Firefox, Safari 14+, Edge) all support it. Use WebP-92% for hero images where quality matters; WebP-80% for body content; WebP-65% for thumbnails.
Which variant is best for email or sharing?
JPG — it's still the most universally compatible format, especially for older email clients and apps that don't decode WebP. Use JPG-92% for archive copies, JPG-85% for everyday sharing, JPG-70% for tight email size budgets.
Should I ever pick the PNG variant?
Use PNG only when you need pixel-exact fidelity (screenshots with sharp text, UI mockups, icons) or when you need transparency. For photographs, PNG is almost always the largest variant and is rarely the right choice unless quality is absolutely paramount.
Why is WebP-65% sometimes smaller than JPG-70% but looks better?
WebP uses a more modern compression algorithm (VP8/VP9-based) than JPG (DCT). At low quality settings, the difference is dramatic — WebP can preserve detail JPG smears. That's part of why WebP is now the recommended default for the web.
Why is my source image smaller than all the optimized variants?
If your source is already a heavily optimized JPG or WebP, ToolChop's encoders may not beat it. The browser's built-in JPG/WebP encoders are tuned for speed, not maximum compression — dedicated optimizers like mozjpeg or libwebp at slow modes can sometimes beat them. For most everyday images, the variants here are competitive.
Does the optimizer resize the image?
No — every variant has the same pixel dimensions as the source. The optimizer changes the encoding only. To resize too, use the Image Resizer first (smaller dimensions = drastically smaller files), then bring the resized image here.
Can the optimizer preserve transparency?
PNG and WebP variants preserve transparency. The JPG variants flatten transparency against a white background (JPG cannot store alpha). If transparency matters, pick the WebP variant — it has the best size/quality tradeoff among transparency-supporting formats.
Why use ToolChop instead of TinyPNG, Squoosh, or an online optimizer?
TinyPNG and most online optimizers upload your file to their servers for processing. Squoosh is a Google tool that, like ToolChop, runs in the browser — both are great for privacy. ToolChop's specific differentiator is the side-by-side comparison view: 7 variants visible at once with file sizes, so you can choose by eye in seconds instead of testing one at a time.