Your PNG is large because the format uses lossless compression that stores every pixel exactly. That is perfect for logos and screenshots but disastrous for photographs, where millions of subtly different colours give the compressor almost nothing to remove. The result is a photo-heavy PNG many times larger than the same image as JPG. The format is not broken; it is doing precisely the job it was designed for, which happens to be the wrong job for a photo. This guide explains every reason a PNG balloons, from compression to resolution to hidden metadata, and gives you the fastest fix for each situation.

The main reason: lossless compression

PNG compression works like a ZIP file, using an algorithm called DEFLATE that packs data without discarding any of it, so the image rebuilds pixel for pixel. Compression of this kind works by finding repetition and predictability. A flat graphic with a handful of colours is enormously repetitive: a thousand identical white pixels in a row compress to almost nothing.

A photograph is the opposite. Every pixel differs slightly from its neighbour thanks to sensor noise and natural gradients, so there is almost no repetition to exploit. The compressor tries, finds little, and stores something close to raw pixel data. This is why the same photo can be several megabytes as PNG but a few hundred kilobytes as JPG, which discards the imperceptible differences PNG faithfully preserves.

Resolution: the multiplier nobody notices

File size scales with pixel count, and pixel count scales with the square of the dimensions. Double the width and height and you get four times the pixels. A photo at 6000 pixels wide holds four times the data of the same shot at 3000, and sixteen times a 1500-pixel version.

This matters because modern devices produce enormous images by default. A recent phone shoots 12 megapixels or more, and a 4K screenshot is over 8 million pixels. If that image will be displayed at 800 pixels wide on a webpage, you are storing roughly fifty times more data than anyone will ever see. Resolution is the single most overlooked cause of a bloated PNG, and resizing costs nothing in visible quality when the image was oversized to begin with.

Colour depth: PNG-24 versus PNG-8

PNG comes in variants, and the wrong one wastes space. PNG-24 stores millions of colours, using 8 bits each for red, green, and blue, which photographs genuinely need. PNG-8 limits the image to a palette of 256 colours, which is plenty for a logo, an icon, or a simple illustration.

Saving a two-colour logo as PNG-24 means every pixel carries capacity for 16 million colours it will never use. Converting it to PNG-8 can cut the file by more than half with no visible change at all, because the image only ever contained a handful of colours. Both variants support transparency, so you lose nothing. Many editors default to PNG-24, which is why so many simple graphics are needlessly heavy.

Metadata and the hidden weight

PNG files carry more than pixels. Colour profiles, editing history, software tags, timestamps, and text chunks all ride along invisibly. On a small graphic this overhead can be a surprisingly large share of the file. A lossless optimizer strips this material and repacks the compression, typically saving 10 to 30 percent with zero change to a single pixel. It is the safest possible optimisation, since the image is bit-identical afterward.

Screenshots: the worst case

Screenshots deserve special mention because they combine every problem at once. Operating systems save them as PNG by default, and you cannot change that on iOS or in most Windows capture tools. A full-screen grab is high resolution, and if it contains a photo, a video frame, or a gradient-heavy interface, it is photographic content trapped in a lossless format. That is precisely the scenario PNG handles worst, which is why a single screenshot can run 3MB to 8MB. A folder of them reaches gigabytes quickly, and converting them to JPG typically reclaims 80 percent or more.

The fastest fix: convert to JPG

For any photographic PNG, converting to JPG is the largest saving available, and it takes one step. Drop the file into our converter, keep quality around 90, and a multi-megabyte PNG becomes a few hundred kilobytes with no visible loss. Batch a whole folder at once with Download All. This is the right move whenever the image has no transparency and is headed for the web, email, or an upload form. For the exact quality settings, see the quality guide.

When you must keep transparency

If the image needs its transparent background, JPG is out, but you still have three good options. WebP runs 25 to 35 percent smaller than PNG while keeping the alpha channel, and every modern browser supports it. Reducing a flat graphic from PNG-24 to PNG-8 shrinks it sharply with no visible change. And resizing to the real display dimensions helps regardless of format. Our converter exports WebP directly, and the PNG vs WebP guide covers the trade-offs.

A diagnostic checklist

Work through these in order and you will find the cause:

Is it a photo or a screenshot of one? Convert to JPG. This alone fixes most cases.
Are the dimensions far larger than the display size? Resize first, before any format change.
Is it a flat graphic saved as PNG-24? Re-save as PNG-8 to cut the palette.
Does it need transparency? Use WebP rather than PNG.
Still slightly too big? Run a lossless optimizer to strip metadata.

The first question resolves the overwhelming majority of large PNGs, because the format is almost always being asked to store a photograph, which is the one thing it was never built for.

Why optimizers cannot save a photographic PNG

A reasonable instinct on finding a 6MB PNG is to run it through a PNG optimizer and expect a big win. It will not come, and the reason is worth understanding. Optimizers work losslessly: they strip metadata, try smarter filter choices, and repack the DEFLATE stream more efficiently. Every one of those gains comes from removing redundancy, not detail. A photograph has almost no redundancy left to remove, because its pixels are all slightly different. So the optimizer works hard and returns 10 or 15 percent, leaving you with a 5MB file that is still hopeless for email.

