Compress JPEG, PNG, and WebP locally. Choose quality or search for an output at or below a size limit, with optional dimension reduction and verified output bytes.
Choose a quality setting or a byte limit
Quality mode re-encodes supported files using your settings. Target-size mode searches for a result at or below your maximum, then checks the actual encoded byte length. It does not promise an exact size, lossless compression, or acceptance by a particular upload portal.
Dimension reduction is optional and off by default. JPEG/WebP target searches use quality settings from 25–95%; PNG does not use a quality slider. JPEG output places transparency on white. All file processing is local; the surrounding page still downloads assets and analytics as described in our privacy policy.
Choose local images
JPEG, PNG, WebP. Up to 20 files and 200 MB combined; 50 MB per file. Decoded images must be at most 40 million pixels and 16,000 pixels on either edge. Devices may have lower practical limits.
Compression settings
PNG ignores this slider. Without conversion, each file keeps its input format.
This explicit width limit applies in either mode, independently of optional further reduction.
File results
Inspect detail and readability before using an output. Target-mode results are downloaded only when you choose their links; oversized candidates are not offered as successful results. Batch downloads are separate files, not a ZIP.
What the target search does
A matching-format original that already fits, with no width reduction requested, is kept without re-encoding. Otherwise JPEG/WebP searches first try 95% and 25% quality, then up to seven intermediate settings if a fitting candidate is found. Optional resizing tries at most eight image sizes, for at most 23 encodes. PNG only tries size changes, not quality changes. Every successful result is checked against its actual encoded bytes; this is not a guarantee of the best possible quality or of finding every possible fit.
Keep required dimensions
Leave extra dimension reduction off if a form requires a particular resolution. An explicit initial maximum width still applies. If the bounded search cannot fit the target, no oversized output is labeled successful. Inspect the preview for legibility and confirm the receiving service accepts the result. See the image compression walkthrough.
Frequently Asked Questions
Does this upload my images?
No. Decoding, encoding and byte checks run locally using browser APIs. The page still loads shared site assets and analytics as described in the privacy policy.
Will it produce exactly 200 KB?
No. Target mode looks for an output at or below 200,000 bytes when you enter 200 KB. If a receiving system requires strictly less, choose a lower target to leave margin. Other dimensions, content and format requirements still apply.
What if it cannot meet the target?
It reports that the target was not reached within its bounded search, shows the smallest tried size, and does not offer that oversized result as a success. Try another format, lower initial width, optional dimension reduction, or a larger limit.
What happens to transparency?
PNG and WebP can preserve transparency. JPEG cannot; JPEG output uses a white background. Lossy encoding and dimension reduction can remove detail even when a size target is met.
Does it remove image metadata?
No metadata-removal guarantee is made. Already-fitting matching files can be returned unchanged, including their metadata. Re-encoding can alter metadata, color, animation and detail; keep the original and inspect the result.
Can I cancel or clear files?
Cancel stops between browser decode/encode operations; it cannot interrupt an operation already running. Existing completed results remain available. Clear or selecting new files removes result links and releases their object URLs. Batch results are separate files, not ZIP archives.
