What Is BRAW? A Production Guide to Blackmagic RAW

Blackmagic RAW, usually shortened to BRAW, is a camera codec designed to preserve much of the control people expect from RAW acquisition while making the footage practical to record, move, and edit. It stores 12-bit image information, camera metadata, and sensor-specific information in a format optimized for modern CPUs and GPUs.

The useful answer is not simply “BRAW is RAW.” A production team needs to know what that means for exposure decisions, storage, editing, and archive design. BRAW changes the point at which some image processing happens, keeps important adjustments editable as metadata, and offers two different approaches to managing compression.

What BRAW records

A conventional compressed video file often bakes major image decisions into RGB or YCbCr pixels before the file reaches the editor. A RAW-oriented workflow aims to preserve sensor-derived information and defer more interpretation to post-production. BRAW combines this flexibility with partial in-camera processing so the recorded data is less demanding than a fully unprocessed sensor dump.

Blackmagic Design describes the format as using a custom non-linear 12-bit space. Twelve-bit encoding provides 4,096 code values per channel before any downstream transformation, compared with 1,024 values for 10-bit or 256 for 8-bit. Bit depth alone does not guarantee image quality, but it gives grading operations more tonal precision to work with.

BRAW also stores camera metadata. Depending on the camera and software, settings such as white balance, ISO interpretation, tint, and color science can be adjusted non-destructively in post. The original captured information is not rewritten every time an editor changes a RAW control; the software interprets the clip using the updated metadata.

Why BRAW is different from a generic “RAW file”

RAW formats sit on a spectrum. At one end, a file may contain data extremely close to the sensor readout and require heavy debayering later. At the other, a camera may perform significant processing before storing a compressed image. BRAW moves part of the demosaic process into the camera and packages the result with sensor characteristics and metadata.

That design creates three production advantages:

1. The camera can reduce the amount of data that must be recorded. This makes common flash media and SSD workflows more practical.
2. The computer can decode clips efficiently. Blackmagic publishes CPU and GPU acceleration paths for supported systems.
3. The color pipeline can remain flexible. RAW controls and camera color science can travel with the footage instead of being permanently baked into a display-ready image.

The tradeoff is that “RAW” should not be read as “untouched sensor bytes.” BRAW is a carefully designed imaging pipeline with camera-side processing and compression. That is not a defect; it is the engineering choice that makes the workflow usable.

Constant Bitrate and Constant Quality

BRAW offers two encoding strategies, and their names describe what they prioritize.

Constant Bitrate settings are expressed as ratios such as 3:1, 5:1, 8:1, and 12:1. The ratio compares the compressed stream with an unprocessed frame baseline. Lower ratios retain more data and require more storage. Their main production advantage is predictability: if the resolution, frame rate, and ratio are known, a crew can make a stable media plan.

Constant Quality settings are labelled Q0, Q1, Q3, and Q5. Instead of enforcing a fixed upper data target, the encoder allows the bitrate to react to image detail. Fine foliage, water, noise, texture, and movement may need more data than a clean interview against a simple background. Constant Quality therefore protects a quality target at the cost of less predictable storage.

Neither family is automatically “professional” or “amateur.” The right choice depends on what the production must control. A live event with a hard card limit may value predictable roll time. A VFX plate or detailed landscape may justify a quality-led mode and more conservative media sizing.

What BRAW changes on set

The codec setting affects more than the total number of terabytes. It shapes the entire data path:

• The recording medium must sustain the peak stream without dropping frames.
• The card capacity determines the maximum continuous roll before a media change.
• The offload station must copy cards quickly enough to return them to camera.
• The backup plan must hold at least two verified copies before source media is cleared.
• The post-production storage must provide enough capacity and throughput for editing.
• The archive plan must account for originals, project files, audio, graphics, and delivery masters.

A one-hour estimate is therefore a workflow unit. If a setting creates roughly half a terabyte per hour, a two-camera day with four recorded hours per camera is not a one-terabyte problem. Before safety margin, it is already around four terabytes of camera originals. Two working copies double the immediate storage requirement, and an archive copy adds more.

BRAW in post-production

DaVinci Resolve provides the most direct BRAW workflow, including RAW controls and Blackmagic color management. Other editing applications can support the format through native integrations, system components, or Blackmagic RAW software, depending on platform and application version.

Even when a computer can decode BRAW natively, proxies may still help. A multicam timeline, laptop edit, remote workflow, or effects-heavy sequence can be limited by storage throughput and simultaneous stream count rather than by a single clip. Proxies are a workflow choice, not proof that the original codec is poorly optimized.

The best handoff preserves three things:

• Original BRAW files with folder structure intact
• Verified checksums or copy reports
• Clear notes about camera settings, color management, audio sync, and any in-camera LUT metadata

Avoid renaming or reorganizing source media before a verified copy exists. An editorially convenient folder structure can be created in the NLE without risking the integrity of the camera original.

When BRAW is a strong fit

BRAW is especially useful when a production wants grading flexibility, Blackmagic camera integration, and manageable data compared with less compressed RAW approaches. It is common in narrative, documentary, commercial, music video, event, studio, and independent film workflows.

It may be less attractive when the post-production environment cannot support the codec efficiently, a delivery pipeline is standardized on another acquisition format, or very small files matter more than RAW control. Codec selection should follow the full pipeline, not the camera menu in isolation.

A practical starting workflow

For a new production, begin with the delivery and post needs, then work backward:

1. Choose the resolution and frame rate required by framing, VFX, stabilization, slow motion, or delivery.
2. Select a compression mode appropriate to image detail and post latitude.
3. Use the BRAW calculator to estimate data rate, storage, and record time.
4. Add a visible safety margin for retakes and unpredictable rolls.
5. Confirm the recording device appears on the current approved-media list.
6. Stress-test the exact camera, firmware, cable, and medium at the highest expected setting.
7. Time a full offload and checksum verification before the shoot.

That sequence treats BRAW as part of a production system. The codec provides flexibility, but the plan protects the footage.

Sources and calculation notes

• Blackmagic RAW overview: manufacturer information about the codec and encoding modes.
• BRAW Planner methodology: the estimation formulas, unit conventions and limitations used on this site.

Workflow suggestions in this guide are planning guidance, not a claim that a particular camera or drive has been tested by the author.