
| Decision factor | ARRIRAW tends to fit when | ProRes tends to fit when |
|---|---|---|
| Storage and offload | The production has enough camera media, verified backup capacity, and time for larger files | The day depends on smaller files, faster copies, simpler shuttles, or limited travel storage |
| Grade flexibility | Exposure, white balance, HDR shaping, or final look decisions may change significantly in post | The look is controlled on set and the grade is expected to be moderate |
| VFX and plates | The work involves keying, cleanup, CG integration, LED wall plates, or heavy image manipulation | VFX is limited, the footage is clean, and ProRes 4444 XQ or 4444 is enough for the shot work |
| Editorial speed | Editorial can wait for a heavier dailies or proxy process | Editorial needs fast access, direct ProRes handling, or lightweight remote review files |
| Pipeline risk | The post team has tested the exact camera, wrapper, color pipeline, software versions, and conform path | The team benefits from broad NLE, finishing, transcode, and review compatibility |
| Archive and future use | Long-term reprocessing, future HDR trims, remasters, or VFX revisions are likely | The deliverables are immediate, well-defined, and do not require maximum camera-negative flexibility |
What ARRIRAW and ProRes actually are
ARRIRAW is ARRI’s raw camera negative. ARRI describes it as uncompressed, unencrypted sensor data that preserves the camera’s natural color response and exposure latitude. On ALEV3 cameras it's 12-bit log ARRIRAW data, while on ALEXA 35, it's 13-bit log ARRIRAW data. Your post team still has to process it into a viewable RGB image through debayering and color processing. That processing step is the point. With ARRIRAW, you keep more of the decisions open for post. The post team can revisit the debayer, color processing, white balance interpretation, exposure handling, and color pipeline later in a controlled finishing environment. Like film negative, it's meant to preserve the source rather than be the fastest working file. ProRes from an ARRI camera is different because it's an in-camera processed recording format. The camera debayers and encodes the image into an Apple ProRes codec, commonly in LogC or LogC4 depending on camera generation and settings. It's still very high quality, especially in ProRes 4444 XQ and ProRes 4444, but it's no longer raw sensor data.
Storage is often the real deciding factor
ARRIRAW produces much larger camera originals than ProRes. The exact number depends on the camera, sensor mode, resolution, frame rate, and recording option, but the operational pattern is consistent: ARRIRAW burns through media faster, takes longer to offload, needs more shuttle storage, creates larger backups, and puts more pressure on nearline, LTO, cloud transfer, and finishing storage.
- Camera media count and reload rhythm
- Checksum verification time
- Number and size of backup drives
- Dailies render time
- Storage required for conform and grade
Where the grade starts to show the difference
In a normal grade with well-exposed footage, good lighting, and a clear show LUT, ProRes can look excellent. ARRI ProRes has been used at high levels for a long time because the camera’s color science and LogC encoding hold up extremely well. If the DP is exposing carefully and the finishing target is SDR or a controlled HDR pass without aggressive rescue work, ProRes 4444 XQ or ProRes 4444 can be more than enough. The differences become more visible when the grade asks the image to stretch.
- Major white balance changes after the shoot
- Underexposed scenes that need shadow recovery
- Mixed lighting where color separation matters
- Heavy HDR highlight shaping
- Debayer choices for final resolution and texture
Dailies and editorial throughput
Dailies are where the format choice becomes visible to the whole production. ARRI describes dailies as color corrected and properly framed versions of the clips shot each day, created after multiple backups of the original camera negative. They're the bridge from set to post, and they let editorial start while the show is still shooting. With ARRIRAW, dailies creation requires debayering and color processing. That means more compute, more time, and more attention to color management. The dailies team needs the correct camera color pipeline, look files, CDL/LUT decisions, framing, audio sync, timecode, naming, and metadata handling. None of that's unusual, but it's real work. With ProRes, the path can be faster because the camera has already produced a high-quality RGB or YCbCr image in a post-friendly codec. Depending on the editorial system and storage, editorial can use ProRes directly, or your team can transcode it into lighter editorial proxies. This is the origin of ARRI’s “direct-to-edit” history with ALEXA and ProRes. It doesn't mean every show should edit original camera files, but it does mean the source format is friendlier to fast editorial access. A production that needs same-day edits, agency review, sports/doc turnaround, remote editorial upload, or a lightweight assistant editor pipeline will usually benefit from ProRes. ARRIRAW can still work, but the dailies system must be built for it. For editorial, the important decisions are usually these:- Will editorial cut camera originals, mezzanine files, or proxies?
- Will your team make dailies on set, near set, or at a lab?
- Is the upload path sized for OCN, proxies, or both?
- Will the dailies software, the NLE, or both handle sound sync?
- Is the show LUT/look metadata traveling consistently into editorial?
- Will the conform return to ARRIRAW, ProRes masters, or rendered graded media?
VFX pulls, plates, and metadata
For VFX-heavy work, ARRIRAW is usually the safer acquisition choice. Green screen, blue screen, set extensions, beauty work, CG integration, high-end cleanup, and heavy plate manipulation all benefit from maximum source data. ARRIRAW gives the VFX and DI teams more control over debayering, color transforms, exposure interpretation, and noise handling. VFX teams deliver many shots from ProRes 4444 or 4444 XQ sources successfully, especially when the work is limited and the photography is clean. But if the project is expecting hundreds of shots, complicated keys, underexposed plates, LED wall interaction, or extensive roto and comp, the extra safety of ARRIRAW is usually worth the storage. Metadata matters here too, and ARRI notes that modern ALEXA cameras store per-frame and per-shot metadata in recorded formats such as MXF/ARRIRAW and MXF/ProRes. The camera can also capture active look files as metadata. That's helpful, but it isn't a replacement for a real VFX data package.
- Camera reports and clip metadata
- Lens metadata when available
- Frame lines and extraction notes
- Lens grids
- HDRI and witness camera material
- Color pipeline notes
- Show LUTs, CDLs, and viewing transforms
- Plate handles and retime information
- Any in-camera texture, sharpening, or noise reduction settings
Compatibility means more than opening the file
ProRes has the broadest practical compatibility. Final Cut Pro, Premiere Pro, Media Composer, Resolve, finishing systems, review systems, transcoders, and many asset platforms understand ProRes in some form. Apple’s own documentation lists support for all ProRes versions in Final Cut Pro. That broad support is one reason ProRes is still a safe choice for fast-moving productions. ARRIRAW support is also common in professional post, but it's more version-sensitive. You need support for the exact camera generation, wrapper, resolution, color science, and metadata. ALEXA 35 introduced LogC4 and the REVEAL color pipeline, so old assumptions from LogC3 workflows may not hold. If the post pipeline hasn't been updated, ARRIRAW may import but display incorrectly, lose metadata behavior, or require extra conversion steps. The same applies to MXF. ARRI’s newer cameras use MXF for both ARRIRAW and ProRes, and ARRI states that the camera stores metadata in the file header. That's good for professional workflows, but it means older tools built around QuickTime ProRes habits may need testing. “It supports ProRes” isn't specific enough. “It supports this ARRI camera’s MXF/ProRes, this resolution, this frame rate, this LogC version, and this metadata path” is the useful version. The practical compatibility test should include the actual route the footage will take:- Offload and checksum tool
- Dailies software
- Sound sync path
- Editorial NLE
- Assistant editor relink workflow
- VFX pull tool
- Color grading system
- Archive and restore process
- Any remote review or cloud proxy workflow
Delivery doesn't automatically require ARRIRAW
Delivery specs often influence acquisition, but they don't always dictate it directly. A streamer, broadcaster, studio, or distributor may specify approved cameras, minimum raster, HDR requirements, archival deliverables, or original camera format requirements. If the spec says ARRIRAW or raw acquisition, you've your decision. If it allows ProRes, then the production still has to judge whether ProRes is enough for the creative and post plan. For theatrical finishing, HDR mastering, premium episodic, and long-term library value, ARRIRAW is attractive because the negative remains maximally reprocessable. Future remasters, alternate trims, new HDR passes, or VFX revisions benefit from having the raw source. For corporate, documentary, live-adjacent, social, branded, internal, event, and fast-turnaround broadcast work, ProRes often makes more sense. The audience won't see the difference if the lighting, exposure, lensing, and color management are good. They might notice missed deadlines, delayed edits, dropped review cycles, or a production that ran out of storage halfway through the day. Delivery is the final output, while acquisition is the risk-management decision that shapes how safely the production reaches it.Common ways the choice goes wrong
Most ARRIRAW versus ProRes problems come from choosing a format without the workflow to support it rather than from choosing the “wrong” format in theory. The common failure patterns are predictable:- The team selects ARRIRAW, but the production doesn't add enough recording media.
- The team estimates offload time from file copy speed instead of checksum-verified backup time.
- Editorial assumes direct playback of OCN on hardware that can't handle it.
- The team chooses ProRes 422 for a VFX-heavy job that really needed 4444 XQ or ARRIRAW.
- ALEXA 35 LogC4 material enters a LogC3-based pipeline.
A practical decision model for set
In prep, the team should start with the hardest part of the job, not the average shot. One greenscreen day, one night exterior, one heavy HDR scene, or one sequence with unknown final look can justify ARRIRAW even if most of the show could survive on ProRes. Conversely, one prestige scene doesn't automatically justify ARRIRAW for a six-week documentary if the storage, travel, and editorial schedule make it unmanageable. ARRIRAW is usually the better call when the project has these conditions:- High-end narrative, commercial, or premium episodic finishing
- Heavy VFX, keying, cleanup, or CG integration
- Aggressive HDR grade or uncertain final look
- Significant reframing, extraction, or stabilization
- Enough media, storage, backup, and dailies capacity
- Fast editorial turnaround
- Limited storage or travel footprint
- Remote collaboration with large upload constraints
- Controlled lighting and exposure
- Minimal VFX
FAQ
No. ARRIRAW preserves the most flexibility because it keeps the image as raw camera data, but it also increases storage, offload time, dailies processing, and post complexity. ProRes can be the better choice when the look is controlled, the grade isn't expected to be extreme, editorial needs fast access, or the production can't support a raw workflow.
For serious finishing, ProRes 4444 XQ or ProRes 4444 are usually safer choices than 422 variants because they preserve more color information. ProRes 422 HQ can still be appropriate for many broadcast, documentary, branded, and fast-turnaround jobs. ProRes 422 Proxy should generally be treated as an editorial proxy format, not as a high-quality acquisition master.
ARRIRAW must be debayered and processed into a viewable image before editorial dailies can be made. That adds compute time and requires correct color management, look files, framing, metadata handling, and audio sync. ProRes is already processed in camera into a post-friendly video file, so it can often move into dailies and editorial faster.
Yes, especially when the footage is clean, well exposed, and recorded in a high-quality ProRes format such as 4444 or 4444 XQ. However, ARRIRAW is usually preferred for heavy keying, compositing, underexposed plates, CG integration, beauty work, LED wall work, and shots that need substantial manipulation because it gives VFX and DI teams more control over debayering, color, exposure interpretation, and noise handling.
The test should follow the real path from camera to delivery: verified offload, backup, dailies, sound sync, editorial import, relink, VFX pulls, conform, grade, review, archive, and restore. It should use the exact camera model, recording format, wrapper, resolution, frame rate, color science, LUTs, and metadata workflow planned for production. A file opening in one application isn't enough proof that the whole pipeline is safe.
Mixed-format shows need consistent clip naming, camera reports, color pipeline notes, and metadata that identifies which scenes are raw, which are ProRes, and which files are editorial proxies or finishing masters. Aspect lets teams track those attributes in searchable project-level fields, so assistants and post supervisors can filter by format, LUT status, VFX status, or delivery stage using custom metadata.





