Camera RAW to a viewable master
How to share BRAW or RED footage with clients
Finish it first, then stream the master.
Camera RAW does not belong in a browser. The file a client actually reviews is a high-bitrate graded export, and the only question worth arguing about is how much that export gives away. Here is the route from a .braw or an .R3D to a 10-bit HEVC master that is stored and served exactly as you exported it, and the point at which a courier is still the right answer.
Video hosting for filmmakers · 5 GB free · Paid plans from USD 9/month
Updated September 2026
The constraint nobody can route around
No browser decodes camera RAW,
so stop trying to send it there.
This is not a policy, a plan limit or a rule anyone here applies. It is what a browser is. A .braw needs Blackmagic’s own decoder, which Blackmagic ships in DaVinci Resolve, in the free Blackmagic RAW Player for Mac, Windows and Linux, and in an SDK that developers build against. None of that is in a web page. REDCODE is the same shape of problem with a different vendor. So the deliverable a client reviews is never the negative: it is the picture you made from it.
That sounds like a limitation and it is mostly a clarification. Camera RAW is a set of decisions that have not been made yet: a debayer, a white point, a tone curve, an exposure read. A client reviewing a cut is not reviewing those. They are reviewing a film. The right file to put in front of them is the one where those decisions are already made, made by you, at a bitrate high enough that nothing else takes them apart.
Where it stops being a clarification is grading and conforming. If the person at the other end is going to touch the image, they need the negative, not a picture of it. That case has its own answer, further down this page, and it is not always this website.
Camera RAW decode requirements read from Blackmagic Design's Blackmagic RAW product page, fetched 7 September 2026. The macOS app supports R3D, BRAW, N-RAW and ProRes on compatible Macs; test a short clip on the recipient's machine before a real review depends on it.
Why finishing first is not a compromise
The negative is measured in gigabytes a minute;
the master is measured in gigabytes.
Both vendors publish exact record rates, so this part is arithmetic rather than opinion. Read the row for the setting you actually shot, then read the last column, which is how much of it fits inside the 50 GB per-file ceiling here.
446 MB/s
V-RAPTOR 8K 17:9, HQ
RED's published record rate at 24 fps
578 MB/s
URSA Mini Pro 12K, BRAW 5:1
Blackmagic's published rate, full sensor, 24 fps
6 GB
A ten-minute HEVC master
At the 80 Mbps baseline we recommend
50 GB
Per file, the only ceiling
No bitrate ceiling and no resolution ceiling exist
RED figures from the V-RAPTOR 8K VV and KOMODO operation guides at docs.red.com; RED lists the KOMODO rates as approximate. Blackmagic figures are the full-sensor constant bitrate rates in the URSA Mini Pro 12K technical specifications. All fetched 7 September 2026, all at 24 fps or 23.98 fps as published. One minute and minutes-under-50-GB are computed from those rates. Blackmagic's constant quality settings remove the upper data limit entirely, so Q0 on the 12K sensor is published as a range of 289 to 1,156 MB/s depending on the image.
Put the two halves beside each other. Ten minutes of V-RAPTOR 8K HQ is about 268 GB. The same ten minutes exported at the 80 Mbps HEVC baseline is about 6 GB. That is not a fair fight, and it is not supposed to be: one is the material every future decision comes out of, and the other is the one file a client clicks. The mistake is sending the first one when the question on the table only needed the second.
It also settles the storage question before it becomes an argument. A review library of graded masters is small. Twelve finished films at 6 GB each is 72 GB, which sits inside a 100 GB plan with room left. A review library of camera originals is not small, and the honest place for the bulk of what you shot is the local disks and the RAID the edit is already running from.
The route
Card to client,
in four steps.
Nothing exotic. The only part most people get wrong is the third step, where a habit learned on platforms that re-encode makes them export far smaller than they need to.
Conform and grade from the camera original
The .braw or .R3D stays where it belongs, in post, on your storage. Every decision the RAW held open gets made here, by you, on a display you trust, rather than implicitly by a preset in a dailies queue.
Export the finishing master
ProRes 422 HQ, ProRes 4444 or DNxHR, for the archive and for anyone downstream who is going to touch the image again. This one is a file to hand over, not a file to watch: those are not browser playback formats, so nobody reviews from it in a tab.
Export the review master
10-bit HEVC in MP4 or MOV, at a real bitrate. This is the file the client watches and comments on. Nothing here re-encodes it, so the number you type into the export dialog is the number that reaches them.
Upload once, send one link
The player streams the exact bytes of that export. Notes come back timecoded against a specific version, and the per-film download switch hands over the original file only when you turn it on.
The third step deserves the extra sentence. On a platform that builds a rendition ladder, exporting above its ceiling is wasted effort: the ladder re-encodes your file down to its own target and your careful bitrate never leaves your machine. That is why so many filmmakers have quietly trained themselves to export small. Here the file is stored as uploaded and served as uploaded, with no encode step at either end, so the bitrate is a real decision again rather than an offering to somebody else’s encoder.
These are our own export recommendations, published for members. They are not vendor figures and they are not caps: no bitrate ceiling and no resolution ceiling exist here, and the only limit on a file is its size, 50 GB per upload.
Before you promise a browser will play it
The honest concession
When the negative has to travel,
a courier is still the right answer.
Everything above assumes the person at the other end is judging a film. If they are grading it, conforming it, or finishing it, they need the RAW, and a 10-bit HEVC master is the wrong file no matter how good it looks.
Ship the drive
A whole shoot's mags headed to a colorist ride better on a courier than through anyone's uplink. A day of V-RAPTOR 8K HQ is roughly 268 GB for every ten minutes recorded, and on a deadline the van frequently beats the upload. The cost is real and permanent: a full-quality copy is now on a shelf you cannot see.
The macOS app route
The macOS app supports R3D, BRAW, N-RAW and ProRes on compatible Macs, so a camera original can be reviewed without a drive in transit. Playback depends on the codec, hardware, storage and file availability, which is a real caveat, not boilerplate: test a short clip on the recipient's Mac before a review depends on it.
Store it, hand it over
Nothing here rejects a camera original at upload. There is no codec allowlist and no container check; the only upload rejection is size, at 50 GB per file. So a .braw or an .R3D can be stored exactly as it is and handed over through the download switch. It still will not play in a browser, and no amount of hosting changes that.
Read those three honestly and the split is obvious. The graded HEVC master goes up, gets a link, and carries every conversation about the cut, the pacing and the sign-off. The camera originals stay on your storage for the duration of post, and travel only to the one or two people who are going to work on the image, by whichever route gets them there fastest. On a Friday deadline with four terabytes of mags, that route is a courier, and this page will not pretend otherwise.
Two sibling guides go deeper on the native path per format: BRAW client review and R3D remote review. If your question is about the handoff at the end of the job rather than the review in the middle of it, delivering final files to clients covers what a complete delivery contains. And if the person reviewing is a colorist, video hosting for colorists takes up where this page stops.
What it costs to keep the link alive
Priced by what you store,
not by how often it is watched.
A review master that lives online for the length of a job is a small, predictable bill, and it does not grow because the client watched it eleven times or forwarded it to a committee.
Storage is the only meter. There are no bandwidth caps, no per-view charge, and external client viewers never need a paid seat, so a film shown to a room does not cost more than a film shown to one person. Starter is free: 5 GB of hot storage, one film at a time, no credit card, which is enough to test the whole chain with one real export before you pay anything. The paid ladder is Lite at $9 a month or $90 a year for 100 GB, Pro at $25 or $250 for 500 GB, Max at $75 or $750 for 1.5 TB hot plus 1 TB cold, and Studio at $250 or $2,500 for 2 TB hot plus 2 TB cold. Beyond a plan, storage blocks are $40 per TB hot and $20 per TB cold a month, and an extra seat is $25 a month. The full rate cards are on the pricing page.
Sized against the numbers above, a year of finished work is not a storage problem. Twelve ten-minute films at the 80 Mbps baseline is about 72 GB of review masters. The pressure comes entirely from camera originals, which is the other reason the workflow on this page starts with an export rather than an upload.
Questions
Frequently asked
Can a client watch BRAW or R3D in a browser?
No. No browser decodes camera RAW, so there is no version of this that works in a tab. Blackmagic RAW playback comes from Blackmagic's own SDK, which lives in DaVinci Resolve, in the free Blackmagic RAW Player and in applications built against it. The macOS app supports R3D, BRAW, N-RAW and ProRes on compatible Macs; playback there depends on the codec, hardware, storage and file availability, so test a short clip on the recipient's Mac. For browser review, use a supported H.264, HEVC or AV1 export.
Can I upload a .braw or an .R3D file at all?
Yes. Nothing here inspects the codec or the container on the way in, and the only upload rejection is size: 50 GB per file is the published ceiling. The file is stored exactly as you uploaded it and can be handed over through the per-film download switch. What it is not is a browser playback format, so treat it as a file you store and hand over rather than something a client watches.
What should I export for client review?
A 10-bit HEVC master in MP4 or MOV, at a real bitrate. Our own published recommendation is 40 to 80 Mbps for HEVC at 4K 24 or 30, and 50 to 100 Mbps at 4K 60, with a single baseline of 80 Mbps 10-bit HEVC covering 1080p through 4K. Those are our recommendations, not limits: there is no bitrate ceiling and no resolution ceiling here, so you never have to shrink an export to fit a platform.
Will a 10-bit 4:2:2 export play for my client?
That is not documented, in either direction. No vendor documents 10-bit 4:2:2 HEVC decode in a browser video element, so nobody can honestly promise you it plays or that it fails. Our half is settled: we never re-encode, so a 4:2:2 file is stored and served exactly as you exported it. Export thirty seconds, upload it, and have the client open the link on the machine they will actually review on before you commit the whole film.
How much of a RED or Blackmagic shoot fits in one file?
At RED's published V-RAPTOR 8K 17:9 HQ rate of 446 MB/s, 50 GB holds about two minutes. At the KOMODO's 6K 17:9 LQ rate of about 110 MB/s, about eight minutes. On an URSA Mini Pro 12K at Blackmagic RAW 18:1, 160 MB/s, about five and a half minutes. Takes and selects fit comfortably; a full mag does not, which is exactly why the graded export is the thing you send.
Do I have to give the client the original file?
No. Download is a switch on each individual film, on every plan including the free one. Left off, no download link is ever generated. Turned on, the viewer gets the exact object you uploaded, byte for byte, with nothing converted or optimised on the way out.
Which plan does a review workflow like this need?
Start on Starter: free, 5 GB of hot storage, one film at a time, no credit card. Paid plans are Lite at $9 a month or $90 a year for 100 GB, Pro at $25 or $250 for 500 GB, Max at $75 or $750 for 1.5 TB hot plus 1 TB cold, and Studio at $250 or $2,500 for 2 TB hot plus 2 TB cold. Storage is the only meter: there are no bandwidth caps, no per-view charge, and external client viewers never need a paid seat.
Send the master, keep the negative
Export one HEVC master, upload it to the free 5 GB tier and send a client the link. The player streams the exact bytes you exported, and the download switch hands over the original file only when you turn it on.
Sources
- 1.RED V-RAPTOR 8K VV Operation Guide, R3D Quality (docs.red.com) (HQ, MQ, LQ and ELQ data rates at 8K and 6K 17:9, 24 fps, fetched 7 September 2026)
- 2.RED KOMODO Operation Guide, R3D Quality (docs.red.com) (6K 17:9 23.98 fps data rates and 512 GB CFast recording times, fetched 7 September 2026)
- 3.Blackmagic Design: URSA Mini Pro 12K technical specifications, Blackmagic RAW data rates (constant bitrate and constant quality rates at 12K, 8K and 4K full sensor, 24 fps, fetched 7 September 2026)
- 4.Blackmagic Design: Blackmagic RAW product page (the four constant bitrate variations, the Q0 to Q5 constant quality options, and the publicly documented .braw SDK, fetched 7 September 2026)
- 5.uncompressed.io pricing: plans, storage blocks and the storage-only meter
