Why Is My PNG So Large? 3 Easy Fixes

Your PNG is 8 MB because PNG stores every pixel exactly, and a full page screenshot at retina resolution genuinely contains that much information. The format discards nothing, which is the whole point of PNG and also the whole problem.

There are 3 ways to fix it, and each one costs you something different. Reducing dimensions costs resolution you probably were not using. Reducing colour depth costs colour accuracy on photographs. Changing format costs compatibility outside browsers. Pick by what the image is for.

Your 3 options

• Reduce the dimensions. Free, and usually the biggest win. Nobody needs a 5000 pixel screenshot.
• Reduce the colour depth. Works well on flat graphics, badly on photographs.
• Change format. WebP keeps transparency and typically lands 25 to 35 percent smaller.

Why PNG files grow so quickly

PNG file size scales directly with pixel count, because every pixel must be described exactly. Doubling the width and height quadruples the number of pixels and roughly quadruples the file.

A 5120 by 2880 screenshot from a high resolution monitor contains 14.7 million pixels. At 3 bytes per pixel before compression that is 44 MB of raw data, and PNG compression typically reduces it to somewhere between 4 MB and 12 MB depending on how much flat colour the image contains. An 8 MB result is normal rather than a fault.

Fix 1: reduce the dimensions

Resize the image to the largest size it will ever display, which removes most of the file weight before anything else is tried. This is the fix with the highest effect and the lowest cost.

Measure the widest the image will ever render on the page, double that for high density screens, and resize to the result. A screenshot displayed 800 pixels wide needs 1600 pixels and nothing more.

Fix 2: reduce the colour depth

Converting from 24 bit colour to an 8 bit palette cuts a PNG by 50 to 70 percent, and works only on images with limited colours. Screenshots of interfaces, diagrams, logos and charts are ideal candidates.

The technique stores a palette of up to 256 colours and references it per pixel, rather than storing full colour values. A user interface screenshot rarely contains more than 256 distinct colours, so the reduction is invisible. A photograph contains tens of thousands, so the same reduction produces visible banding across skies and skin.

Fix 3: change the format

Convert to WebP for web use, which keeps transparency and typically lands 25 to 35 percent smaller than PNG. Convert to JPG only when the image is photographic and needs no transparency.

• WebP lossless for graphics and screenshots, which keeps every pixel exact and still saves 20 to 30 percent.
• WebP lossy for photographic PNG files, where the saving reaches 70 percent or more.
• JPG for photographs with no transparency, where PNG was the wrong choice from the start.
• AVIF for large photographic images, which compresses harder still on files over 100 KB.
• Vector graphics for logos and icons, where an SVG file may weigh a fraction of any raster format.

The most common cause: a photo saved as PNG

A photograph saved as PNG is 3 to 5 times larger than the same photograph as JPEG, with no visible difference. This single mistake accounts for most oversized PNG files.

PNG compression looks for repetition, and photographs contain almost none at the pixel level, since every pixel differs slightly from its neighbour. The format ends up storing millions of near unique values exactly. Save photographs as JPEG or WebP and reserve PNG for images that genuinely have flat colour or transparency.

How to shrink a PNG without losing quality

To reduce a PNG while keeping it lossless, follow these 5 steps in order.

1. Crop away any unused area, since empty margins still cost file size.
2. Resize to the largest display size the image will ever need, doubled for high density screens.
3. Check whether the image actually needs transparency, since a flattened image compresses better.
4. Reduce the colour palette if the image is a graphic rather than a photograph.
5. Convert to WebP lossless, which is still exact and typically 20 to 30 percent smaller.

Steps 1 and 2 usually solve the problem alone. The remaining steps matter when an image must stay very large, such as a full page screenshot in documentation.

Why screenshots are so big on modern screens

High density displays capture at 2 or 3 times the logical resolution, so a screenshot of a window 1200 pixels wide is saved at 2400 or 3600 pixels. The file is far larger than the window appeared to be.

That extra resolution is useful when the screenshot will be viewed on another high density screen and wasted otherwise. For documentation and support articles, resizing back to the logical size halves the dimensions and cuts the file by about 75 percent while looking identical to most readers.

When to keep the PNG large

Keep the full size PNG when the image is a master file, a print asset or a source that will be edited later. Compression decisions belong to delivery copies rather than to originals.

Design files, logo masters, print artwork and scanned documents all justify their size. Store those at full resolution and generate smaller copies for each destination. The mistake is publishing the master rather than keeping it, since a master costs disk space once while a published master costs bandwidth on every visit.

Transparency costs more than people expect

A transparency channel adds a fourth value to every pixel, increasing the raw data by about 33 percent before compression. Many PNG files carry that channel without using it.

Screenshots, exported charts and images flattened onto a white background frequently keep an alpha channel that is fully opaque everywhere. Removing it costs nothing visually and reduces the file measurably. Check whether the image genuinely needs a transparent background before assuming the channel is required, since most images placed on a white page do not.

Does compressing a PNG lose quality

Lossless PNG optimisation loses nothing, while reducing colours or dimensions changes the image permanently. The 3 techniques are frequently described together and are not equivalent.

Lossless optimisation reorganises how the file stores its data and typically saves 5 to 20 percent with pixel identical output. Palette reduction and resizing alter the image itself, which is acceptable for delivery copies and unacceptable for masters. Keep the original whenever the reduction is not reversible.

Fixing a whole folder of oversized PNG files

Process the folder in one batch, since oversized PNG files usually arrive in groups from the same source. A documentation set, a screenshot library or an export from a design tool tends to share the same problem throughout.

Drop up to 500 files in at once, or drag a ZIP archive straight in, and set the dimensions and format once for the whole set. Everything runs inside your browser on your own processor, so internal screenshots, product designs and client documentation never reach a server. Nothing is uploaded, so there is no retention policy to read and nothing left behind afterwards.

Fix the source of the problem as well as the files. A screen capture tool set to save PNG at full retina resolution will keep producing 8 MB files indefinitely. Most capture tools allow a default format and a scale factor, and changing both once removes the need to process screenshots again after every support article.