Why Are My PNG Files So Large?

You export a simple screenshot and it lands at 6 MB. You save a photo as PNG and it's bigger than the original camera file. If PNG keeps surprising you with its heft, you're not doing anything wrong, you're just running into how the format works. Once you understand the four things that drive PNG size, the fix is usually obvious.

1. PNG is lossless, by design

The headline reason is that PNG stores your image without discarding any data. Every pixel is recorded faithfully so it can be reproduced exactly. That's wonderful for a logo or a chart, but it means PNG can't do the aggressive shortcut that makes photographs small: throwing away detail your eye won't miss.

JPG does take that shortcut, which is why the same photo is often a fraction of the size as a JPG. PNG's honesty is precisely what makes it heavy for the wrong kind of image.

2. Dimensions matter more than you think

File size scales with the number of pixels, and pixel counts grow fast. Doubling the width and height of an image doesn't double its size. It roughly quadruples it, because you've added pixels in both directions.

A 4000 × 3000 screenshot has 12 million pixels. Even efficiently stored, that's a lot of data. Before blaming the format, check whether the image is simply larger than it needs to be. A screenshot displayed at 800 pixels wide doesn't need to be saved at 4000.

3. Photographic content defeats PNG's compression

PNG does compress, but its compression rewards large areas of the same colour and simple, repeating patterns. A flat UI or a diagram with a handful of colours squashes down nicely.

Photographs are the opposite: every pixel is subtly different from its neighbour, with smooth gradients and fine texture everywhere. PNG has almost nothing repetitive to exploit, so it stores nearly all of it verbatim. That's why a photo saved as PNG can be enormous while the same photo as JPG is tiny.

4. Extra channels and metadata

A few smaller factors add up:

• The alpha (transparency) channel adds a fourth value to every pixel, increasing size even where the image is fully opaque.
• High colour depth (16-bit PNGs) doubles the data per channel.
• Embedded metadata (colour profiles, editing history, thumbnails) quietly pads the file.

None of these dominate on their own, but together they explain why two visually identical PNGs can differ in size.

What to do about it

Match the fix to the cause:

• It's a photo or screenshot? Convert it to JPG. This is the single biggest win. Lossy compression is built for exactly this content, and savings of 60–90% are common. Our PNG to JPG converter does it in the browser: pick a fill colour for any transparent areas, set the quality, and download.
• It's genuinely too big in dimensions? Resize it down to the size it's actually displayed at before anything else.
• It's a real logo or icon that must stay PNG? Then it should already be small: if it isn't, it's probably saved at oversized dimensions or with unnecessary metadata.
• You need transparency and small size? Consider WebP, which supports both, or accept a solid background and use JPG.

A simple mental model

Think of PNG as a format that says "I'll remember everything exactly." For a crisp logo, that's a feature. For a 12-megapixel photo, that promise is expensive, and JPG's willingness to forget the imperceptible details is exactly what you want.

If your PNGs feel too large, they almost always are, and it's rarely a mystery. Identify whether you're fighting losslessness, dimensions, or photographic content, apply the matching fix, and those bloated files shrink fast.

The format is doing what you told it to

PNG is lossless by definition: it must preserve every pixel exactly, so it can only squeeze out repetition. Flat interface colours repeat beautifully. The fine sensor noise in a photo repeats almost never, which is why a photograph in PNG balloons. When you convert one here, the JPEG is produced by the MozJPEG encoder compiled to WebAssembly, running in your browser. It is the same encoder class the big image pipelines use, and it exists precisely for the photographic content PNG handles worst.

Sources

• PNG Specification, Third Edition (W3C)
• Image file type and format guide (MDN Web Docs)