Why you should take photos in RAW
An easy-to-understand infographic to why you should take your photos in raw
You can say a lot about whether you should be shooting in JPG or TIFF or RAW, but ultimately, for most photographers, the argument is very simple indeed:

Why are Negative destructive actions so bad?
When you apply, for example, white balance to an image in-camera, you do it to the exclusion of other white balances: Once it is applied, all the data that wasn't used to apply that particular white balance is discarded before it is ever written to a file. All the 'destructive' actions are like that, discarding image data every step of the way. Once a destructive action is completed, you cannot undo the actions.
If you do try to correct them (say, your camera wrote an image with a color cast to the memory card), you will incur even further data loss when you attempt to fix the problem.
Think of 'negative destructive' actions as one-way streets: Once you've gone down it, there's no going back.
How is editing in RAW different?
When you are editing RAW files, you never 'lose' the original data, and it is possible to change your white balance, sharpness, saturation, etc after the fact. If you change your mind, the original data is still there, and you can do so without degrading your image.
To coninue the analogy of above: Non-destructive editing on RAW files is more like a two-way street. If you get half-way down the road and discover that it takes you in the wrong direction, you can spin your car around, go back, and try another path.
If you're still not quite convinced, this article on froknowsphoto.com has some excellent side-by-side comparisons of post production flexibility on editing JPEG vs RAW files.
Does that mean you should never shoot in JPEG?
I've discussed this question in more detail in my article Can photos taken in JPG be as good as photos taken in RAW.
About this article
This is version 2 of the above graphic. The original is available here. Version 2 was updated with input from Reddit user jannne - thanks to Petapixel for pointing me towards the update!
Do you enjoy a smattering of random photography links? Well, squire, I welcome thee to join me on Twitter - Follow @Photocritic
© Kamps Consulting Ltd. This article is licenced for use on Pixiq only. Please do not reproduce wholly or in part without a license. More info.
Keep track of your camera with CameraTrace
The most photogenic festivals in the world
Red eyes and how to avoid them
A love story
Nikon PB4 Bellows Reborn
Worlds Fastest Camera
Photojojo iPhone Telephoto Lens review — AudioCast
Photo Accessories that Fail Security Checks
My week with Q
Studio equipment buying guide for beginners
VSCO Film Studio Review
The wild blue yonder of straight horizons
Photo Tips
Shoot with Love
Photographing Children in the wedding party
One Man Show: My 25 Years With Digital Photography
Sheer Heaven: Valentine Day Photo Techniques
How to Use Multiple Lights for Dramatic Portraits
Making your own flash diffuser
Software Review: Tiffen Dfx 3.0 Suite
LR4 free presets: Faded series
A gift of flowers: unfold your senses
On Set of "Love & Robots" the Film
My Night with Ilford Galerie Gold Silk Fibre
FOTOMOTO - Why I Left











25 Wedding Photos That Break the Mould
Silhouettes & Photo Contests
Cyan, not just another color
Our 26 best photo projects of 2011
Family Ties That Bind
Animal Group Portraits
Gallery: Embedded with the Territorial Army
10 case studies in exposure for outdoor photography
How to photograph Lord of the Rings landscapes
Interview with Vincent Laforet — Photo Journalist, Commercial Photographer, & Film Maker
Interview with Photographer Martin Evening - Photographer and Photoshop Author
A Brief History Of Light & Photography: Part 3 of 3
A Brief History Of Light & Photography: Part 2 Of 3
Decades of Evolving Personal Imagery in Photography
Lightroom Interview: Kevin Tieskoetter
Easy technique to select, edit and sequence keywords for web
How much should you charge for a photograph?

































