Compress image to 300 KB

Set the budget, and the encoder is searched for the best quality that fits under 300 KB. On your device — the image is never uploaded.

  • 0 uploads
  • No limits
  • No signup
  • Works offline

Where a 300 KB limit comes from

Nobody chooses 300 KB for fun. If you are here, a form told you to, and the form probably did not explain how. These are the places this particular number turns up:

  • Web page hero images where page weight matters
  • Portfolio uploads with a per-file cap
  • Marketplace listings with high-resolution requirements

At 300 KB even a detailed 2000-pixel photograph — foliage, crowds, textured fabric — stays clean.

What 300 KB actually buys you

Three hundred kilobytes is enough for a detailed 2000-pixel photograph, which means it holds up on the images that defeat smaller budgets: foliage, crowds, textured fabric, anything with high-frequency detail spread across the whole frame. Those subjects are expensive precisely because there is nothing for the encoder to simplify.

This is also the budget where format choice starts paying real dividends. The same photograph that needs 300 KB as a JPEG frequently fits in noticeably less as WebP at matching visual quality, and better still as AVIF if the destination accepts it. If the form does not insist on JPEG, converting is a free win.

Comfortable for anything that is not going to print. The search here spends the budget on dimensions before quality — a larger image at quality 55 beats a smaller one at 95, because the eye forgives artefacts more readily than missing resolution.

Getting a better result

Three things reliably help when the budget is tight:

  • Crop before compressing. Every pixel you keep costs bytes. A tightly framed portrait at 300 KB looks far better than a full-body shot squeezed into the same space. The cropper hands its result straight to this tool.
  • Start from the highest-quality original you have. Compressing an image that has already been through WhatsApp compounds the damage. Go back to the file straight off the camera.
  • Prefer WebP if the form allows it. At the same file size WebP holds noticeably more detail than JPEG. Most official forms still want JPG, but it costs nothing to check.

Other common targets

10 KB · 20 KB · 30 KB · 50 KB · 100 KB · 150 KB · 200 KB · 500 KB

How it works

  1. 01Add your imageDrop it on the page, click to browse, or paste from the clipboard.
  2. 02The 300 KB target is already setYou landed on this page, so the budget is filled in. Change it if you need something different.
  3. 03The search runsThe encoder is run repeatedly, binary-searching quality for the best result that still fits under 300 KB.
  4. 04Compare, then downloadDrag the before/after slider to see what the compression cost before you commit.

Questions people actually ask

Would WebP or AVIF get me under 300 KB more easily?
Usually yes, and sometimes by a wide margin on detailed photographs. The catch is acceptance — plenty of upload forms take JPEG and PNG only, and reject anything else without saying why. Check what the form states before converting, and keep a JPEG copy as a fallback.
Will my photo still look acceptable at 300 KB?
At 300 KB even a detailed 2000-pixel photograph — foliage, crowds, textured fabric — stays clean. Comfortable for anything that is not going to print.
Is the result exactly 300 KB?
It lands within about 5% below 300 KB, and never above it. Going over would defeat the point — a form that says "maximum 300 KB" rejects a file of 301 KB without explanation.
Is my image uploaded to reach 300 KB?
No. Every encode in the search runs on your own device, in a background thread, using WebAssembly builds of MozJPEG and libwebp.