Skip to content

300 KB

Resize a photo to exactly 300 KB

300 KB is 307,200 bytes. This page is preset to that number, and the tool lands on it exactly whether your file needs to shrink or grow. Everything runs in your browser, so your photo is never uploaded. 300 KB covers generous photo fields and multi page document uploads.

Updated , written and tested by Rizwan Aslam

Resize your photo to 300 KB

Preset to 300 KB. Change the number if your form asks for something else.

Nothing leaves this device
Quality strategy
Output format
Common targets
0 KBBefore
0 KBAfter
0 x 0Dimensions
100%Encoder quality

What 300 KB actually looks like

Three hundred kilobytes is a generous target. It appears on photo fields with room to spare and on document uploads where several pages or a detailed scan must fit one file. Quality stops being the problem at this size; sending far more than the form needs is the usual mistake.

Most phone photos still arrive larger than 300 KB, so shrinking is the common direction, while detailed scans may need to grow. The measure that decides quality is bits per pixel: the file size in bits divided by the number of pixels. Here is what 300 KB gives you at three sizes.

Measured quality of a 300 KB file at three photo sizes
DimensionsPixelsBits per pixelResult
600 x 8000.48 MP5.12Excellent, no visible difference
900 x 12001.08 MP2.28Excellent, no visible difference
1800 x 24004.32 MP0.57Acceptable, slightly soft up close

The largest photo that still looks very good at 300 KB is around 1520 by 2030 pixels. That is the point where this target still delivers roughly 0.8 bits per pixel. Above it, quality starts dropping whatever tool you use.

Both directions, one page

Both cases turn up at this target, which is why splitting them into two separate tools makes no sense. Most sites give you one tool to grow a file and a different one to shrink it, but the same algorithm does both, so this page does both.

What happens depending on your starting file size
Your fileWhat the tool doesPicture quality
Over 300 KBBinary searches encoder quality downward until it fits, then pads back up to the exact byteAs good as 300 KB allows
Under 300 KBRaises encoder quality as high as still fits, then pads the remainder losslesslySlightly sharper than before
Already 300 KBNothing at all, and it tells you soUntouched

The padding is not a trick. Every major format reserves a block for data decoders skip, so writing neutral bytes there changes the file size and not one pixel.

Getting 300 KB accepted

Three things worth knowing before you upload.

  • Treat the number as a ceiling when only a maximum is given, and land just under it.
  • Resize before you compress. Scaling to the pixels the form asks for gives the encoder far more room.
  • Size each page of a scan. For multi page documents, fit every page to a sensible share of the limit instead of letting one page eat the whole budget.

The format behaviour described here follows the same rules set out in MDN's guide to image file types.

More rejection messages and what each one really means are in the guide to why forms reject photos.

Questions about the 300 KB target

Does compressing to 300 KB change my photo dimensions?

Not unless you ask it to. Compression lowers file size while width and height stay the same. The sharpest possible strategy will scale the image down when that is the only way to keep quality reasonable, and it tells you when it does.

How many bytes is 300 KB exactly?

307,200 bytes when 1 KB means 1024 bytes, or 300,000 when it means 1000 bytes. Since 300 KB is nearly always a ceiling, target the smaller figure and you pass under either interpretation.

Will my photo look bad at 300 KB?

It depends on the pixel dimensions, not on the tool. At 600 by 800 you get 5.12 bits per pixel, which is excellent, no visible difference. At 1800 by 2400 the same file size gives 0.57 and the result is acceptable, slightly soft up close.

What is the largest photo that still looks good at 300 KB?

Around 1520 by 2030 pixels. That is where 300 KB still delivers roughly 0.8 bits per pixel, the point at which most people stop seeing compression damage.

Other targets