Bring an image under 1 MB
Starts from a high quality setting and narrows down, so a large photo keeps detail wherever the budget allows. Files stay on your device.
How this works locally
- You choose a file; the page reads it from your device.
- The matching engine is loaded from fileslimmer.com and runs in a Web Worker.
- The result is written back to a location you choose on this device.
Before or choose files from your device
Original size —
Accepted formats
- Reads
- JPG · PNG · WebP · AVIF
- Writes
- JPG · PNG · WebP · AVIF
Estimated memory
Your browser reports only a coarse memory hint, so this figure is an estimate.
| Device profile | Largest file | Largest image | Files per batch |
|---|---|---|---|
| Minimal | 40 MiB | 32 megapixels | 50 |
| Low | 75 MiB | 50 megapixels | 100 |
| Balanced | 150 MiB | 90 megapixels | 250 |
| High | 250 MiB | 150 megapixels | 500 |
Your browser is placed in one of these profiles from the coarse hints it exposes. A file above the limit is refused before it is read, rather than after the tab has run out of memory.
Limitations
- Lossy compression discards detail permanently. Re-compressing a file that was already compressed removes more detail without recovering anything an earlier pass removed.
- The target size is what the search aims at, not what the result is promised to be. The search stops at the configured quality floor and reports the smallest file it reached.
- An animated GIF, WebP or AVIF is not handled by the still-image engine. It is refused rather than quietly reduced to its first frame.
Target size
Best-effort local compression. If the target cannot be reached safely, FileSlimmer returns the smallest acceptable result.