Camera original
R3D remote review.
Full debayer, no proxy.
Ship a drive and lose days. Send H.264 dailies and lose the image. Or upload the R3D and let your client play the negative at full debayer, the day you offload.
No credit card required. Cancel any time.
Updated September 2026
The dailies chain
Your client judges an image
three translations from the sensor.
Three renders separate the sensor from your client’s screen, and you signed off on exactly one of them. Each box below is a place where image quality got decided.
The sensor
Light becomes a RAW frame. Exposure, white balance and highlight recovery stay open, waiting for the grade. This is the image the job is selling.
REDCODE R3D
The one compression you chose: HQ, MQ or LQ on the camera menu, sized so the negative survives post. Your call, made on set.
The dailies transcode
A preset picks the debayer quality, the downscale and the H.264 encode. Fast to render, cheap to move, no longer your image.
The platform re-encode
The host transcodes the daily again into its own ladder. Vimeo caps 4K playback at 22 Mbps; Frame.io serves an H.264 or HEVC proxy.
The chain strips out exactly what a review exists to judge. Fine texture in skin, fabric and foliage lives in the detail a lossy encoder discards first; MDN’s codec guide states the rule plainly: the more compression, the more loss of detail and fidelity. Sensor noise on a Komodo is fine grained and mostly pleasant. After two more encodes it either smears into plastic or clumps into blotches, so a client who says the shot looks soft or noisy is usually describing the codec, not the negative.
Graded stills are the usual patch, and they fail on the axis that matters: time. Noise is a moving phenomenon; a frozen frame of grain says nothing about how it behaves at 24 fps. Compression artifacts crawl. Motion cadence, shutter feel, how a grade holds through a lighting change: none of it survives the freeze, and a note written against a still is a note about a picture, not a film.
None of this is RED specific. The same chain runs under every RAW format, and the BRAW version of the problem has its own page. What is RED specific is the weight of the negative, so start there.
The negative
What an R3D weighs,
straight from the RED guides.
RED publishes a record rate for every body, frame size and quality setting. Two conclusions fall out: the negative is heavy, and a modern uplink can carry it.
446 MB/s
V-Raptor 8K HQ
REDCODE record rate at 8K 17:9, 24 fps
3,568 Mbps
Same rate, player units
The number a streaming pipeline has to survive
30 min
Per 512 GB mag
Komodo 6K HQ record time on one CFast card
3x
ProRes 4444 XQ vs R3D
RED: 8K XQ takes nearly three times the data of 8K R3D at 5:1
Data rates read from RED operation guides at docs.red.com, September 2026. Mbps computed at 8 bits per byte. RED lists Komodo figures as approximate maximums; one 512 GB CFast card records about 30 minutes at Komodo 6K HQ.
Rates like these are the reason REDCODE exists. RED’s own comparison paper, from November 2020, puts 8K R3D at 5:1 “somewhere between ProRes 4444 and 422HQ at 4k” and notes that 8K ProRes 4444 XQ takes nearly three times the data of the same R3D. The negative was engineered to travel. A full mag at Komodo 6K HQ is about half a terabyte for 30 minutes; a selects reel for review is a fraction of that, which is exactly the size of problem a resumable upload solves.
The shuttle drive
Honest about the image.
Merciless about the calendar.
A courier moves the real negative, and nothing else about the method survives contact with an iterative review.
Transit, twice per round
The drive spends a day or two in a van each way, every review cycle. International adds customs. Three rounds of notes turns into two weeks of watching tracking numbers.
Serial, not parallel
Nobody sees frame one until the drive lands, and notes wait for the return leg or an email thread detached from timecode. The review loop cannot overlap the edit.
Custody surrendered
Every drive you ship is a full-quality copy you no longer control, on a shelf you cannot see, long after the job wraps.
Drives keep one legitimate job: the bulk handoff. A finished project archive, or a whole shoot’s rushes headed to a colorist in one lump, rides better on a courier than through anyone’s uplink. What a drive cannot do is carry a conversation. Review is iterative by nature, and iteration over a courier runs at the speed of the van.
The native path
Stream the R3D itself.
15,000 Mbps of headroom.
The uncompressed.io macOS app decodes RED RAW natively and plays camera masters up to 15,000 Mbps. Upload the R3D you offloaded, and the person at the other end plays that file. Full debayer, no proxy in the pipeline.
uncompressed.io macOS app, R3D native
V-Raptor 8K HQ, the R3D itself
Frame.io 4K playback, H.264 proxy
Vimeo 4K playback cap
Frame.io playback measured, August 2026. Vimeo cap read from vendor documentation, September 2026. The R3D bar is the V-Raptor 8K HQ record rate from RED's guide, converted at 8 bits per byte. The two proxy bars are drawn at a minimum visible width; to scale they would be thinner than a pixel.
Full-rate playback changes which conversations can leave the suite. Noise reduction sign-off, texture on a beauty job, whether 6K Raptor material survives a punch-in: these are negative-quality questions, and a 4K proxy ladder cannot host them. Streamed native, they happen the day the card is offloaded, with timecoded comments and drawings on the frame instead of a phone call about a file name.
One boundary stays fixed: no browser decodes RAW, here or anywhere. For producers and agency reviewers on Windows or phones, export an HEVC 10-bit twin beside the master and share the web link. It streams byte for byte with no re-encode; browser hardware decoders top out around 300 to 400 Mbps, and 100 to 150 Mbps is the safe no-drop band. Full debayer for the people making image decisions, a faithful master stream for everyone else.
When the drive still wins
Four transports
Dailies, stills, drives,
or the negative itself.
Same footage, four ways to show it. Only the drive and the stream carry the negative, and only one of them carries it this week.
Custody column for uncompressed.io: password, unlisted or public per video, expiring access, and original-file downloads only when the owner switches them on.
Card to client
From the mag
to the review room.
Four steps and no transcode anywhere. RED RAW decode is native in the macOS app, so the bytes you offload are the bytes your client plays.
Offload the mag
Copy the R3D clips off the card into your project structure, exactly as you already do. The dailies render queue is not part of this pipeline.
Upload the clips
Drag the R3D files in. Uploads are resumable, survive navigation, and take masters up to 50 GB per file.
Send one link
The share link is the sign-in. Your client opens the room in the macOS app and plays the R3D at full debayer: no account, no RED software.
Pull notes into the NLE
Timecoded comments and frame drawings come back as markers through a Resolve script, a signed Premiere panel, or a one-drag Final Cut bundle.
Around playback sits the review layer: per-version red and green approvals, versions and aspect ratios side by side, and deliverables in the same room, so sign-off lands on a specific cut. Notes return to the timeline through the NLE sync tools rather than an email thread, with drawing stills placed next to their markers.
For material under embargo, the same link carries the controls: password or unlisted access, expiry dates, session watermarks, and forensic invisible watermarking that survives screen recording, detailed on the security page. Every feature ships on every tier, including Free. Storage is the only meter.
Questions
Frequently asked
Can a client play R3D files without RED software or an NLE?
Yes. The uncompressed.io macOS app decodes RED R3D natively, alongside BRAW, N-RAW and ProRes, and plays camera masters up to 15,000 Mbps. The client opens the review link, which is also the sign-in, and plays the R3D at full debayer with no account, no REDCINE-X and nothing to configure.
How do I share RED footage with a client on Windows or a phone?
No browser decodes RAW, so export an HEVC 10-bit twin beside the master and share the web link from the same review room. It streams byte for byte with no re-encode. Hardware decoders in browsers top out around 300 to 400 Mbps, and 100 to 150 Mbps is the safe band for playback without dropped frames.
What data rate is REDCODE R3D?
RED's operation guides list Komodo 6K at up to about 280 MB/s in HQ, and V-Raptor 8K VV at 446 MB/s HQ, 312 MB/s MQ and 195 MB/s LQ at 24 fps. In streaming units the heaviest of those is about 3,568 Mbps, well inside the app's 15,000 Mbps playback ceiling.
Is streaming R3D safer than shipping a drive?
A shipped drive is a full-quality copy you no longer control. A streamed link stays revocable: set a password or unlisted access, add an expiry date, and rely on session watermarks plus forensic invisible watermarking that survives screen recording, so a leaked capture still carries its mark.
How much storage does a RED review workflow need?
Plan around the larger tiers: Max is $75 per month with 1.5 TB hot plus 1 TB cold, and Vault is $250 per month with 2 TB hot plus 2 TB cold. Each add-on is $175 per month for another 1 TB hot plus 1 TB cold, with overage at $40 per TB hot and $20 per TB cold. Keep the active review set hot, move wrapped jobs to cold, and test the pipeline first on the free 1 GB tier.
Show them the negative
Upload an R3D, send one link, and run a full-debayer review the same day you offload. Storage is the only meter; every feature is on every plan.
Sources
- 1.RED KOMODO Operation Guide, R3D Quality (docs.red.com) (Komodo 6K data rates and CFast recording times)
- 2.RED V-RAPTOR 8K VV Operation Guide, R3D Quality (docs.red.com) (V-Raptor 8K and 6K data rates)
- 3.RED, Benefits and Evolution of REDCODE RAW (PDF, docs.red.com) (REDCODE vs ProRes data comparison, November 2020)
- 4.Guidelines for determining playback resolution (Vimeo Help Center) (4K playback capped at 22 Mbps)
- 5.What are my assets converted to when uploaded (Frame.io Support) (uploads served as H.264/H.265 MP4 proxies)
- 6.Web video codec guide (MDN Web Docs) (lossy coding: more compression, more loss of detail and fidelity)