This is the clearest signal that the format is wrong for the content. When lossless optimisation barely moves the needle, it is telling you the file is not bloated by waste; it is honestly storing photographic data that PNG was never meant to hold. The answer is a format change, not more optimisation.

The transparency trap

Many large PNGs exist for one reason: someone needed transparency once, saved as PNG, and never revisited it. The question worth asking is whether the image still needs its alpha channel today. A product photo cut out for a website header might now sit on a plain white section, where the transparency does nothing but cost you megabytes. A logo exported as a transparent PNG might be used only on white.

If the transparency is genuinely unused, converting to JPG with a white fill gives you the same visible result at a fraction of the weight. If it is used, WebP keeps the alpha channel while still cutting 25 to 35 percent. Either way, check rather than assume; transparency is often a leftover from an old workflow rather than a live requirement.

Choosing the right target size

Knowing a PNG is too big is only half the problem; knowing what to aim for is the other half. As rough guidance, a full-width web hero image should land under 200KB, an in-article photo under 100KB, a thumbnail under 30KB, and an email attachment set under a few megabytes in total. Upload forms state their own cap, commonly 100KB or 200KB, and that number is not negotiable.

These targets are achievable for almost any photograph once it is a JPG at a sensible resolution. If you have a specific cap to meet, Target Size mode in our converter hits it automatically by searching quality levels for the sharpest version that fits, which removes the guesswork entirely. The 100KB guide walks through the most requested limit.

Preventing large PNGs in the first place

Fixing bloated files one at a time is slower than not creating them. A few habits stop the problem at the source. On Windows 11, the Snipping Tool lets you choose JPG in its save dialog, so a screenshot bound for an upload form never becomes a PNG at all. On Mac, the screenshot format is changeable with a Terminal command if you capture often.

When exporting from design tools, ask two questions before saving: does this need transparency, and what size will it display at? If the answer to the first is no, export JPG. If the answer to the second is 800 pixels wide, export at 800 rather than 4000. Both decisions take a second at export time and save you the entire conversion exercise later. The general principle is that PNG should be a deliberate choice for graphics and transparency, not the default you reach for out of habit.

What size a PNG should actually be

A quick sanity check tells you whether a file is genuinely bloated or simply honest about its content. A flat logo or icon at a sensible size should be well under 50KB, and often under 10KB as PNG-8; anything larger means it was saved as PNG-24 or at an inflated resolution. A screenshot of an interface with flat colours and text compresses reasonably, often landing between 200KB and 800KB, which is fine for PNG.

A photograph, however, has no acceptable PNG size, because even a well-optimised one runs into megabytes. If your file is a photo and it is large, nothing is broken and no setting will rescue it. That is simply what lossless storage of photographic data costs, and it is the clearest possible signal to change format rather than keep optimising.

Frequently asked questions

Why is my PNG file so large?

Because PNG stores every pixel losslessly. Photographs have millions of unique colours with no repetition to compress, so the file stays near raw size.

How do I make a PNG smaller?

Convert it to JPG for photos, the biggest saving. A photographic PNG drops 60 to 90 percent as JPG. For graphics, use WebP, PNG-8, or resizing.

Is a PNG bigger than a JPG?

For photos, far bigger. The same photo is about ten times larger as PNG, because PNG keeps every pixel while JPG discards imperceptible detail.

Does resolution affect PNG size?

Yes, dramatically. Doubling the width and height quadruples the pixel count, so an oversized PNG is many times heavier than one at its real display size.

What is the difference between PNG-8 and PNG-24?

PNG-8 holds 256 colours; PNG-24 holds millions. A flat logo saved as PNG-24 wastes space, and switching to PNG-8 can halve it with no visible change.

Why are my screenshots such large PNGs?

Because operating systems save screenshots as PNG by default at full resolution. If the screen showed a photo, that is photographic content in a lossless format, the worst case.

Can I shrink a PNG without losing transparency?

Yes. Use WebP or reduce to PNG-8, both of which keep the alpha channel, unlike converting to JPG, which flattens transparency to a solid colour.

Do PNG optimizers actually help?

Modestly, and safely. They strip metadata and repack losslessly, saving 10 to 30 percent without changing a single pixel. Use one as a final pass.

Why doesn't a PNG optimizer shrink my photo much?

Because optimizers remove redundancy, not detail, and photos have almost none left. A 10 to 15 percent gain signals the format is wrong; convert to JPG instead.

Does my image actually still need transparency?

Often not. Many PNGs keep an alpha channel nobody uses, left over from an old workflow. If it sits on white now, convert to JPG with a white fill.

What file size should I aim for?

Roughly: under 200KB for a hero image, 100KB in-article, 30KB for a thumbnail. Upload forms state their own cap, commonly 100KB or 200KB.

How do I stop creating huge PNGs?

Choose the format deliberately. Windows 11's Snipping Tool can save JPG directly, and when exporting from design tools, pick JPG unless you genuinely need transparency, at the size it will actually display.

What size should a normal PNG be?

A flat logo under 50KB, an interface screenshot 200KB to 800KB. A photograph has no acceptable PNG size, since lossless storage of photo data always runs into megabytes.