ProRes vs ProRes RAW: Which Camera Workflow to Use

ProRes RAW is not better ProRes. It changes where image processing happens. A regular ProRes file arrives in post as finished video pixels. A ProRes RAW file arrives as sensor data with much of the camera interpretation still pending. That shift buys color real control, including ISO, exposure offset, and color temperature. It also hands your workflow a bill. Someone now owns debayering, RAW control support, and metadata that has to survive every transcode. The working set gets bigger too.

Regular ProRes is already interpreted into a video image; ProRes RAW keeps more sensor information available for later adjustment.

Factor	Regular ProRes	ProRes RAW
Image state	Already processed video pixels	RAW sensor data preserved for post processing
Camera decisions	White balance, ISO behavior, debayering, sharpening, noise reduction, and log or display transform are mostly committed	More camera interpretation can be adjusted later in supported software
Grading latitude	Strong latitude when recorded well, especially in 10-bit 4:2:2 or 4:4:4:4	Greater control over ISO, exposure offset, color temperature, and sensor-level interpretation when supported
Editorial compatibility	Broadly supported across NLEs, finishing systems, dailies tools, and review workflows	More dependent on specific software, metadata handling, and RAW control support
Performance	Designed for efficient real-time editing and multistream playback	More decode and processing work because RAW data must be interpreted into viewable pixels
Storage pressure	Published, predictable targets: ProRes 422 HQ is about 707 Mb/s at UHD 29.97, and 4444 XQ about 1,697 Mb/s at 4K	Variable by scene, and Apple publishes no target rate. It generally lands between ProRes 422 and 4444, plus the overhead of proxies, dailies, and transcodes
Best fit	Fast turnaround, multicam, documentary, corporate, live capture, and predictable post pipelines	HDR work, difficult lighting, hero shots, select VFX plates, and Apple-centered RAW workflows

The difference that matters in post

Regular ProRes stores conventional video pixels. The camera has already converted sensor data into an image using its own color science. That conversion commits most of the camera-side choices:

White balance and ISO behavior.
Debayering, sharpening, and noise reduction.
The log or display transform.

You can still grade a good 10-bit 4:2:2 or 4:4:4:4 recording heavily. You just cannot unwind those decisions. ProRes RAW stores RAW sensor data using ProRes compression technology. It does not commit fully to the camera’s processed video output. It keeps the underlying sensor information available for RAW processing later. In Final Cut Pro, ProRes RAW can expose controls such as ISO, exposure offset, and color temperature in the inspector. For supported iPhone ProRes RAW media, Apple’s tools can expose additional camera settings and processing options. The simple version:

ProRes is a high-quality editing and finishing codec for already processed video.
ProRes RAW is a capture format for RAW sensor data.
ProRes is easier to hand between departments and applications.
ProRes RAW gives more image latitude, but requires compatible tools and a more deliberate post path.
You can't turn a normal ProRes recording into ProRes RAW later.

That last point is the one that catches productions. You have to capture ProRes RAW from a compatible camera, or a compatible camera-plus-recorder setup. If the camera only recorded ProRes 422 HQ internally, the production has already missed the RAW decision.

When regular ProRes is the right camera workflow

Regular ProRes is the safer default for a lot of professional work because it is predictable. Editors know how it behaves. DITs and assistants know how to back it up, proxy it, and relink it. Post supervisors can estimate storage and turnaround without building a science project around every camera body. ProRes fits projects that need:

Fast dailies and same-day edits
Multicam cutting with many streams
A broad choice of NLEs and finishing systems
Simple archive and turnover
A grade that starts from a well-exposed log image rather than relying on RAW-side correction

