Why Is My Converted Image Larger Than the Original?
Last reviewed:
A larger result is often a predictable consequence of changing compression models—not a failed conversion. Diagnose the route, content, and requirements before trying to shrink it again.
Quick answer
The most common cause is converting an efficiently compressed lossy source, such as JPEG, into a lossless or uncompressed destination, such as PNG, TIFF, BMP, or TGA. The new file stores the decoded appearance differently; it does not recover original detail merely because it uses more bytes.
Start with the conversion direction
| Direction | Growth risk | Reason |
|---|---|---|
| JPEG → PNG | High for photos | Lossless PNG must represent detailed decoded pixels |
| JPEG → TIFF | High | High-fidelity interchange favors preservation over delivery size |
| PNG → BMP | High | Uncompressed bitmap output |
| PNG → TGA | High | Uncompressed RGBA output |
| PNG → JPEG | Often lower | Lossy photo-oriented encoding, but alpha must be flattened |
| JPEG/PNG → WebP or AVIF | Often lower, not guaranteed | Modern lossy encoding may be efficient at suitable settings |
| Already optimized source → any re-encode | Unpredictable | The source may already beat the new settings |
A five-minute diagnostic workflow
- Confirm dimensions. If width or height changed, this is not a format-only comparison.
- Confirm the true formats. Do not infer them from filenames alone.
- Classify source and output. Note lossy, lossless, palette, or uncompressed behavior.
- Identify content. A photograph, noisy scan, screenshot, and flat icon compress differently.
- Check special properties. Alpha, high bit depth, frames, and metadata can add data.
- Compare purpose. Decide whether the larger output provides a required feature or is simply the wrong delivery format.
Why lossless output can expand a lossy source
JPEG decoding produces pixels that include both intended image detail and artifacts from the earlier lossy encoding. PNG does not know which variation is “real”; it preserves the decoded values. Photographic texture and JPEG artifact patterns can be difficult for PNG’s lossless model to compress.
This explains a seemingly paradoxical result: a 3 MB JPEG can become a 12 MB PNG without becoming visually better. The PNG is a lossless record of the JPEG’s decoded result, not a recovery of the camera scene. See the dedicated PNG versus JPG size explanation.
Other causes of unexpected growth
The source was exceptionally optimized
A downloaded image may have been encoded with slow, specialized settings. A fast general converter can create a larger output even in a newer format. “Modern” does not guarantee smaller for every source.
The output keeps an alpha channel
Transparent graphics add another channel and often require lossless or alpha-aware storage. Removing alpha may reduce data, but only flatten it when the destination genuinely does not need transparency.
Noise and fine texture resist compression
Film grain, scanner noise, confetti, grass, and fabric make neighboring pixels less predictable. Lossless output grows; high-quality lossy output may also need more bytes to avoid visible damage.
The output encoding has a different goal
TIFF, BMP, and TGA often serve interchange, legacy, or production workflows rather than compact web delivery. Judge them by workflow fitness, not by a web-size contest.
Quality settings differ
Codec quality numbers do not share a universal scale. A quality of 80 in one encoder cannot be compared directly with 80 in another.
ForgeConvert-specific output behavior
ForgeConvert does not resize images during normal conversion, so output growth is usually an encoding consequence. PNG is lossless; TIFF uses lossless LZW; BMP output is uncompressed 24-bit; and TGA output is uncompressed 32-bit. JPEG and WebP use quality 82, while AVIF uses quality 60. These fixed policies prioritize predictable general use rather than guaranteeing the smallest possible result.
The maximum generated file is 64 MB. A conversion can therefore be valid in principle but rejected when a lossless or uncompressed destination expands beyond that boundary.
What should you do?
If the destination requires that format
Accept the larger derivative, then use a specialized optimization workflow if the receiving system permits it. Keep the source and verify that optimization does not remove required alpha, depth, or fidelity.
If the goal is web delivery
Test a format designed for that purpose, such as PNG to WebP for compatible delivery or TIFF to WebP for an access derivative. Compare appearance at final display size.
If the goal is editing or preservation
Do not sacrifice a suitable master merely to reduce bytes. Storage masters and delivery copies have different jobs.
If no feature was gained
Keep the original. Conversion is optional when it does not improve compatibility, workflow, transparency, or delivery.
Common mistakes
- Assuming larger means higher quality.
- Converting the larger output repeatedly instead of returning to the master.
- Reducing dimensions without checking the required display or print size.
- Flattening transparency solely to save bytes.
- Comparing file sizes while dimensions or frame counts differ.
- Expecting every WebP or AVIF to beat a carefully optimized source.
Frequently asked questions
Does a larger converted file have better quality?
Not necessarily. A lossless destination may store already decoded pixels less compactly without restoring detail lost in the source.
Why does JPG to PNG increase file size?
JPEG is designed to compress photographs lossily, while PNG preserves decoded pixel values losslessly. Detailed photo pixels are often expensive for PNG to store.
Should I convert the larger output again?
Return to the best source and create the required destination once. Repeated lossy conversions can add artifacts and may not solve the underlying format mismatch.