Raw video used to be a cinema-camera problem. In 2026 it is a wedding problem. Canon's EOS R5 Mark II records Canon RAW and RAW Light internally, Panasonic's GH7 records ProRes RAW to its own card, Nikon's ZR offers N-RAW, R3D NE and ProRes RAW HQ, and a Sony FX3 paired with an Atomos recorder writes ProRes RAW over HDMI. On the software side, the last big gaps closed in the past year: DaVinci Resolve 20.2 added native ProRes RAW decoding in September 2025, and Adobe added N-RAW in November 2025 and R3D NE in January 2026. The result is that a lot of wedding videographers can now shoot raw without buying anything new — and a lot of them are handing raw cards to an outsourced editor without telling them what they are, how they were exposed, or what the editor is supposed to do with them. This guide covers what raw actually gives you on a wedding day, which formats each editing application reads, what raw costs in storage and turnaround, and how to hand it over so your editor spends their hours on the film rather than on decoding.
What Raw Video Actually Changes, and What It Does Not
Raw video moves the camera's image processing from the wedding day to the edit suite. A normal video file has already been demosaiced, white-balanced, sharpened, noise-reduced and encoded into a picture profile inside the camera. A raw file stores the sensor data before most of that happens, and the editing software does the conversion later. Apple's ProRes RAW white paper describes exactly this: conventional video has demosaicing and processing "burned in" at capture, while ProRes RAW encodes the Bayer-pattern image and defers that work to the application.
For a wedding, the practical consequence is a short list of things that become adjustable after the fact:
- White balance and tint — changed as a decode parameter rather than pushed around in a grade, which matters under the mixed tungsten, LED and window light of most receptions.
- Exposure or ISO metadata — the editor can re-map the image before any look is applied, within the limits of what the sensor actually captured.
- Demosaicing and noise handling — the software, or a camera maker's plug-in, does this instead of the camera's real-time processor.
- Log conversion — the editor chooses which log curve the raw data is mapped into, so footage can be graded like the log files they already know.
Raw does not fix everything, and wedding shooters who expect it to are the ones who end up disappointed. It cannot restore a highlight that clipped on the sensor, because there is no data there to recover. It cannot fix missed focus, motion blur from a shutter that was too slow, rolling-shutter skew on a fast whip-pan, or a dance floor that was simply too dark. It does not replace good exposure; it widens the tolerance around good exposure.
| Problem on the wedding day | Does raw help? | Why |
|---|---|---|
| Wrong white balance in a mixed-light reception | Yes, strongly | White balance is a decode parameter, not a baked-in setting |
| Slight underexposure on a backlit ceremony | Yes, moderately | More latitude to lift shadows before noise and banding appear |
| Blown sky behind the couple | No | Clipped sensor data cannot be recovered by any format |
| Missed focus on the ring exchange | No | Focus is optical; raw stores the same soft image |
| Noisy, very dark dance floor | Partly | Better noise processing options, but the underlying signal is still thin |
| Skin tones that look different between cameras | Partly | Consistent decode helps; mismatched sensors still need matching |
If you already shoot log and expose carefully, raw is an incremental improvement, not a transformation. If you regularly fight white balance at receptions, it can be a very real one.
The Raw Formats Wedding Videographers Actually Meet
There are four raw families that matter to wedding work in 2026, and they behave differently enough in post that your editor needs to know which one is on the card before they open a project.
Apple ProRes RAW
ProRes RAW comes in two levels, ProRes RAW and ProRes RAW HQ. It is the closest thing to a cross-brand standard: Panasonic records it internally on the GH7, Nikon offers ProRes RAW HQ on the ZR, and Atomos recorders produce it from HDMI raw output on bodies such as the Sony FX3. Since 2023, camera makers can ship ProRes RAW plug-ins that replace Apple's standard conversion with their own processing, which is why the same format can look slightly different depending on whether the editor chooses standard processing or the camera maker's plug-in.
Blackmagic RAW (BRAW)
BRAW is Blackmagic Design's format, recorded by its own cameras and by Blackmagic recorders from some other cameras. It is native in DaVinci Resolve. Premiere reads it through Blackmagic's free Blackmagic RAW plug-in, which Adobe's help pages direct users to install. Final Cut Pro has no built-in BRAW support; editors on Final Cut typically use BRAW Toolbox, a paid third-party app from LateNite Films sold on the Mac App Store.
Canon RAW and Cinema RAW Light
Canon's raw video is recorded as .CRM files: the EOS R5 Mark II offers RAW and a lighter RAW Light option internally, and the Cinema EOS line markets the same family as Cinema RAW Light. Premiere supports it, Resolve supports it, and Final Cut Pro reads it through Canon's own RAW plug-in. If a second shooter is running an R5 Mark II in raw and your A-camera is a Sony in S-Log3, you already have a mixed-format day.
Nikon N-RAW and R3D NE
Nikon's N-RAW is recorded internally on bodies including the Z8, Z9 and Z6III. The Nikon ZR, launched in 2025, added R3D NE — a RED-derived raw format — alongside N-RAW, ProRes RAW HQ and H.265. These are the formats where editing-software support has moved fastest and where a partner running an older version is most likely to hit a wall.
| Format | Typical wedding cameras | Recorded | Adjustable after capture |
|---|---|---|---|
| ProRes RAW / RAW HQ | Panasonic GH7, Nikon ZR, Sony FX3 via Atomos | Internal on some bodies, external recorder on others | ISO/exposure and white balance where the camera supplies metadata; log conversion |
| Blackmagic RAW | Blackmagic cinema cameras | Internal | Full decode settings, stored in sidecar files |
| Canon RAW / RAW Light (.CRM) | Canon EOS R5 Mark II, Cinema EOS bodies | Internal | White balance, ISO, colour space and gamma at decode |
| N-RAW / R3D NE | Nikon Z8, Z9, Z6III, ZR | Internal | Exposure, white balance, log conversion at decode |
Exact recording options, resolutions and frame rates vary by body and firmware version, so check your own camera's manual before you commit a whole wedding to one format. The point of the table is not the spec sheet; it is that each format carries a different set of decode decisions your editor will be making on your behalf.
Which Editing Software Reads Which Raw Format in 2026
Compatibility is the single most common reason a raw hand-off goes wrong. The format opens perfectly on your machine, the editor's copy of Premiere or Resolve is a version behind, and the first day of their turnaround goes on troubleshooting instead of cutting.
| Format | DaVinci Resolve | Adobe Premiere | Final Cut Pro |
|---|---|---|---|
| ProRes RAW | Native since Resolve 20.2 (Sept 2025), on macOS, Windows and Linux | Supported; on Windows it requires Apple's ProRes RAW decoder to be installed | Native |
| Blackmagic RAW | Native | Via Blackmagic's free RAW plug-in | Via third-party BRAW Toolbox |
| Canon RAW / Cinema RAW Light | Native | Supported | Via Canon RAW plug-in |
| Nikon N-RAW | Supported | Native since Premiere 25.6.1 (Nov 2025) | Check current support before handing off |
| R3D NE (Nikon ZR) | Supported | Native since Premiere 26 (Jan 2026) | Check current support before handing off |
Three details from the vendor documentation catch people out. First, Adobe's ProRes RAW support page states that on macOS, ProRes RAW import only works with the Metal renderer selected, and on Windows the user must separately install Apple's ProRes RAW decoder. Second, Adobe staff have stated that N-RAW and R3D NE support on the Mac is limited to Apple silicon machines, so an editor still on an Intel Mac cannot open those files in Premiere at all. Third, Premiere was renamed from "Premiere Pro" to simply "Premiere" with version 26 in January 2026 — if a partner tells you they are "on Premiere Pro 2025", that is a version-number conversation worth having before you ship a drive of R3D NE.
The fix is not to memorise the table. It is to ask your editor one question before the wedding, not after: which application and version will you use, on what hardware, and can it open this exact format? A good partner answers in a line. If they are not sure, send a thirty-second test clip before the day and have them confirm it opens, plays and decodes correctly.
The Real Cost of Raw: Storage, Transfer and Turnaround
Raw is not free just because the camera already supports it. The cost shows up in three places: card and drive space, upload time to your editor, and decode load on the editor's machine.
Apple is unusually specific about ProRes RAW data rates. Its white paper says ProRes RAW generally falls between ProRes 422 and ProRes 422 HQ, and ProRes RAW HQ between ProRes 422 HQ and ProRes 4444. It also notes that ProRes RAW is designed for constant quality rather than a fixed bitrate, so detailed or noisy images — a high-ISO reception, for instance — encode at higher data rates and produce larger files. You cannot quote a single number for raw, but you can bracket it using Apple's published ProRes targets.
| Format at UHD 23.976/24p | Data rate | Per minute | Per hour of footage |
|---|---|---|---|
| ProRes 422 | 471 Mbps | about 3.5 GB | about 212 GB |
| ProRes 422 HQ | 707 Mbps | about 5.3 GB | about 318 GB |
| ProRes 4444 | 1,061 Mbps | about 8.0 GB | about 477 GB |
| ProRes RAW (bracket) | between 422 and 422 HQ | roughly 3.5–5.3 GB | roughly 212–318 GB |
| ProRes RAW HQ (bracket) | between 422 HQ and 4444 | roughly 5.3–8.0 GB | roughly 318–477 GB |
| A 150 Mbps H.265 file, for comparison | 150 Mbps | about 1.1 GB | about 68 GB |
The arithmetic is simple: divide the bitrate in megabits per second by eight to get megabytes per second, multiply by sixty for a minute, and by 3,600 for an hour. At 29.97p the same formats run about 25 percent higher — Apple lists ProRes 422 HQ at 884 Mbps for UHD 30p — and higher resolutions scale the numbers up further; 8K raw, which several current bodies offer, is in a different storage class altogether.
Now multiply by a wedding. A two-camera day that records four hours of footage on each body is eight hours of material. At H.265 bitrates that is a few hundred gigabytes. At ProRes RAW HQ rates it can be several terabytes. That changes every downstream decision:
- Cards and media — you need more cards or larger cards, and swaps happen at worse moments in the day.
- Backup — three copies of several terabytes is a very different overnight job from three copies of 400 GB. The 3-2-1 backup rule still applies; it just takes longer and costs more drives.
- Upload — at a sustained 100 Mbps upload, one terabyte takes roughly a full day to transfer. Raw can add days to a hand-off before the editor has seen a frame.
- Decode load — raw has to be demosaiced during playback, which is heavier than decoding a finished video file. Apple designed ProRes RAW for real-time multistream editing, but it also notes that raw playback needs more computation, because every frame must be demosaiced as well as decoded.
None of this is an argument against raw. It is an argument for deciding where on the day raw earns its cost, rather than leaving the camera in raw from getting-ready to sparkler exit.
When Raw Is Worth It on a Wedding Day
The best wedding raw workflows are selective. Raw goes where the light is hard to control and the moment cannot be repeated; efficient codecs go everywhere else.
| Part of the day | Raw? | Reasoning |
|---|---|---|
| Getting ready | Usually no | Long, low-stakes coverage; window light is manageable in log |
| Ceremony, A-camera | Often yes | Unrepeatable, often backlit, frequently mixed light in churches and venues |
| Ceremony, locked-off wide | Usually no | Long continuous take; storage cost is high and grading needs are simple |
| Couple portraits at golden hour | Often yes | Hero shots, high dynamic range, the footage most likely to anchor the highlight film |
| Speeches | Usually no | Long takes where audio and continuity matter far more than latitude |
| Reception and first dance | Case by case | Mixed LED and tungsten light is where raw white balance shines, but high-ISO noise inflates file size |
| Dance floor, handheld | Usually no | Fast, chaotic, high volume; efficient codecs keep cards and hand-off manageable |
A useful rule of thumb: if a shot is likely to make the highlight film and the light is difficult, raw is worth considering. If it is documentary coverage that mainly feeds the full-length film, a well-exposed log or 10-bit codec is usually the better trade.
There is one exception worth naming. If you are matching several camera brands, putting every camera in raw does not automatically match them. Different sensors still render colour differently, and a raw Canon clip next to a log Sony clip is still a matching job. Consistency across the day comes from a camera-profile plan, which we cover in detail in how to match color across multiple wedding cameras. Raw can make that matching easier; it does not replace it.
How to Expose and Set Up Raw So Your Editor Can Use It
Raw widens latitude, but it rewards consistent capture far more than it rescues inconsistent capture. The habits below matter more to the final film than the choice between ProRes RAW and BRAW.
Expose for highlights, then protect them. Because clipped sensor data is gone in any format, the priority in raw is the same as in log: keep the brightest important detail — the dress, the sky behind the arch, a window in the prep room — below clipping. Use your camera's waveform or zebras rather than the rear screen, which may be showing a monitoring LUT rather than the raw signal.
Still set a sensible white balance. White balance in raw is adjustable, but it is not meaningless. It is recorded as metadata and becomes the editor's starting point for every clip. A day shot at a consistent, roughly correct white balance means the editor's first pass lands close; a day shot on auto white balance, drifting between clips, means every clip starts from a different place.
Keep ISO and base settings consistent within a scene. Changing ISO mid-ceremony on one body while the other stays put is a matching headache in any format. In raw it also changes noise and file size, since ProRes RAW's constant-quality design encodes noisier images at higher data rates.
Match frame rate and resolution across bodies. Raw on one camera and a different frame rate or resolution on another turns a colour decision into a conform decision. Agree these before the day with every shooter, including second shooters on different brands.
- Pick one project frame rate and set every body to it.
- Decide which cameras record raw and which record a 10-bit codec, and write it down.
- Note whether any body records raw externally to a recorder, because those files will not be on the camera card.
- Jam timecode or plan a sync method; raw does not help with sync at all.
Handing Raw Footage to an Outsourced Editor
A raw hand-off needs more context than a normal one, because the editor is being asked to make decode decisions that the camera would otherwise have made. The goal of the hand-off note is to make those decisions explicit rather than guessed.
| Include in the hand-off | Why the editor needs it |
|---|---|
| Camera body and format per card or folder | Determines which decoder, plug-in or software version they need |
| Which cameras shot raw and which did not | Tells them where decode settings apply and where a log LUT applies |
| Intended log conversion, if you have a preference | Keeps raw clips grading consistently with your log clips |
| Whether to use the camera maker's ProRes RAW plug-in or standard processing | The two can look different on the same file |
| Your reference look or grade stills | Raw gives them more room to move; tell them where you want it to land |
| Known problem clips | Flags underexposed or clipped moments before they spend time on them |
| External recorder files and how they map to camera clips | Atomos files and in-camera proxies or scratch files must be matched up |
There are two sensible models for delivering raw to an outsourced editor, and the right one depends on how much grading control you want to keep.
Send raw, let the editor decode. This gives your editor the full latitude you paid for in storage. It suits partners who also handle the grade and who work in the same application you shot for. It needs the most upload time and the most careful compatibility check.
Decode once, send a mezzanine. You or an assistant decode the raw files to a high-quality log intermediate — ProRes 422 HQ in the camera's log curve is a common choice — with white balance and exposure set during that decode. The editor receives something that behaves like the log footage they already know, at a predictable data rate, with no plug-in dependency. You give up some latitude, but you keep your hand-off simple and your turnaround predictable.
For most wedding workflows the second model is under-used. It lets you make the one decision raw is best for — correcting white balance and exposure at source — and then hand over a normal file. Whichever model you choose, a proxy workflow sits comfortably on top of it; our wedding video proxy workflow guide covers how to generate and name proxies so they relink cleanly to either raw originals or a decoded mezzanine.
For BRAW specifically, remember that decode adjustments can be saved to sidecar files next to the media. If you have already adjusted clips in Resolve and want the editor to start from your settings, include those sidecar files in the transfer and keep the folder structure intact.
Common Raw Hand-Off Mistakes and How to Avoid Them
Most raw problems are not image problems. They are communication and logistics problems that happen to involve large files.
- Assuming the editor's software opens the format. Test with a real clip before the wedding. This is the single highest-value check in the whole workflow.
- Sending external recorder files without mapping them. An Atomos recording and the camera's internal scratch file of the same moment look like duplicates. Label which is the master.
- Shooting raw everywhere by default. A full day in raw can turn a next-day hand-off into a multi-day upload. Decide per part of the day.
- Leaving white balance on auto. Raw lets the editor fix it, but a drifting starting point multiplies their grading time across hundreds of clips.
- Mixing plug-in and standard ProRes RAW processing. If some clips are decoded with a camera maker's plug-in and others with standard processing, the same camera can look inconsistent. Pick one and say which.
- Forgetting the backup maths. Raw multiplies storage at every copy. Budget drives for all three copies before the season, not the night after the wedding.
- Treating raw as a rescue plan. Clipped highlights, missed focus and motion blur are identical in raw. Expose as carefully as you would for log.
When the transfer itself is the bottleneck, it is worth planning the upload route as carefully as the capture. Our guide to sending wedding footage to your editor compares transfer methods for multi-terabyte hand-offs, including when shipping a drive beats uploading.
The same checklist is how we approach raw at FrameFlow Edit, a white-label editing partner for wedding videographers and studios. We work with raw and log footage from the formats covered here, and we ask the same questions before a raw project that this guide recommends you ask any editor: which cameras shot which formats, whether you want us to decode from raw or start from a decoded log intermediate, and what reference look the grade should land on. If you are planning to shoot raw this season and want to confirm your formats before the wedding rather than after, send a test clip with your brief and we will tell you exactly how we will handle it. Pricing depends on the deliverables and footage volume, so the fastest route is to get a quote with your camera list attached.
Raw Wedding Video: Frequently Asked Questions
Is raw video worth it for wedding videography?
For selected parts of the day, often yes; for the whole day, usually not. Raw earns its storage cost on unrepeatable moments in difficult light — a backlit ceremony, golden-hour portraits, a reception under mixed LED and tungsten — where adjustable white balance and extra latitude improve the final grade. For long documentary coverage such as getting ready, speeches and the dance floor, a well-exposed 10-bit log codec usually gives nearly the same result at a fraction of the storage and upload time.
How much more storage does raw video use than H.265?
Substantially more, and it varies with content. Apple states that ProRes RAW generally falls between ProRes 422 and ProRes 422 HQ in data rate, which at UHD 24p works out to roughly 471 to 707 Mbps — about 3.5 to 5.3 GB per minute, and about a quarter more at 29.97p. A 150 Mbps H.265 file uses about 1.1 GB per minute. Because ProRes RAW encodes noisy or highly detailed images at higher data rates, a high-ISO reception can produce larger files than the same length of daylight footage.
Can my editor fix a blown-out sky if I shot raw?
No. Raw stores the sensor data before processing, but if the sensor itself clipped, there is no data beyond that point to recover. Raw gives more room to recover shadows and adjust white balance, and it can help with highlights that were bright but not clipped. Protect your highlights with waveform or zebras exactly as you would when shooting log.
Should I send my editor raw files or transcode them first?
It depends on who is grading. If your editor also grades and uses software that natively reads your format, sending raw preserves the most flexibility. If you want to control white balance and exposure yourself, or you need a faster, more predictable hand-off, decoding once to a high-quality log intermediate such as ProRes 422 HQ gives the editor a familiar file with no plug-in dependency. Either way, confirm your choice in the hand-off note.
What happens if my editor's software cannot open my raw format?
They lose time before the edit starts — installing a decoder or plug-in, updating the application, or asking you to transcode. On a Mac, Adobe's N-RAW and R3D NE support requires Apple silicon, and Windows editors need Apple's ProRes RAW decoder installed for ProRes RAW in Premiere. The prevention is simple: send a short test clip in your exact format before the wedding and have your editor confirm it opens and plays correctly.
Does shooting raw make multicam colour matching automatic?
No. Raw gives each camera a more flexible starting point, but different sensors still render colour differently, and a raw clip next to a log clip from another brand still needs matching. Consistent exposure, white balance and a shared camera-profile plan across every body matter more for matching than the choice of raw format.