RAW vs JPG: Which Should Photographers Shoot In?
The Fundamental Difference Nobody Explains Clearly
When your camera captures a RAW file, it writes virtually everything the sensor recorded — all the light data across the full dynamic range the hardware can achieve. A JPG, by contrast, is the camera's own processed, compressed interpretation of that same data. The camera applies sharpening, noise reduction, a color profile, and then throws away roughly 80–90% of the original data to shrink the file down. That process is irreversible. To put numbers on it: a RAW file from a 24-megapixel Sony a7 III typically runs 24–28 MB per image. The equivalent JPG at the highest quality setting lands around 8–12 MB. That size difference isn't just storage — it represents actual tonal information. A RAW file from most modern cameras records 12 or 14 bits of data per channel, meaning it can describe between 4,096 and 16,384 distinct brightness values per color channel. A JPG is always 8-bit, giving you 256 values per channel. That gap matters enormously the moment you try to recover a blown-out sky or lift shadows in post-processing. The other thing worth understanding is that 'RAW' is not a single format. Canon uses CR2 and CR3. Nikon uses NEF. Sony uses ARW. Fujifilm uses RAF. Adobe created DNG as an open alternative. Each behaves slightly differently in editing software, and not every tool supports every variant — something to keep in mind when you're choosing a workflow.
Where RAW Gives You a Real Advantage
The clearest argument for RAW is exposure latitude — the ability to recover detail from images that weren't perfectly exposed in-camera. In Lightroom Classic, an underexposed RAW file from a modern full-frame sensor can often be pushed +3 to +4 stops in the Exposure slider before the image becomes unusable. Try that with a JPG and you'll hit a wall of noise and banding at around +1.5 stops, if you're lucky. White balance is another area where RAW wins decisively. If you shoot a wedding reception under mixed tungsten and LED lighting and set your white balance to Auto, the JPG locks in whatever the camera decided. With a RAW file, you can slide the Kelvin temperature from 3,200K to 6,500K in post with zero quality loss, because the color data was never baked in. RAW also gives you access to the full bit depth when making targeted adjustments. If you're photographing a landscape with a bright sky and dark foreground — a classic high-contrast scene — a RAW file lets you pull down the highlights by 80–100 points and push the shadows up by 60–70 points in Lightroom without the image looking processed. The same move on a JPG produces visible banding in gradients and muddy, artifact-ridden shadows. For portrait and commercial photographers who deliver heavily retouched files, RAW is essentially non-negotiable. Skin tone grading, color grading for brand consistency, and any significant compositing work all benefit from having the full data set to start from.
The Honest Case for Shooting JPG
JPG gets dismissed too quickly by photographers who've never had to deliver 1,500 wedding images by Monday morning. Modern camera JPG engines are genuinely good. Fujifilm's Film Simulations — Classic Chrome, Velvia, Eterna — are so well-regarded that many photographers shoot JPG specifically to use them straight out of camera. The Fujifilm X-T5, for example, lets you assign Film Simulations through Menu > Image Quality Setting > Film Simulation, and the results are often better than what most photographers would achieve manually in Lightroom. Speed is a concrete, practical advantage. Sports and news photographers shooting at 20 frames per second need a camera buffer that can keep up. A Nikon Z9 shooting 14-bit lossless RAW fills its buffer far faster than the same camera shooting Fine JPG. When the decisive moment is a 0.3-second window, buffer depth matters. Storage and transfer costs are real too. A sports photographer shooting a three-hour game at 15 fps in RAW can generate 200–300 GB in a single session. JPG cuts that to 60–80 GB. For photographers working in remote locations with satellite uplinks, or filing images directly from press boxes, JPG is often the only practical option. If your images are destined primarily for social media — where Instagram recompresses everything to its own spec anyway — the quality difference between a well-exposed JPG and a RAW file processed in Lightroom is essentially invisible to your audience.
The RAW+JPG Compromise and Its Trade-offs
Most cameras let you record both formats simultaneously. On a Canon R5, you find this under Menu > Shoot 1 > Image Quality, where you can set the primary slot to RAW and the secondary CFexpress card to Large Fine JPG. This gives you the flexibility of RAW for images worth editing and an immediately shareable JPG for everything else. The obvious downside is storage. You're now writing two files per frame — roughly 45 MB of RAW plus 10 MB of JPG on that Canon body, so around 55 MB per shutter press. A 256 GB card that holds roughly 5,700 RAW files now holds around 4,650 RAW+JPG pairs. Not a catastrophic difference, but it adds up across a full shoot. There's also a workflow clarity problem. Culling 3,000 images when you have 6,000 files on your drive — two versions of everything — creates organizational friction. You need to decide upfront whether you're working from RAW or JPG, otherwise you end up with a chaotic mess of duplicates at different stages of processing. For photographers who use this approach, the most practical method is to import only one format into your DAM (Digital Asset Management) software. In Lightroom Classic, go to Preferences > General > Treat JPG files next to raw files as separate photos — leave this unchecked if you only want to see the RAW files in your catalog, with the JPGs available as sidecar files on disk when needed.
Converting Between RAW and JPG: What's Actually Possible
Converting a RAW file to JPG is straightforward and something you'll do at the end of almost every editing session — it's how you deliver files to clients, upload to stock agencies, or send images for print. Lightroom's Export dialog, Capture One's Export Recipes, and even camera manufacturer software like Canon's Digital Photo Professional all handle this cleanly. You choose your JPG quality (typically 80–95 on a 0–100 scale for a good balance of size and quality), set your color space (sRGB for web, Adobe RGB for print), and export. Going the other direction — converting a JPG to RAW — is not really possible in any meaningful sense. Tools that claim to do this are essentially wrapping your JPG inside a RAW container. The underlying 8-bit, compressed data doesn't gain any additional latitude or bit depth. You cannot reconstruct information that was discarded at the moment of capture. For straightforward RAW-to-JPG batch conversion without needing a full editing suite installed, an online tool like CocoConvert handles the conversion reliably. It's worth being direct about what that means: you upload your RAW file, and CocoConvert applies a neutral rendering to produce a JPG. You won't get the same control over tone curves, color grading, or noise reduction that you'd have in Lightroom or Capture One. If you have 200 product photos that were shot correctly in-camera and you just need clean JPGs for a client portal, that's a perfectly reasonable use case. If you need precise color-graded deliverables, you'll want a dedicated editing application. CocoConvert supports common RAW formats including CR2, CR3, NEF, ARW, and DNG. Less common formats from older or niche cameras may not convert correctly, and we'd rather tell you that upfront than have you discover it mid-deadline.
Which Format Actually Suits Your Work?
The answer depends on three things: how much post-processing you actually do, how critical image quality is to your end use, and what your delivery timeline looks like. If you're a landscape or portrait photographer who spends time in Lightroom on every image, shoots in challenging or unpredictable light, and delivers high-resolution files to clients or prints — shoot RAW. The editing latitude alone justifies the storage cost. A single recovered highlight in a bride's dress or a salvaged sunset that would have been blown out in JPG is worth the extra gigabytes. If you're a street photographer or photojournalist who shoots in good light, values speed, and publishes quickly — JPG is a legitimate professional choice. Henri Cartier-Bresson didn't have RAW. The decisive moment doesn't wait for your buffer to clear. If you shoot events, travel, or documentary work where you can't always predict the lighting but you're also delivering hundreds of images — RAW+JPG is worth the storage overhead. Use the JPGs for quick selects and client previews, the RAWs for any image that needs real work. For beginners still learning exposure and color, there's a strong argument for RAW: it gives you a safety net while you develop your eye, and it teaches you what post-processing actually does to an image. Once you're consistently nailing exposure in-camera, you can reassess whether JPG serves your workflow better. The format you shoot in should serve your photography, not the other way around. Both RAW and JPG are tools with specific strengths — understanding those strengths is what lets you make the right call for each situation.
Storage, Backup, and Long-Term Archiving Considerations
Whichever format you shoot, you need a backup strategy that accounts for file size and format longevity. The 3-2-1 rule — three copies, on two different media types, with one offsite — applies regardless of format, but RAW files make the storage math more significant. A working photographer shooting 50,000 images per year in RAW generates roughly 1–1.5 TB of raw capture data annually, not counting processed exports. At current prices, a 4 TB external drive for local backup runs about $80–100, and cloud storage for that volume costs $10–20 per month depending on the service. Over five years, that's a meaningful ongoing cost to factor into your business pricing. Format longevity is a legitimate concern for RAW files. Proprietary formats like CR2 or NEF depend on manufacturers continuing to support them in software. Adobe's DNG format was created specifically to address this — it's an open standard that any software can implement. Many photographers convert their proprietary RAW files to DNG for archiving, using Lightroom's built-in DNG converter (File > Convert Photos to DNG) or Adobe's standalone DNG Converter application. DNG files are typically 15–20% smaller than their proprietary equivalents, which is a secondary benefit. JPG, being a universal standard since 1992, will almost certainly remain readable by any software for the foreseeable future. For photographers who don't plan to revisit their archives for significant re-editing, archiving final-processed JPGs alongside RAW originals is a sensible belt-and-suspenders approach. The JPGs remain instantly accessible; the RAWs are there if you ever need to re-process with better tools or different creative intent.