For many shows, ProRes 422 HQ or ProRes 4444 is already more than enough. Apple designed the ProRes family for real-time, multistream editing performance. It delivers high image quality at lower storage rates than uncompressed media. Editorial can then cut all day without rendering every move. The main ProRes decision is which flavor to record. That answer follows from camera output, bit depth, and chroma requirements, plus any alpha or graphics needs and the finishing target. ProRes 422 HQ is a strong acquisition choice for high-quality 4:2:2 workflows. ProRes 4444 or 4444 XQ makes sense when the pipeline needs 4:4:4:4 quality, alpha channels, or very high-end log preservation. ProRes LT and Proxy show up more in offline editing or lower-data-rate recording, and they are rarely the first choice for premium camera masters unless project constraints demand it. The benefit is fewer weird handoff moments. A ProRes file is easier to view, sync, and string out. It is also easier to transcode and send to another department. That is why regular ProRes remains strong for documentary and corporate work. It fits episodic editorial and multicam shoots. It fits live capture, branded content, and lower-friction commercial post.

When ProRes RAW is worth the overhead

ProRes RAW earns its keep when the image really benefits from post-side RAW control. The project needs a realistic use case for those options and a schedule that can support them. ProRes RAW is most useful when you expect one or more of these conditions:

High dynamic range delivery where highlight handling matters
Mixed lighting or uncontrolled environments where white balance may need deeper correction
Exposure conditions that are hard to nail consistently
VFX pulls or beauty work that benefit from cleaner sensor-level interpretation
A color workflow centered on Final Cut Pro, Motion, Compressor, or another confirmed ProRes RAW-aware tool

RAW gives post more room to make camera interpretation decisions later. It does not rescue a shot that is badly clipped, noisy, or underlit. It does not fix the wrong monitoring assumptions either. When exposure and color are close enough, though, RAW gives the colorist more latitude before the image falls apart. This is especially relevant for HDR. Apple positions ProRes RAW as well suited to HDR content creation because it carries more of the sensor information into post. That helps with highlight rolloff, with bright practicals and skies, and with reflective surfaces and high-contrast interiors, where a baked log recording may leave less flexibility.

Camera and recorder support isn't automatic

Don't assume that a camera that records ProRes also records ProRes RAW. These are separate capabilities. A given body may do any of the following:

Record regular ProRes internally.
Output RAW over HDMI or SDI to a supported external recorder.
Record ProRes RAW internally.
Support a different RAW format instead, such as BRAW, ARRIRAW, REDCODE RAW, or Nikon N-RAW.

Common ProRes RAW capture paths include:

Supported cameras outputting RAW to Atomos recorders
Cameras that record ProRes RAW directly, including models such as Nikon Z 8 and Nikon Z 9
DJI Zenmuse X7 recording ProRes RAW directly
Supported iPhone models recording ProRes RAW through Apple’s camera workflow with the required external storage setup
Specific third-party cameras and devices that Apple has licensed and certified for ProRes RAW workflows

You still need to check the exact model and firmware version. Then check resolution and frame rate, recorder and media, and app support. ProRes RAW compatibility is full of “yes, but only in this mode” details. A camera may output RAW at one resolution but not another. A recorder may support one frame rate but not another. The camera or recorder may need a firmware update. A camera may support ProRes RAW over HDMI but not internally. The production mistake is treating “supports ProRes RAW” as one complete spec. Treat it as a chain.

ProRes RAW compatibility depends on the whole capture and post chain, not just the camera setting.

The chain includes:

Camera model and firmware
RAW output mode
Recorder model and firmware, if external
Cable type and signal reliability
Recording media speed
Resolution, frame rate, and sensor crop mode
Audio and timecode handling
NLE import support
RAW control support in the finishing application
Transcode or proxy plan
Archive plan for the original camera files

If one part of that chain fails, the format choice becomes a post problem instead of an image-quality advantage.

The edit system may not want your RAW files

