Pick the wrong side of RAW vs JPEG and you pay in one of two currencies: wasted kilobytes or broken compatibility. The spec table below settles the facts; the verdict sections tell you which way to lean for photos, graphics and the web.
Side by side
| Format | Compression | Transparency | Animation | Support (2026) |
|---|---|---|---|---|
| RAW | Uncompressed | No | No | Lightroom, Capture One and editing software — never browsers |
| JPEG | Lossy | No | No | every browser and device made in the last 25 years |
Two rows, but they hide the biggest practical gap: file size on real images, covered next.
File size on real images
For RAW, the working reality: 20-60 MB per shot on a modern mirrorless camera. For JPEG: a 12-megapixel photo lands around 3-4 MB at quality 85.
Averages mislead here — a logo and a sunset photo will rank these two formats in opposite order. Convert one of each and look at the readouts.
For pure web delivery, measure both against WebP before deciding: at over 96% of browsers in use in 2026 (caniuse), it often makes this whole debate academic.
Whichever way the kilobytes fall, remember they compound: a saving of 200 KB per image across a forty-image page is eight megabytes a visitor never downloads.
What each format can carry
RAW is uncompressed, strongest at professional photography, photo editing, maximum quality capture; its known costs are huge file sizes, requires processing software, not shareable directly.
JPEG is lossy, aimed at photographs, social media, web images; the trade-off there: lossy compression, no transparency, quality degrades on re-saving.
Notice the two cost lists barely overlap: that is why this pairing survives — each format covers the other's blind spot.
The verdict
Choose RAW when your job looks like professional photography, photo editing, maximum quality capture and the priority is maximum image data, full editing flexibility, highest quality.
Choose JPEG when you are in photographs, social media, web images territory and need small file size, universal support, great for photos.
When in doubt, run the same image through the RAW converter and the JPEG converter and let the size readouts vote.
Thirty seconds of compression theory
Uncompressed storage writes every pixel verbatim. Maximum fidelity and maximum disk usage travel together, which is why these files live in working pipelines and rarely on the public web.
Lossy compression throws away detail the eye is bad at noticing — fine texture, subtle color steps — and keeps what perception cares about. That is how a photo drops 80% of its weight while looking identical at arm's length; it is also why each re-save discards a little more.
Once you see the mechanism, every size difference in this article stops being magic and starts being arithmetic.
Four real scenarios
The photographer delivering a wedding gallery cares about quality first and upload time second — the format whose profile reads "maximum image data, full editing flexibility, highest quality" or "small file size, universal support, great for photos" closer to that wins the job.
The web developer chasing Core Web Vitals weighs file size above everything: between 20-60 MB per shot on a modern mirrorless camera and a 12-megapixel photo lands around 3-4 MB at quality 85, the smaller real-world output gets shipped.
The office user attaching a file for an unknown recipient optimizes for one thing — that it opens. Whichever of the two enjoys broader support is the safe envelope.
The print shop reverses every web instinct: resolution and lossless data outrank file size completely, because a 60 MB master is cheaper than a reprint.
Troubleshooting the usual suspects
Colors shifted. Usually a color-profile story: the source carried a wide-gamut profile and the viewer assumes sRGB. Convert from an sRGB master when the destination is the web, and the shift disappears.
The file will not open. Nine times out of ten the viewer is the limitation, not the file. Try a second viewer before blaming the conversion, or convert to JPEG — if that copy opens, the original was fine all along.
Transparent areas turned white. The target format has no alpha channel; flattening is the documented behaviour, not a bug. Re-convert to PNG or WebP if transparency must survive.
The file got bigger. Some content genuinely compresses worse in the new format — flat graphics in photo-oriented codecs, photos in graphics-oriented ones. The size readout before download is the early warning.
Two formats, two eras
RAW comes from 1998, built by camera manufacturers (CR2, NEF, ARW and others); JPEG from 1992, by the Joint Photographic Experts Group. Every difference in the table above traces back to what problems were worth solving in those two moments.
Age buys an ecosystem — viewers, converters, muscle memory. Youth buys compression. Pick which currency your project spends.
The Core Web Vitals angle
Images are usually the heaviest asset class on a page, so format choice flows straight into Largest Contentful Paint — the Core Web Vitals metric Google weighs for ranking. Lighter images, earlier paint, better scores: the chain is that direct.
Pair the format change with loading="lazy" on below-the-fold images and correct display dimensions, and the speed gain typically doubles.
Measure before and after with PageSpeed Insights — the image-weight line item makes the improvement concrete instead of theoretical.
Quick Answers
Which is smaller, RAW or JPEG?
Depends on the image. The anchors: for RAW, 20-60 MB per shot on a modern mirrorless camera; for JPEG, a 12-megapixel photo lands around 3-4 MB at quality 85. Photographs and flat graphics compress on opposite curves, so test one of your own files rather than trusting an average.
Can I convert between RAW and JPEG without quality loss?
Lossless-to-lossless conversions are perfect copies. The moment a lossy format is involved, some data is discarded — normally invisible at default settings, but keep your originals as the master copies.
Which should I send to a print shop?
Print workflows want lossless, high-resolution files — that points to formats like TIFF and PNG. Between these two, the one with JPEG's compression profile is the safer print choice.
Does it matter which one my camera or phone produces?
Devices choose for storage efficiency, not for your workflow. Whatever comes out of the device is just the starting point — keep it as the original and convert copies to fit each destination.
Can I batch convert a mixed folder of RAW and JPEG?
Yes — converters key on each file's actual type, not the folder. Drop the mixed set, pick one target format, and the output comes back uniform in a single ZIP.
Written by Giovanni Picaro, a web developer who has been building image tools and optimizing sites since 2019. Sources: MDN image format reference and Google web.dev. Last reviewed: 2026.