Compress image to 1000 KB
Land on 1000 KB, not “somewhere under it”. Nothing is uploaded.
- No upload
- Exact target size
- Batch ready
Drag images here, or click to choose
JPG / PNG / WebP / HEIC · up to 25MB each · batch supported
Files never leave your device — everything runs in your browser.
Progress
That file could not be processed
Why 1000 KB is a hard gate, not a suggestion
A form that says “maximum 1000 KB” rejects a 1001 KB file. Most compressors only promise “compressed”, so people submit, get rejected, lower the quality slider, and try again. This tool searches for the best quality whose encoded byte count is still ≤ 1000 KB, then reports the exact number it produced.
Why 1000 KB specifically
One megabyte is the psychological limit used by LMS platforms and print shops, and it is strict: “under 1 MB” means the file must not reach 1024 KB, so aim at 1020 KB rather than 1024. Visually the output is identical to the source in almost every case — you are buying a smaller envelope, not a different picture.
Where a 1000 KB cap actually comes from
- Forums and community platforms with a 1–2 MB limit per image
- Learning management systems and print-on-demand uploads
- Phone-to-cloud backup, where 2 MB is a big cut with no visible change
- Client deliverables with a “keep it under 2 MB” instruction
If your form states a pixel size as well (for example 600×600 px), set the target size first and check the output dimensions — the two limits sometimes conflict.
What resolution survives at 1000 KB
At a typical JPEG quality of 70–80%, a byte budget converts to a pixel budget. These are the dimensions that stay clean:
| Aspect | Dimensions | Typical use |
|---|---|---|
| 1:1 | 1740×1740 | profile, 2×2 in photo |
| 3:2 | 2130×1420 | camera default, prints |
| 16:9 | 2310×1300 | screens, slides |
These are computed, not copied: bytes ÷ 0.34 ≈ usable pixels. Going wider than this at 1000 KB starts to show blocking on skin and text.
Why one pass usually misses the target
JPEG size is not linear in quality: dropping from 90% to 80% can halve the file, then 80% to 70% only saves 15%. A single guess either overshoots the limit or wastes 40 KB of headroom. This tool encodes, measures, and narrows the range until the output sits within about 2% of the limit — and if even the lowest quality cannot reach the target, it reduces dimensions instead of shipping a broken image.
JPG, WebP or PNG at 1000 KB?
At the same 1000 KB, WebP keeps roughly 8–12% more quality than JPG and preserves transparency — but a handful of legacy government portals still reject .webp, so check the form’s accepted types first. JPG is the safest default for photographs: every portal accepts it, and the cost is that transparency is flattened onto white (or the background colour you pick) and thin text edges soften. PNG is lossless, so “1000 KB” cannot be reached by lowering quality at all — the tool reduces pixel dimensions instead, which is the right trade for screenshots, logos and line art and usually the wrong one for photos.
Privacy: the file never leaves the tab
No upload request is made. The browser decodes the image, re-encodes it on a worker thread, and hands you a download blob. You can open DevTools → Network, drop a file, and confirm there is no request carrying it. You can also switch off your network and it still works.