You pick a PNG, hit upload, and get bounced straight back: "File too large." You resize the browser window, try again, same error. The form doesn't tell you how large is too large, or why a single screenshot somehow weighs more than ten photos from your phone. It's one of the most common — and most avoidable — upload errors on the web.
The good news is that PNG file size problems are almost always fixable in under a minute, once you understand why PNGs balloon in size in the first place. Unlike a blurry photo or a broken file, this isn't a mistake you made — it's how the format behaves by default, and there's a reliable fix for every version of the problem.
PNG files get large because the format is lossless and stores every pixel exactly, with no automatic compression the way JPEG has. To fix a "file too large" upload error, compress the PNG with a lossy PNG compressor, resize it to the dimensions it's actually displayed at, and strip embedded metadata. This typically cuts file size by 50-80% with no visible quality loss, and takes under a minute per image.
Why do PNG files get so large in the first place?
PNG is a lossless format. Every single pixel's exact color is preserved, with no data thrown away the way JPEG discards detail the eye won't notice. That's exactly why PNG is the right choice for screenshots, logos, and graphics with sharp edges or transparency — but it also means the file size grows with almost everything the image contains, rather than being tamed by the format itself:
- Full color depth by default. Most PNGs are saved as 24-bit truecolor, storing 16.7 million possible colors even when the image only uses a few dozen, like a logo or a UI screenshot.
- An alpha (transparency) channel. If the image has any transparency, an entire extra channel of data is stored alongside the color data, even for the fully opaque parts of the image.
- Resolution far above display size. Screenshots taken on high-DPI displays or phones are frequently saved at 2-4x the pixel dimensions they'll ever actually be shown at.
- Embedded metadata and color profiles. Editing software often bakes in ICC color profiles, EXIF data, or even a hidden thumbnail preview, none of which the viewer ever sees.
None of this is compressed away automatically the way it would be with a lossy format. A PNG only gets smaller if something — you, or a compressor — actively removes that extra data.
Why this error keeps happening
"File too large" isn't a random glitch — it's a deliberate limit set by the platform you're uploading to, and it exists for reasons that have nothing to do with how the image looks:
- Server and bandwidth limits. Forms, CMS platforms, and marketplaces cap upload size to control storage costs and keep pages loading quickly for every visitor, not just you.
- Email attachment ceilings. Most providers cap total attachment size around 25MB, and a handful of high-resolution PNGs can hit that limit fast.
- Strict per-image limits on listings and ads. Marketplaces, ad platforms, and app store assets often enforce limits well under 1-2MB per image, far stricter than a general web upload.
- Mobile data and page speed. Even where a platform allows a large PNG through, it will slow down every page that displays it, which is why some tools quietly re-compress or reject oversized files instead of accepting them as-is.
Step-by-step: fixing a "file too large" PNG error
- Check the platform's actual limit. Look for the stated max file size near the upload button or in the error message itself — this tells you exactly how far you need to shrink the file, rather than guessing.
- Confirm PNG is still the right format. If the image is a photograph with no transparency and no small text, it may not need to be a PNG at all — converting to JPEG or WebP can shrink it dramatically. If it has transparency, sharp text, or flat UI colors, stay with PNG.
- Run it through a lossy PNG compressor. This is the single biggest lever — a good compressor intelligently reduces the color palette while keeping edges and transparency intact, typically cutting size by 50-80%.
- Resize to the dimensions you'll actually display. If the image will show at 800px wide on a page, saving it at 3000px wide only adds dead weight. Resize down to roughly the largest size it will ever be shown at.
- Strip metadata and color profiles. Most compressors do this automatically, but if you're using basic editing software, check for a "remove metadata" or "for web" export option.
- If the platform demands an exact size cap, use a resizer built for that. When "under 500KB" isn't optional, a tool that targets an exact output size will adjust compression and dimensions automatically until it lands under the limit, rather than you guessing at settings.
- Compressing more than one image? Batch it. Uploading a gallery or product catalog one file at a time is slow — a bulk compressor applies the same fix to every file in a folder in one pass.
Common mistakes that trigger the error again
1. Resizing the display, not the file
Shrinking an image's width and height in a page's CSS or a document's layout doesn't change the underlying file — the browser still has to download the full original size. The dimensions have to be reduced in the actual image file to make any difference to upload size.
2. Assuming "lossless" means "can't be compressed"
PNG being lossless refers to how it stores pixel data, not whether the file can be made smaller. Lossy PNG compression tools reduce the color palette and strip unnecessary data while keeping the image visually intact — it's a different kind of compression than JPEG uses, but it works.
3. Converting every PNG to JPEG by default
JPEG can't preserve transparency at all, and it introduces blur and color bleeding around sharp edges and small text — exactly the content PNG is usually chosen for. Converting a logo or screenshot to JPEG to save space often trades one problem for a worse one.
4. Confusing MB with Mb, or misreading the actual limit
File size units are easy to misread under pressure — a platform capping uploads at "2MB" means 2 megabytes, not 2 megabits, and file managers sometimes round displayed sizes in ways that hide you're still over the limit by a small margin. Check the exact byte count if you're right on the edge.
5. Compressing files one at a time when there are many
If an upload error is happening across a whole folder of images — a product catalog, a gallery, a batch of screenshots — fixing them individually wastes time. A bulk compressor handles the whole folder in one pass instead.
Real-world size reductions
These are representative results from compressing common types of oversized PNGs using a standard lossy PNG compression pass:
Flat-color graphics — logos, icons, UI screenshots, diagrams — tend to compress the most dramatically, since most of their file weight comes from an oversized color palette they never actually use.
Causes of oversized PNGs and their fixes
Most "file too large" errors trace back to one of a handful of causes. Here's what's usually driving the size, and the fastest fix for each:
| Cause | Why it inflates size | Best fix | Typical savings | Quality risk |
|---|---|---|---|---|
| No compression applied | PNG stores every pixel exactly, with nothing discarded by default | Run through a lossy PNG compressor | 50–80% | Low |
| Oversized dimensions | Saved at a far higher resolution than it's ever displayed | Resize to actual display dimensions | 40–90% | None |
| Full 24-bit color palette | 16.7 million possible colors stored, even for simple graphics | Reduce to an 8-bit indexed palette | 50–70% | Low-medium |
| Unused alpha channel | Transparency data stored even on fully opaque images | Flatten or remove the alpha channel | 10–25% | None |
| Embedded metadata / profiles | ICC profiles, EXIF data, or hidden thumbnails baked into the file | Strip metadata on export | 1–10% | None |
| Wrong format for the content | A photograph saved as PNG instead of a compressed format | Convert to JPEG or WebP if no transparency is needed | 70–90% | Medium |
Free tools to fix this right now
Rebrixe's image tools run entirely in your browser. Nothing is uploaded to a server — compression happens locally, so you can preview the result and file size before you download, whether you've got one oversized PNG or an entire folder of them.