Apple designed ProRes RAW to bring ProRes-like performance to RAW media. It is still not the same editing burden as regular ProRes. RAW playback requires processing at decode time. The system has to interpret sensor data into viewable pixels and apply RAW-to-log conversion or a camera LUT. Then it has to handle whatever the editor adds on top: grade, effects, scaling, retiming. Final Cut Pro has the cleanest Apple-native path. It can process ProRes RAW automatically on import by applying RAW-to-log conversion and built-in camera LUT settings based on metadata. If that metadata is missing, for example because transcoding or mishandling stripped it, your team may need to view or change those settings manually. That metadata behavior is what trips up assistants. A clip that looks correct in one system and strange in another may not be bad footage. It may be a RAW interpretation issue. The application may be using a different conversion, missing a camera LUT, reading the camera metadata differently, or defaulting to a transform no one intended. For editorial, this creates a decision. Cut the ProRes RAW originals, or create dailies and proxies. Cutting originals can work on strong hardware, especially for shorter projects or simpler timelines. An offline workflow is saner once the job involves heavy footage volume, remote editors, or tight daily turnaround. Dailies are still worth the effort. A proper dailies process gives editorial usable files that are color-corrected, framed, and synced, while preserving the original camera negative for finish. For RAW acquisition, that process also becomes the place where the show establishes its first interpretation of the image. Your team shouldn't treat the dailies color pipeline as an afterthought.

Storage and performance tradeoffs

ProRes RAW is compressed, but RAW workflows still create more data pressure than a simple ProRes editing path. The camera originals may be larger than the ProRes alternative. The workflow then generates extra files on top of them:

Dailies and editorial proxies.
Review exports and intermediate transcodes.
VFX pulls and final graded masters.

The storage problem is really an access problem. How many departments need the media, how fast do they need it, and can the network or drives sustain playback? A single editor on a fast local RAID has a very different experience than five remote editors pulling media across shared storage.

RAW overhead can show up as shared storage pressure, access delays, and playback bottlenecks across departments.

Expect pressure in these areas:

Camera card offload time
Cloud upload and download windows
Proxy generation time
Relink reliability
Archive cost

RAW is easiest to justify when the production has already planned for this. If the post team is discovering the storage impact after the first shoot day, the workflow is already in trouble. The safer compromise is selective capture. Record ProRes RAW only where it earns its place, record regular ProRes everywhere else, and keep one consistent dailies format for editorial. Not every angle in a multicam interview needs RAW. Neither does every B-roll shot or every social cutdown. Selective RAW capture preserves the image benefits without drowning the whole post pipeline.

Color control and metadata behavior

The main creative reason to choose ProRes RAW is the ability to adjust camera interpretation in post. Apple’s RAW controls can include ISO, exposure offset, and color temperature. Those controls are different from pushing a normal color correction node on baked video. They happen as part of RAW processing, before the image is fully converted into the working color space.

RAW controls happen before the image is fully interpreted, while normal grading works on an already processed frame.

That flexibility only works with consistent color management. Decide early how your team should view RAW media and which log conversion to use. Decide whether to apply built-in camera LUTs, and settle what editorial dailies should look like. Otherwise editorial, VFX, and color end up looking at different versions of the same shot, and so does the client. Common failure modes include:

RAW clips importing with the wrong camera LUT or no LUT
Metadata missing after a transcode
Editorial proxies not matching the RAW interpretation used in color
Assistants relinking to files with different names, reel metadata, or timecode
A finishing system that can't access the same RAW controls used earlier

Your team can solve all of these, but only by catching them during workflow testing. Run a five-minute camera test through the entire path: ingest, dailies, edit, relink, color, export. That test is worth more than a long theoretical debate about codecs.

ProRes RAW in DaVinci Resolve: the answer changed in 2025

This used to be the reason not to shoot ProRes RAW, and it is worth stating plainly because most of the advice online still predates the change. Apple launched ProRes RAW in April 2018, and for seven years DaVinci Resolve could not read it. A Resolve-finishing facility handed ProRes RAW files had to transcode them to ProRes 4444 or image sequences before doing anything, which baked in the RAW decisions and threw away most of the reason for shooting RAW at all. That was a genuine, unrecoverable production trap: the capture decision was made on set and could not be undone in post. That gap closed in DaVinci Resolve 20.2, released September 2025, which decodes Apple ProRes RAW and ProRes RAW HQ natively. Clips import, play back, and grade in Resolve without a conversion step. Blackmagic shipped it alongside ProRes RAW recording on the Pocket Cinema Camera 4K. So the practical guidance now splits on one question, which is your Resolve version rather than your camera:

