Which image formats are supported?
The tool accepts JPG/JPEG, PNG and WebP files. Your browser must also support decoding the selected file and encoding the chosen output format.
Compress batches of JPG, PNG and WebP images in your browser with adjustable quality, format controls, previews and private downloads.
Drag files into the panel or use the file picker.
Up to 10 files, 10 MiB each, 30 MiB per batch and 16 megapixels per image.
Quality applies to JPEG and WebP output. PNG is re-encoded without a quality setting and may not become smaller.
If an encoded result is not smaller, Tool Teaze keeps the original instead of silently enlarging it. Re-encoding may remove metadata, and animated images are flattened to the decoded frame.
Choose images to begin.
Your images are processed in your browser and are not uploaded to our servers.
This image compressor re-encodes JPG, PNG and WebP files locally in your browser. It measures the real output size and keeps the original when an encoded result would be larger.
Input: A batch of JPG, PNG and WebP images up to 10 MiB each
Output: Measured browser-encoded images, or the retained original when re-encoding is not smaller
The tool accepts JPG/JPEG, PNG and WebP files. Your browser must also support decoding the selected file and encoding the chosen output format.
Quality from 40% to 95% is passed to the browser's JPEG or WebP encoder. Lower values usually create smaller files with more visible loss. PNG output does not use this lossy quality setting.
No. Browser PNG re-encoding may produce the same size or a larger file. If any encoded result is not smaller, the tool keeps the original and reports zero reduction instead of claiming a saving.
No. Validation, decoding, canvas processing, previews and downloads run in your browser. Tool Teaze does not send image content to its servers or a third-party compression API.
A batch can contain up to 10 images, each no larger than 10 MiB, with a 30 MiB total and a 16-megapixel decoded-image limit. Files are processed one at a time to bound memory and CPU use.
Not necessarily. Canvas re-encoding can remove metadata such as EXIF fields, and animated images are flattened to the frame decoded by the browser.