Skip to content

1 MB

Resize a photo to exactly 1 MB

1 MB is 1,048,576 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. 1 MB is asked for by portals that want a high resolution copy.

Updated , written and tested by Rizwan Aslam

Resize your photo to 1 MB

Preset to 1 MB. 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 1 MB actually looks like

One megabyte is a high resolution request. Portals that set a 1 MB target, or a minimum near it, want a copy with detail to spare, usually for records that will be zoomed into later. The surprise for most people is how often the file has to grow, not shrink, to get there.

A photo exported from a phone app or a messaging app often arrives at a tenth of this size, stripped down by the app. Growing it back to 1 MB restores the byte count, not the detail the app removed. The measure that decides quality is bits per pixel: the file size in bits divided by the number of pixels. Here is what 1 MB gives you at three sizes.

Measured quality of a 1 MB file at three photo sizes
DimensionsPixelsBits per pixelResult
600 x 8000.48 MP17.48Excellent, no visible difference
900 x 12001.08 MP7.77Excellent, no visible difference
1800 x 24004.32 MP1.94Excellent, no visible difference

The largest photo that still looks very good at 1 MB is around 2800 by 3730 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 1 MBBinary searches encoder quality downward until it fits, then pads back up to the exact byteAs good as 1 MB allows
Under 1 MBRaises encoder quality as high as still fits, then pads the remainder losslesslySlightly sharper than before
Already 1 MBNothing 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 1 MB 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.
  • A bigger file is not a sharper photo. If the original looks blurry, start from a better original. Padding reaches the byte count; it cannot invent detail.

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 1 MB target

Does compressing to 1 MB 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 1 MB exactly?

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

Will my photo look bad at 1 MB?

It depends on the pixel dimensions, not on the tool. At 600 by 800 you get 17.48 bits per pixel, which is excellent, no visible difference. At 1800 by 2400 the same file size gives 1.94 and the result is excellent, no visible difference.

What is the largest photo that still looks good at 1 MB?

Around 2800 by 3730 pixels. That is where 1 MB still delivers roughly 0.8 bits per pixel, the point at which most people stop seeing compression damage.

Other targets