REDCODE RAW debuted in 2007 with the RED ONE, RED Digital Cinema’s first production camera, at a moment when practical 4K raw digital cinema capture barely existed outside specialized, far more expensive systems. R3D made raw sensor-level capture financially and operationally viable for independent and mid-budget productions, and it has remained RED’s core recording format across every subsequent camera generation \u2014 EPIC, SCARLET, the DSMC2-era WEAPON and RAVEN, and the current DSMC3 line including KOMODO and V-RAPTOR.<\/p>
What makes R3D fundamentally different from a delivery codec like H.264 is that it isn’t storing finished pixels at all \u2014 it’s storing compressed raw Bayer-pattern sensor readout plus a large set of shooting metadata (ISO, white balance, lens data, RED’s own color science settings). Debayering, white balance, and color grading are all applied non-destructively afterward in post-production software, and the original sensor data is always recoverable, which is exactly why cinematographers shoot raw in the first place \u2014 creative decisions made on set don’t permanently bake into the file.<\/p>
That flexibility comes at a direct cost to a DAM: R3D files are large, and previewing them at all requires real decoding and debayering work, not simple thumbnail extraction. Standard practice \u2014 and the only practical approach for browsing at scale \u2014 is to generate ProRes or H.264 proxies via REDCINE-X PRO or RED’s REDLINE transcoder immediately at ingest, keeping those proxies as the everyday browsing and rough-cut asset while the R3D itself stays untouched as the archival master. Any DAM handling R3D natively needs either RED’s SDK integrated directly or a transcoding step built into the ingest pipeline, since generic video libraries won’t decode it out of the box.<\/p>","protected":false},"excerpt":{"rendered":"
R3D is RED Digital Cinema’s proprietary camera-native raw video format, storing compressed sensor data and shooting metadata rather than fully rendered pixels, requiring specialized software to preview or edit.<\/p>\n","protected":false},"author":0,"featured_media":0,"template":"","meta":{"footnotes":"","faq":[{"question":"Is R3D a video codec like H.264, or something different?","answer":"It's a camera-native raw capture format, not a finished-video codec. R3D stores compressed sensor data and metadata rather than fully debayered, rendered pixels, with color and exposure decisions applied later in post rather than baked in at capture."},{"question":"Can a DAM generate a thumbnail preview of an R3D file directly?","answer":"Not without real decoding work \u2014 because R3D holds raw sensor data rather than rendered pixels, generating even a basic thumbnail requires debayering, which needs RED's SDK or RED-aware software rather than a generic image\/video preview library."},{"question":"What's the standard proxy workflow for R3D in a production pipeline?","answer":"Generate lower-resolution ProRes or H.264 proxies via REDCINE-X PRO or RED's REDLINE transcoder immediately at ingest, edit and browse using those proxies, then relink to the full-resolution R3D only for final color grading and finishing."},{"question":"Which editing software supports R3D natively without a plugin?","answer":"DaVinci Resolve and Adobe Premiere Pro (since CS6) both offer native R3D support built directly into the application, with GPU-accelerated debayering, requiring no separate RED plugin."},{"question":"Is R3D an open format, or proprietary to RED cameras?","answer":"It's proprietary to RED Digital Cinema, though RED does publish a software development kit that lets third-party applications read and decode R3D files, which is how tools like Resolve and Premiere Pro implement native support."},{"question":"Why are R3D files so much larger than typical delivery video files?","answer":"Because they preserve raw sensor data at high bit depth rather than compressed, finished pixels \u2014 that's precisely what gives editors and colorists the latitude to adjust exposure and white balance non-destructively in post, but it comes at a real storage cost compared to a rendered H.264 or ProRes export."},{"question":"What happens if we only archive the H.264 proxy and delete the original R3D?","answer":"You permanently lose the raw sensor data and the non-destructive grading flexibility that's the entire point of shooting REDCODE RAW \u2014 proxies are meant for browsing and rough editing, not as a substitute archival master for footage that may need re-grading or re-mastering later."},{"question":"Does R3D support show up in newer non-RED cameras?","answer":"Yes, in a limited way \u2014 RED has licensed a newer variant called R3D NE to some third-party camera makers, such as Nikon's ZR, extending REDCODE RAW capture beyond RED's own camera line."}],"checked_date":"2026-08-07","sources":[{"statement":"The RED ONE camera, launched in 2007, introduced REDCODE RAW capture.","source_name":"Wikipedia \u2014 RED Digital Cinema","url":"https:\/\/en.wikipedia.org\/wiki\/Red_Digital_Cinema","checked":"2026-08-07"},{"statement":"RED's own documentation on the design and benefits of REDCODE RAW.","source_name":"RED Digital Cinema \u2014 Benefits & Evolution of REDCODE RAW (PDF)","url":"https:\/\/docs.red.com\/955-0179\/REV-B\/Benefits%20&%20Evolution%20of%20REDCODE%20RAW.pdf","checked":"2026-08-07"},{"statement":"RED has extended REDCODE RAW via R3D NE to third-party licensed cameras.","source_name":"RED Digital Cinema Support \u2014 R3D NE and the Expansion of REDCODE RAW","url":"https:\/\/support.reddigitalcinema.com\/hc\/en-us\/articles\/45719402183059-R3D-NE-and-the-Expansion-of-REDCODE-RAW","checked":"2026-08-07"}],"kicker":"","fact_checker":0,"reading_time":0,"revisions":[],"seo_title":"","seo_description":"","noindex":false,"ext":"r3d","full_name":"REDCODE RAW (RED Digital Cinema's camera-native raw video format)","vendor_name":"RED Digital Cinema","introduced":"2007","container_notes":"R3D wraps compressed raw Bayer-pattern sensor data plus extensive shooting metadata \u2014 ISO, white balance, color science, lens data \u2014 captured at the moment of recording; debayering, white balance, and grading are all applied non-destructively later in post, with the underlying raw sensor data always recoverable. It is a proprietary format tied to RED's camera ecosystem, though RED publishes an SDK that lets third-party software read and decode R3D files.","open_with":[{"platform":"Cross-platform NLE (Mac\/Windows\/Linux)","how":"DaVinci Resolve offers native R3D support, including GPU-accelerated debayering for real-time playback and grading without a separate plugin."},{"platform":"Windows \/ macOS","how":"REDCINE-X PRO, RED's own free transcoding and pre-editorial application, is the reference tool for organizing R3D clips and generating proxies before they reach an NLE."},{"platform":"macOS \/ Windows","how":"Adobe Premiere Pro has offered native R3D support built directly into the application since Premiere Pro CS6, requiring no separate plugin."},{"platform":"Proxy generation","how":"RED's REDLINE transcoder or REDCINE-X PRO generate lower-resolution ProRes or H.264 proxies for lightweight browsing and offline editing, relinking to full-resolution R3D only for final color and finishing."}],"archive_advice":"R3D files are large and computationally expensive to decode natively, so a DAM cannot rely on browser or thumbnail-generator-level preview without a dedicated decode path \u2014 generate ProRes or H.264 proxies at ingest for browsing while retaining the original R3D as the true archival master, since it's the only version that preserves the full sensor data and non-destructive grading flexibility. Because R3D decoding depends on RED's SDK or RED-licensed software, confirm that whatever DAM or transcoding pipeline is in use has current RED SDK support rather than assuming generic video tools will read it.","related":[2935,2631,2930,2632,2933,2624],"tool_link":""},"silo":[23],"class_list":["post-2934","format","type-format","status-publish","hentry","silo-formats"],"_links":{"self":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/format\/2934","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/format"}],"about":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/types\/format"}],"version-history":[{"count":1,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/format\/2934\/revisions"}],"predecessor-version":[{"id":3401,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/format\/2934\/revisions\/3401"}],"wp:attachment":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/media?parent=2934"}],"wp:term":[{"taxonomy":"silo","embeddable":true,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/silo?post=2934"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}