RAW vs JPG: Which Should Photographers Shoot In?
The Fundamental Difference Nobody Explains Clearly
When your camera captures a RAW file, it saves nearly everything the sensor saw. It's all the light data, across the entire dynamic range the hardware can muster. A JPG is what happens next. The camera takes that same data, makes its own decisions about sharpening, noise reduction, and color, and then permanently throws away 80–90% of the information to create a much smaller file. That last part is key: the process is irreversible. Let's put numbers on it. A RAW file from a 24-megapixel Sony a7 III is typically 24–28 MB. The equivalent JPG at the highest quality setting is only 8–12 MB. That size difference isn't just about storage; it's about information. A RAW file from a modern camera records 12 or 14 bits of data per channel, which translates to between 4,096 and 16,384 distinct brightness levels for each color. A JPG is always 8-bit. That gives you just 256 levels. That enormous gap is what you feel the moment you try to rescue a blown-out sky or pull detail from deep shadows. To add a little chaos to the mix, 'RAW' isn't one single format. Canon uses CR2 and CR3. Nikon has its NEF files. Sony uses ARW, and Fujifilm has RAF. Adobe even created DNG as an open alternative. They all behave a bit differently in editing software, and not every tool supports every flavor, which is a crucial part of building a reliable workflow.
Where RAW Gives You a Real Advantage
The real magic of RAW is its forgiveness. It's the power to recover detail from images that weren't perfectly exposed in-camera. In Lightroom Classic, you can often push an underexposed RAW file from a modern full-frame sensor by +3 or even +4 stops before the image falls apart. Try that with a JPG. You will hit a wall of noise and ugly color banding around +1.5 stops, if you're lucky. White balance is another decisive win for RAW. If you're shooting a wedding reception under a miserable mix of tungsten and LED lights on Auto white balance, the JPG locks in whatever guess the camera made. It's permanent. With the RAW file, you can slide the Kelvin temperature from a warm 3,200K to a cool 6,500K in post-production with absolutely zero quality loss. The color data was never baked in to begin with. This all comes down to having the full bit depth for targeted adjustments. Take a classic high-contrast landscape with a bright sky and dark foreground. A RAW file lets you drag the highlight slider down by 80 points and crank the shadow slider up by 70 without making the image look fake. The same move on a JPG results in visible banding in the sky's gradient and muddy, artifact-filled shadows. For portrait and commercial photographers delivering heavily retouched files, RAW is non-negotiable. Period. Fine-grained skin tone adjustments, precise color grading for brand standards, and any serious compositing work demand the full data set that only a RAW file can provide.
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. The truth is, modern camera JPG engines are genuinely excellent. Fujifilm's Film Simulations—like Classic Chrome, Velvia, and Eterna—are so beloved that many photographers shoot JPG just to use them straight out of the camera. On a Fujifilm X-T5, you can dial these in through Menu > Image Quality Setting > Film Simulation, and frankly, the results are often better than what most people could achieve fiddling with sliders in Lightroom. Then there's speed. For sports and news photographers firing off shots at 20 frames per second, the camera's buffer is everything. A Nikon Z9 shooting 14-bit lossless RAW will fill its buffer much faster than the same camera shooting high-quality JPGs. When the perfect shot exists in a 0.3-second window, buffer depth is the only thing that matters. Storage and transfer costs are also a very real factor. A sports photographer covering a three-hour game at 15 fps can easily generate 200–300 GB of RAW files in one session. JPGs would cut that down to a more manageable 60–80 GB. For photographers working in remote locations with slow satellite uplinks, or filing images directly from a chaotic press box, JPG isn't just a choice; it's often the only practical option. And if your images are destined for social media, remember this: Instagram is going to recompress your photo to its own specifications anyway. The subtle quality difference between a well-exposed JPG and a meticulously processed RAW file will be completely invisible to your audience.
The RAW+JPG Compromise and Its Trade-offs
Most cameras let you have it both ways, recording both formats at the same time. On a Canon R5, you can find this under Menu > Shoot 1 > Image Quality. Just set the primary card slot to RAW and the secondary CFexpress card to Large Fine JPG. This setup promises the best of both worlds: the flexibility of RAW for key shots and an immediately shareable JPG for everything else. The most obvious downside is storage. You're now writing two files for every single photo. On that Canon, that's roughly 45 MB of RAW plus 10 MB of JPG, totaling 55 MB per shutter press. A 256 GB card that holds about 5,700 RAW files will now only hold around 4,650 RAW+JPG pairs. It's not a catastrophic loss, but it absolutely adds up over a long day of shooting. But the real cost isn't storage, it's sanity. Anyone who has stared at a folder with 6,000 files from a 3,000-shot event knows the special kind of dread this can inspire. Culling becomes a nightmare of duplicates. You must decide upfront which version you're working from, or you'll end up with a chaotic mess of half-edited RAWs and final-looking JPGs. The most practical way to manage this is to tell your software to ignore one of the formats on import. In Lightroom Classic, you can find this setting under Preferences > General. Make sure 'Treat JPG files next to raw files as separate photos' is unchecked. This way, you'll only see the RAW files in your catalog, keeping the JPGs neatly hidden on your drive but available if you need them.
Converting Between RAW and JPG: What's Actually Possible
Converting a RAW file to a JPG is a standard part of every photographer's workflow. It's how you deliver files to clients, upload them to the web, or send them for printing. Every major tool, from Lightroom's Export dialog to Capture One's Export Recipes and Canon's Digital Photo Professional, handles this cleanly. You pick your JPG quality (a setting of 80–95 on a 0–100 scale is a great balance of size and quality), choose a color space (sRGB for web, Adobe RGB for print), and hit export. But what about going the other way? Converting a JPG to a RAW file is, in any meaningful sense, impossible. Tools that claim to do this are just wrapping your existing JPG inside a RAW file container. You don't gain back any of the lost data. The underlying 8-bit, heavily compressed information doesn't magically regain its dynamic range or bit depth. You simply cannot reconstruct information that was permanently discarded when the JPG was created. For straightforward batch conversions from RAW to JPG without firing up a full editing suite, an online tool like CocoConvert is a solid choice. Let's be clear about what this means: you upload your RAW file, and our service applies a standard, neutral rendering to create a clean JPG. You don't get the granular control over tone curves or color grading that you would in Lightroom. But if you have 200 product photos that were shot correctly and just need to become JPGs for a client portal, this is a fast and efficient solution. For precise, artistic deliverables, you'll still want a dedicated editing application. CocoConvert supports all the common RAW formats, including CR2, CR3, NEF, ARW, and DNG. However, it might struggle with files from older or more obscure cameras. We believe in being transparent about that so you don't hit a wall five minutes before a deadline.
Which Format Actually Suits Your Work?
So, which format is right for you? It boils down to how you work, what you shoot, and where your images end up. If you're a landscape or portrait photographer, shoot in challenging light, and spend any amount of time in Lightroom perfecting each image for clients or prints—shoot RAW. No question. The editing latitude alone justifies the storage. That single recovered highlight in a wedding dress or salvaged sunset that would have been a white blob in a JPG is worth all the extra gigabytes. If you're a street photographer, event shooter, or photojournalist who values speed, shoots in decent light, and needs to publish quickly—JPG is a perfectly legitimate professional choice. Henri Cartier-Bresson didn't have RAW, after all. The decisive moment doesn't wait for your camera's buffer to clear. If you shoot a mix of events, travel, or documentary work where you can't predict the light but are also delivering hundreds of images, RAW+JPG is worth the extra storage. Use the JPGs for fast culling and client previews, and dive into the RAWs only for the shots that need serious work. My advice for beginners is simple: shoot RAW. It's a safety net while you're still learning the nuances of exposure and color. More importantly, it forces you to learn what post-processing can and cannot do for an image. Once you're consistently nailing your shots in-camera, you can make an informed decision about whether JPG suits your workflow better. Don't let format dogma dictate your art. Let your work dictate the format. Both RAW and JPG are just tools, and understanding their strengths is how you choose the right one for the job.
Storage, Backup, and Long-Term Archiving Considerations
Regardless of format, you need a solid backup strategy. The classic 3-2-1 rule—three total copies of your data, on two different types of media, with one copy stored offsite—is the gold standard. RAW files don't change the rule, but they do make the storage math a lot more significant. A working photographer shooting 50,000 images a year in RAW can easily generate 1–1.5 TB of data annually, and that's before counting any edited exports. At today's prices, a 4 TB external drive for local backup costs around $80–100, while cloud storage for that volume is $10–20 per month. Over five years, that's a real business expense you need to factor into your pricing. The real long-term question for RAW files is format longevity. Proprietary formats like Canon's CR2 or Nikon's NEF rely on manufacturers to keep supporting them. Will your 20-year-old NEF files open in 2045? Maybe. This is the exact problem Adobe's DNG (Digital Negative) format was created to solve. It's an open, archival standard that any software can implement. Many photographers use Lightroom's built-in converter (File > Convert Photos to DNG) to create DNGs for long-term storage, which also happen to be 15–20% smaller. JPG, on the other hand, has been a universal standard since 1992. It's not going anywhere. It will almost certainly be readable by any software for decades to come. For this reason, many photographers use a belt-and-suspenders approach: archive the final, edited JPGs alongside the original RAW files. The JPGs give you instant access, while the RAWs are your insurance policy in case you ever want to re-process an image with new tools or a fresh creative vision.