Savings are measured after encoding
BeanNest compares the verified output bytes with the original file. If the result is not smaller, the tool recommends the original and does not present the larger re-encode as a successful compressed download.
Free browser tool
Choose a quality level and a browser-supported output format. BeanNest re-encodes the pixels locally, verifies the result, and only calls it smaller after comparing the actual bytes.
Quick feedback
One tap is enough. You can ignore this and keep working.
Thanks — that helps us improve.
BeanNest compares the verified output bytes with the original file. If the result is not smaller, the tool recommends the original and does not present the larger re-encode as a successful compressed download.
Light sends 82%, Balanced 70%, and Strong 55% to supported lossy browser encoders. They are not guaranteed size reductions. Actual bytes depend on the image content, output format, and browser encoder.
Automatic keeps supported JPG, WebP, or AVIF sources in their own format. Other sources prefer WebP when this browser can encode it. Output options the browser cannot create are disabled instead of being promised.
PNG encoding ignores Light, Balanced, and Strong. A PNG re-encode can stay the same size or grow, especially when the source is already optimized. Try WebP or another supported format when smaller bytes matter more than keeping PNG.
Compression does not resize the image. The pixels are decoded and encoded again, so original camera metadata and other file metadata should not be treated as preserved. JPG also replaces transparent areas with white.
This tool processes one image at a time and applies the current device profile to input bytes, decoded pixels, canvas dimensions, output bytes, and processing time. An image can be rejected before compression if it exceeds those safety limits.
Need a different result? resize the pixel dimensions, convert the image format, or remove image metadata with a dedicated workflow.