Resolve 20.2 or later. ProRes RAW is a normal RAW workflow. No transcode, no baked-in decisions, no reason to prefer N-RAW or BRAW purely on toolchain grounds.
Anything earlier. The old advice holds in full. Plan the transcode target before the shoot, and confirm which RAW controls survive it, because they will not all survive.

Note that this is decode support. Resolve reads ProRes RAW; it does not write it. If your deliverable is a RAW file, that is still a camera and recorder decision rather than something you export.

A sane way to choose on a real job

Start from the finish, not the camera menu. Ask where your team will grade the master, what the delivery requires, and how much image flexibility the grade actually needs. Then work backward to acquisition. Regular ProRes fits when speed, compatibility, and predictable editing outweigh RAW latitude. That covers most fast-turnaround jobs and many multicam shoots. It covers most corporate and documentary projects, and any production where the camera team can expose and white balance consistently. ProRes RAW fits when the image needs post-side camera control and your team has built the pipeline for it. That covers HDR-focused work and difficult lighting. It covers premium small-camera acquisition, select VFX plates, and jobs where the finishing team specifically wants ProRes RAW controls. A mixed workflow is often the most production-friendly choice. Record ProRes RAW for hero material, difficult scenes, or shots your team will grade most aggressively. Record ProRes 422 HQ or ProRes 4444 for everything that benefits more from easy editing and handoff. Then normalize the editing experience with dailies or proxies, so assistants and editors aren't switching behavior clip by clip. The codec decision is really about where risk belongs. Regular ProRes puts more responsibility on the camera team to bake a strong image, and gives post a stable, efficient file. ProRes RAW gives post more control, and asks the production to manage compatibility, metadata, and performance with more care, plus storage on the same footing. So ask one question before the shoot: will anyone open the RAW controls? If yes, ProRes RAW is the right call. If those controls will sit unused while assistants fight transcodes and relinks, record regular ProRes.

FAQ

Not automatically. ProRes RAW gives post more control over sensor interpretation, including settings such as ISO, exposure offset, and white balance in supported workflows. Regular ProRes is easier to edit, share, relink, and archive. Choose ProRes RAW when the extra image latitude will actually be used and the whole pipeline supports it.

No. ProRes RAW must be captured from a supported camera, or a supported camera and recorder setup, at the time of shooting. A normal ProRes 422, ProRes 422 HQ, or ProRes 4444 file is already processed video and can't be turned back into sensor RAW data.

ProRes RAW support depends on the exact camera, firmware, resolution, and frame rate, plus the recorder, media, and app. Common workflows include supported cameras outputting RAW to Atomos recorders, cameras such as the Nikon Z 8 and Z 9 that record ProRes RAW internally, DJI Zenmuse X7 workflows, and supported iPhone ProRes RAW capture paths with the required external storage setup. Always confirm the specific mode before production.

Yes, and this changed recently enough that a lot of advice still says otherwise. DaVinci Resolve decodes Apple ProRes RAW and ProRes RAW HQ natively as of Resolve 20.2, released September 2025, so ProRes RAW clips import, play back, and grade without a transcode step. For the seven years before that, Resolve could not read the format at all, which is why older guidance tells you to convert to ProRes 4444 or image sequences first. If you are on a Resolve version earlier than 20.2, that older advice still applies to you.

Not always in a simple one-to-one comparison, because ProRes RAW is compressed and has different data rates depending on resolution and quality setting. The bigger issue is total workflow storage. RAW jobs often generate additional dailies, proxies, VFX pulls, review files, intermediates, and online conform media, so the overall storage and transfer burden can be higher than a straightforward ProRes editorial workflow.

Treat the RAW interpretation as production metadata, not tribal knowledge. Store notes for camera LUTs, RAW-to-log settings, and exposure offsets alongside the media, together with the dailies look. Assistants, editors, and color can then track the intended version in Aspect through custom metadata.