Set a target file size and format - the search finds the highest quality that still fits, stepping resolution down only if quality alone can't get there. Batches, video, and a crop/rotate editor included.
Three steps. The target-size search and any crop/rotate you set run server-side, so the result is guaranteed to land at or under your target - not just close to it.
Tap one to load it into Options above - hand-edit anything afterward and it switches to Custom. Not sure what target to use? See the current upload size limits by platform.
The short version is below - the format guide covers AVIF and HEIC too, and why AVIF isn't an output option here yet.
For images, the server binary-searches encoder quality between a perceptual floor and the format's max at a given width. If nothing fits at any quality, it steps width down and searches again - so the result lands at or under your target, not just close to it. See the full breakdown of when quality drops versus when resolution does.
No. Files are processed in memory or a short-lived temp location only for as long as it takes to compress and return them, then swept automatically. There's no account system and no database of uploads.
It's not silently resolved. You'll be shown both the smallest file at your resolution floor and the smallest resolution that actually hits your target, and asked to pick.
Yes - open the per-file editor (or "Edit all" for a batch) to crop, rotate, flip, lock an aspect ratio, or set a focus point. Geometry is sent to the server and baked in before the size search runs.
Video targets a bitrate computed from your target size and duration, then encodes once with at most one corrective re-encode - it's best-effort, landing close to rather than exactly at your target, and can degrade resolution/audio bitrate if needed. See the video tool.
It always lands at or under your target, with two documented exceptions: if the file is already smaller than your target and no format conversion was requested, it's returned unchanged rather than re-encoded larger; and if your minimum-resolution floor makes the target unreachable, you're shown a conflict to resolve yourself instead of it being silently picked for you.
Yes. HEIC/HEIF - the format iPhones save photos in by default - is detected automatically and converted internally before compression, so you can drop HEIC files in directly and get back JPEG, WebP or PNG at your target size. The pre-compress crop/rotate editor can't preview HEIC in the browser, so cropping isn't available for those files, but compression itself works the same as any other format.
Yes - a batch can mix JPG, PNG, WebP, GIF, AVIF, BMP and HEIC files together; each is compressed independently to the format and target you set. There's a per-batch file-count cap and a per-file size cap to keep the shared server responsive for everyone - the current limits are shown above the drop zone.
Quality below a perceptual floor (around 30 for JPEG/WebP) starts visibly degrading color, so the search stops there and steps image width down about 15% at a time instead, re-running the quality search at each width until one fits. That trade-off - resolution over color fidelity - is why a very tight target on a large photo can come back noticeably smaller in pixels, not just more compressed.
No install - it's a normal website. Drop files or tap "browse files" from your phone's photo library the same as on desktop; compression runs on the server, so there's no app, browser extension, or desktop software required.