Comments
Terrific! You have made it so easy now for me to explain to people why they should shoot in RAW. I talk till I'm blue in the face and they still don't get it. Now I'll send them the link to this article.
But are you really recording all the data your camera captures? Don't many cameras have other sensors, like photo cells, which it uses in doing all those adjustments, in addition to other info such as the flash speed and brightness and exact focus.
Yes, and the in-camera JPG processor applies those scene exposure measurements once and for all and tosses 90% of the image data it does not use to make the lossy JPG.
The Raw file, conversely, just saves the scene exposure measurement data in the Raw file right beside the Raw sensor pixel data so it all can be interpreted or overridden later at your control, whenever the photographer develops the Raw file, over and over, differently.
We can even develop a Raw file at +2, 0, and -2 exposure, then combine the three TIF results in an HDR high dynamic range version of the file that will blow the JPG away!
Cool or what?
I had no idea you could get HDR from RAW. I am shooting in RAW and have just entered a couple of my HDR works in a gallery show. I use Photomatix but I'm interested in using your suggestion. Is there a tutorial or a website? I don't want to bother you to explain it.
Thanks.
To use one Raw image file for HDRI High Dynamic Range Imaging or an "exposure stacking" combination of different exposures of the same image, simply convert that one Raw image file differently two or more times to TIF or PSD (or JPG if that's all your blending software can handle).
With each Raw conversion, simply adjust the exposure setting differently each time when "developing" the Raw image file so you have at least one dark conversion (showing highlights with no blown-out detail) and one light conversion (showing shadows with no blocked up detail), I usually include a "regular" exposure (showing mid tones well).
My Raw developing software allows + / - 2 to 4 "stops" of exposure compensation on-screen before saving a copy as TIF or PSD (or whatever file format you like), simply save a version at each step in the available exposure range from your Raw development software.
Save each file as, say:
pict3245-01.tif
pict3245-02.tif
pict3245-03.tif
... or whatever series makes sense to you, then import the series into your HDRI software and have at it, blending them to your desire.
Tutorial?
http://www.lmgtfy.com/?q=raw+exposure+stacking+hdri
Heck, everything in photographic storytelling is based on personal exploration and experience built from there.
There are no rules -- figure it out your own way to make your own self happy with your own art.
Then tell us where you share your photos!
Click!
Love and hugs,
Peter Blaise
White balance is still applied to a RAW file, my understanding is this is not a destructive process in RAW however and altering RAW after the fact in post processing of RAW files is non-destructive.
This makes the chart a little misleading since RAW based white balance is applied before the RAW is written but isn't destructive.
Nope, white balance is recorded beside the sensor data and is only applied later, whimsically, when software is used to "develop" a Raw file, different depending on the software or on the photographer's choices whenever after capture.
Manufacturer Raw developers tend to use a white balance calculation that corresponds to their in-camera JPG, and 3rd party Raw developers tend to develop using an "as shot" white balance or seek out a neutral white balance.
Regardless, white balance is set of additional numbers in a separate field in the Raw file that is NOT applied to the per-pixel data before saving in camera, and the photographer can tweak white balance any way they want to, differently over and over each time they develop a Raw file as many times as they want to in the future, as they see fit as time rolls on whenever they revisit the original Raw image file.
White balance is not applied to a RAW file.
The RAW file consists roughly of 2 parts: the raw sensor data and the camera settings/metadata.
The camera stores which white balance it would have applied to the jpg in the metadata. Lightroom or other converters use this white balance settings or do their own white balance.
Furthermore, there's a preview jpg image in the metadata of the RAW file, this is the one you see on the display, which has all camera processing stuff applied to.
There are some pretty obvious flaws here, Haje. First up is that the user sets the colour, saturation, contrast, and often the white balance. And believe it or not sometimes they set the camera to take the correct exposure. Imagine that. That means that the shot, with its data loss, will print perfectly... Wow.
When it comes to high volume shooting like festivals, fashion shows and sports games, it's JPEG all the way. Raw is a liability with camera framerate and buffer size at these things, not to mention the sheer volume of flash media required.
For low volume stuff, yep Raw is absolutely the king... but it's horses for courses.
I suppose it all depends on your shooting style. Personally - even at gigs and fashion stuff - my camera never leaves RAW.
So you're happy to shoot 1200 shots at a fashion show in Raw, even though the buffer keeps running out? Fashion 'stuff' is a lot broader than just shows, and I do shoot lookbooks, porfolios, etc., in Raw.
While I do shoot Raw in studio, it's ironic that Chris Grey, who literally wrote the book on modern lighting, says that in studio, when you meter and white balance correctly, there's no reason to not shoot Jpeg. You've total control over the exposure.
Over the Arts Festival here, I shot 10,000 photos. And that was with restraint. I really couldn't afford to have shot in Raw, I simply wouldn't have enough cards or space. (Not everything was in Jpeg, but most things were). Maybe when we've 10 or 20 TB drives, it may become more feasible, and when camera buffer speeds increase.
What kind of antique camera do you shoot with that runs the buffer out when shooting the Raw sequence of your choosing, when high resolution 10-frames-per-second-Raw cameras with enormous buffers are available for $800 nowadays?
Oh, nevermind -- we all have the tools we have, and we are either sere to our tools, or they serve us.
As you say, if you are happy with your camera's JPG images, go for it.
But, if you are happy with JPG, what are you doing on a Raw discussion thread, eh what?
Hungry for more after all?
A 5DII, which last time I looked was still a current camera and cost a lot more than $800. I also use a 7D as a spare, which again is a current camera.
You obviously didn't bother your ass reading my post properly, or you'd have seen seen that I usually shoot Raw, but shoot JPEG for specifically mentioned tasks. Ironically Haje has published a post about when it shooting JPEG might be appropriate.
No problem.
But current $800 high-resolution (16mp APS) cameras do capture Raw at 10 frames per second, up to, well, depending on the storage card design, up to, oh, about 20 frames (geese, only 2 seconds?!?) -- how many Raw frames do you need in immediate sequence?
Of course anyone who's happy with JPG can just go right on being happy -- please, don't even think about Raw.
And, of course, being happy with JPG does not diminish Raw one bit (so to speak).
But, deciding to capture in JPG ONLY because of camera Raw speed limitations or camera Raw responsiveness limitations or only because of storage limitations is more a comment on gear design than it is a comment on the content of JPG images versus the content of Raw images in and of themselves.
I think you're really talkin' about camera responsiveness and storage requirements, not the qualities of JPG versus Raw -- except as implemented in some camera software processors and memory cards, and then again, you're talkin' about camera responsiveness or storage space (and affordability?).
Heck, speed wise, and storage wise, let's change the subject to talk about even smaller resolution JPGs as being even faster and smaller than higher resolution JPGs, so why not capture 3 mp images in our 12+ mp cameras -- 3 mp JPGs are even faster and smaller, and that's all that matters ... IF you're talking about camera speed and responsiveness and storage limitations.
And if you're happy with 3 mp images.
Go for it.
Perhaps we're talkin' past each other.
I'm not arguing with you, I'm identifying where we agree -- JPGs are implemented in your cameras as a speedier, smaller, and lengthier sequence than your cameras can capture when shooting Raw.
And I fully understand 10,000 Raw 12+ bit uncompressed image storage requirements versus 10,000 same-resolution JPG 8 bit compressed storage requirements -- but your assignments sound like photo consumption, not photo conservation, and JPGs sound right on to hit that target.
Again, not a lot to do with Raw, but a lot to do with camera and storage design and costs -- you even suggest as much in suggesting that 10 to 20 TB drives would probably obviate some of the Raw challenge compared to JPG, at least storage wise.
Your "current cameras" that cost a lot more than "$800":
-- 2008 (3 year old) Canon EOS-5DII ~$3,600 can Raw capture ~4 frames per second for ~13 frames,
-- 2009 (2 year old) Canon EOS-7D ~$2,000 can Raw capture ~8 frames per second for ... how long? You tell us.
I'm just noting that other newer, cheaper cameras ... oh, you get it by now.
Click!
Love and hugs,
Peter Blaise
When the model is walking down the runway, yes, you do need rapid fire for a long time.
When the singer takes a running dive into the audience, yes, you need the buffer for that.
As for the rest Peter, it looks awfully like trolling or pedantry and for that I bow to you and bow out.
Okay, quick search, and I find that some discussion threads claim that their Canon EOS-7D can capture a Raw sequence up to ~17 shots at 8 frames per second or less (depending on automatic settings and card speed).
Sean, you gotta know that your 2 to 3 year old cameras have been bested at least in Raw rapid fire, continuous sequence, and price -- it's bound to happen, and probably always will.
Hey, my 7 to 8 year old cameras measure their Raw burst in seconds per shot, not shots per second! ;-) (But I format my storage card as FAT12 and take advantage of Lexar Wa Write Acceleration, and update my cameras BIOS, so I get more than twice the original performance promised with by my cameras, so I'm happy for now.)
You've identified speed in-camera, sequence length, and storage consumption as criteria for you, and yes, JPG is comparatively terrific for that, and probably always will be.
Alternatives are movie cameras with stills pull-out capability, but the topic was Raw versus JPG, probably Raw versus JPG for stills shooters -- you almost sound like a movie shooter!
Storage wise, what have we got, 128 GB flash cards now - I have portable computers smaller than that!
I wish someone would just slap a PC-controlled 1 TB 2.5" drive into a tripod-threaded "battery / vertical control grip" with it's own 5v power, and call it a day.
On-topic discussion wise, I sometimes crop viciously and then need to enlarge to compensate, and have seen the 4x4 blocks in JPGs reveal themselves where Raw does not. Otherwise, even lowly free Picasa and an amazing inexpensive Epson 13" wide special come-on price printer schmoozes JPGs and Raw alike into knock-out images same same. I have tried to revisit and tweak some ancient JPGs, but compared to Raw, they are unforgiving, so I regret any JPG-only shooting I have done.
I look at it this way: would I respect some 5- or 10-year younger kid telling me what to with my photography now, giving me arbitrary limits on my use and repurposing of my own archives? Well, that is what I did to myself with my early JPG-only shooting -- limited my future self. Never again. I'm keeping my film negatives, and I'm keeping my digital Raw, which are even better than film negatives because I can redevelop them differently each time I revisit them. (JPGs are like prints, good for what they were originally good for -- distribution, publication.)
Anyway, calling fellow chatters trolls instead of engaging point for point, giving as good as you get, just leaves us thinking Canon shooters are snooty -- proves us wrong. Perhaps you could share what do you do with your Raw images that go beyond what you do with your JPGs?
What about SRAW on a Canon? Is there any data loss with that file format? I find it frustrating that I'm constantly buying hard drives throughout the year.
Yes there is data loss. The sensor information is demosaiced and a version of it written into the sRAW. You still have full white balance control, but it's still inferior to the full Raw file.
What in ya'lls opinon is the best software to use with raw files?
"Best" Raw software?
It depends.
I use free Google Picasa -- it treats Raw as simple and easy as JPG or TIF, same same as far as image management, printing, sharing is concerned.
http://picasa.google.com/
@keith hoover == this is the REAL question... RAW has all those strengths, but it also requires the photographer to do a heck of a lot of after-image corrections... of course some programs are friendlier/easier/cheaper than others, and have shorter learning curves... and I've gone both ways, JPEG and RAW ... and had excellent results with JPEG using Picasa (Google) ... good enough for most uses -- the viewers love JPEG photos exactly as much as those begun in RAW... subjectively, very little difference in real life.
Earlier, "... RAW ... requires the photographer to do a heck of a lot of after-image corrections ..."
Well, since you use Picasa, you see quite clearly that Raw does NOT require the photographer to do a heck of a lot of after-image corrections any more than JPG or TIF.
No, the beauty of Raw is that when and if the photographer desired to process post capture, Raw offers significantly more resources from the original image then JPG or TIF -- up to 90% more original image capture information.
Or, as you suggest, just use free Google Picasa and treat Raw same same as JPG and TIF with no additional overhead on the photographer's part to handle Raw differently.
Yet, years from now, if the photographer ever desires to revisit an image, especially with new, more powerful software and hardware, the Raw file will be so much more rewarding than a JPG, including repurposing via cropping, greater enlargement without image detail deterioration, shadow and highlight detail recovery, and so on.
Raw is cool, eh what?
You forgot:
"camera throws away 4 or more bits of information when saving as TIF or JPG, about 33% or more of the originally captured image data"
"camera breaks image into 4x4 blocks at best before lossy JPG compression, effectively limiting resolution to 1/4 of Raw or TIF capabilities"
"combined total of what the camera tosses when writing JPG: as much as 90% of the data the sensor captured is lost forever"
It's amazing JPGs look as good as they do, eh?
Click!
Love and hugs,
Peter Blaise
http://www.peterblaisephotography.com/
http://www.flickr.com/photos/peterblaise/sets/
http://www.facebook.com/photos.php?id=728280964
There's another step missing: Going from raw to non-raw, the camera collapses subpixel-information into one square pixel w/o regard for geometry of the pixels on the sensor.
Is that bad? Well, think of the difference between standard-antialiasing and subpixel-antialising.
Also noteworthy: Many of the steps when going away from raw format are good and useful. However, the camera is often not the best at applying them. Sometimes the processing power (although in hardware) is just not there to give the best results. Also there might be alternative algorithms to perform a step, and that is typically best dealt with on a standard computer with all its flexibility.
That said … from a guy who still uses JPEG because it's so amazingly convenient. ;-)
Yes, we could go on and on forever about the inner comparisons of Raw versus JPG -- and we'd be right.
And others can go on and on about the outer comparisons between Raw and JPG, and they'd be right.
The hard truth for many people is that even though JPG tosses 90% of Raw, JPG still looks fine in most people's use-cases, and behaves faster, and has a smaller storage demand, so, what's not to like about JPG?
All we Raw shooters can do is share our insights accurately, and then wait to say, "... I told you so ..." if and when JPG-only shooters revisit their JPG archives over the years ahead, and ask, "... how can I recover lost information so I can re-purpose my old JPG pictures? ..."
... and who knows, maybe in 10 or 20 years, someone may come up with an artificial intelligence algorithm for "recovering" or synthesizing the missing information people might eventually want to "get back" from their JPGs -- sort of the way Adobe Camera Raw "recovers" blown highlights by synthesizing what "should have been" in the blown pixels from predictive ramp information in neighboring pixels.
Regardless:
Raw is a lossless archive medium;
JPG is a lossy distribution medium;
... be happy with whatever choice you made, our only goal here is to make sure the uninformed are informed.
Ahh, JPG aficionados -- gotta love 'em!
Click!
Love and hugs,
Peter Blaise
Yes this is endless, here's a recent blog from a fellow professional photographer:
http://friedmanarchives.blogspot.com/2011/08/where-anti-jpg-bias-came-fr...
... and my response:
Hi Gary, and fellow photographers et al,
Re: Raw versus JPG, ad infinitum, ad nauseum
Thanks as always for your thoughtful and honest experience-based insights.
Yes, modern high-resolution JPGs and modern high-resolution printer dither algorithms are splendid, aren't they?
We Raw shooters are NOT anti-JPG -- we use JPG all the time ... for what JPG is best for, just as we use Raw all the time for what Raw is best for.
Let me dig a little deeper and share some of my experience and insights.
Background:
JPG was of course "invented" to allow quick transmission of photojournalist's images over 300 BAUD phone lines from anywhere around the world, and since newspaper and magazine images weren't very demanding, often only black-and-white, the minimum qualities of those JPG images "way back when" were acceptable in the 1990s.
As personal and publisher demands on image qualities increased, with affordable high resolution large format personal and professional printers, the JPG's loss of original image capture information and detail became increasingly unacceptable, and so, Raw image capture was seen as a supportive relief against JPG's loss of flexibility and loss of potential dynamic range, detail, and color.
And Raw provides relief from compression artifacts when cropping and enlarging small areas of an image, and Raw also provides the flexibility to re-purpose an image later with minimum compromise, including recovery of lost highlight and shadow data and HDR high dynamic range processing, and, perhaps most importantly, Raw can be "re-developed" at any time to a variety of different results by any number of competitive and evolving Raw converter programs.
Foreground:
[ Note, some duplicate information already shared here: ]
Yes, we could go on and on forever about the INNER comparisons of Raw versus JPG -- and we'd be right, JPGs toss up to 90% or more of originally captured Raw image information.
And others can go on and on about the OUTER comparisons between Raw and JPG -- and they'd be right, JPGs look fine in most immediate use-cases, are faster in-camera and when transferring data, and have a smaller, cheaper storage requirements.
Yet, personally, I regret my initial JPG-only archive from when I was new to digital photography and I was afraid of Raw because I was unsure if there'd be an easy way to immediately see and use my images, let alone use them in the unknown distant future.
But now I see that Raw are easily opened on demand, even with free programs like Google's Picasa, and I see thumbnails in Windows Explorer with free codecs from Microsoft or extra-cost codecs from others, and storage has gotten faster and cheaper while getting huge, such that 2 TB stand-alone backup drives now cost well under US$100.
My JPG "originals" from my early years are finished, done, kaput, and do not hold up well to revisiting and repurposing, not as well as my Raw archive from later years -- even though both are through the same camera and are the same resolution -- inexpensive 5 MP, not the comparatively expensive 24 MP you initially refer to, nor the 16 MP or even the 10 MP you eventually searched through.
I must admit that even my 5 MP JPGs print sweet to 2x1.5 feet on modern printers.
Yet, the problem is tweaking those JPGs to re-purpose them to my artistic vision today -- those JPGs then crap out, while Raw originals just keep on giving.
All that we now-Raw shooters can do is share our experience and insights accurately, and then wait to say, "... I told you so ..." if and when JPG-only shooters revisit their JPG archives over the years ahead and ask us, "... how can I recover lost information so I can re-purpose my old JPG pictures? ..."
Who knows, maybe in 10 or 20 years, someone may come up with an artificial intelligence algorithm for "recovering" or synthesizing the missing information people might eventually want to "get back" from their JPGs -- sort of the way ACR Adobe Camera Raw can "recover" blown highlights or noisy shadows by synthesizing what "should have been" in blown or noisy pixels from predictive ramp information in neighboring pixels.
So, regardless:
Raw is a lossless ARCHIVE medium;
JPG is a lossy PRESENTATION medium;
Let's be happy with whatever choice we make for our image archive needs and for our image presentation needs, and know the difference between those two needs.
Our only goal in this "debate" is to make sure the uninformed are informed ... if they wanna be.
Click!
Love and hugs,
Peter Blaise
http://www.peterblaisephotography.com/
http://www.flickr.com/photos/peterblaise/sets/
http://www.facebook.com/photos.php?id=728280964
https://picasaweb.google.com/peterblaise
Post new comment