--- title: "ARRIRAW HDE Workflow: How High Density Encoding Changes the DIT Offload Pipeline" author: "Cutsio Team" date: "2026-05-08" lastmod: "2026-05-08" category: "Storage & Performance" excerpt: "Learn how ARRIRAW High Density Encoding (HDE) compression works in practice, how it affects DIT offload times and storage budgets, and how HDE-compressed ARRIRAW integrates with cloud dailies pipelines." tags: ["ARRI RAW","ARRIRAW","HDE","High Density Encoding","Codex","DIT Workflow","Cloud Dailies","Post Production","ARRIRAW HDE","ARRI Compression"] --- ## What is ARRIRAW High Density Encoding and how does it affect the DIT pipeline? ARRIRAW High Density Encoding (HDE) is a lossless variable-bit-rate compression applied to ARRIRAW files during the offload process, reducing file sizes by approximately 40% with no quality loss. HDE is not a camera recording format — it is a post-capture compression step performed in software like Codex Device Manager or Pomfort Silverstack during card offload. HDE-compressed ARRIRAW is designed to behave like standard ARRIRAW in supported post applications because decompression is handled by ARRI/Codex-compatible tooling. The distinction between HDE and formats like ARRICORE is critical. ARRICORE is an in-camera RGB recording format that records smaller files directly. HDE is a lossless re-compression of existing ARRIRAW data that happens after the card is removed from the camera. HDE does not change the sensor data, the color science, or the metadata. It reduces the storage footprint of standard ARRIRAW by applying a variable-bit-rate compression algorithm that is mathematically lossless — every original pixel value is recoverable. For DITs, HDE means approximately 40% less storage media required per production, faster offload verification times, and lower hard drive costs. For cloud dailies, HDE means smaller uploads and faster upload windows because the pipeline transfers less data. Transcode behavior should be verified with the target platform before the shoot. Working with raw camera footage? Check out [How to Build a Searchable Library From ARRIRAW, RED R3D, and ProRes Footage](/blog/how-to-build-searchable-library-from-arriraw-red-r3d-prores-footage). Streamline your workflow with [How to speed up video editing workflow 10x](/blog/how-to-speed-up-video-editing-workflow-10x). ## How does HDE compression actually work? HDE is applied during the offload process using Codex Device Manager on macOS. The compressed files use a variable-bit-rate encoding that analyzes each frame and allocates more bits to complex frames and fewer bits to simple frames. The lossless nature means every original pixel value from the ARRIRAW sensor readout is preserved — no data is discarded. | Aspect | Standard ARRIRAW | ARRIRAW HDE | | :--- | :--- | :--- | | Compression type | None (uncompressed sensor data) | Lossless variable-bit-rate | | Applied when | On-camera | During offload (Codex Device Manager) | | Average size reduction | Baseline | ~40% smaller | | Quality impact | None (source) | None (lossless) | | NLE/color compatibility | Native | Transparent (decompressed by ARRI SDK) | | File extension | .ari, .mxf, .arx | Same (.ari, .mxf) | | Verification required | CRC check | CRC check (including HDE integrity) | The compression ratio varies by scene content. A flatly-lit interview with minimal motion might compress 50%. A complex VFX plate with fine detail and noise might compress 30%. The 40% average is based on real-world data from productions using HDE across multiple Alexa camera models. HDE uses a fast-fail CRC verification method. If any frame has a CRC mismatch, the offload fails on that clip — there is no partial or degraded HDE file. This ensures data integrity but means the DIT must re-offload any clip that fails verification. ## What hardware and software do you need for an HDE workflow? HDE compression requires specific hardware and software. It is not available on all platforms or with all copy tools. | Requirement | Specification | | :--- | :--- | | Operating system | macOS only (HDE is not supported on Windows) | | Software | Codex Device Manager (latest version) | | Copy tools | Hedge Offshoot Pro, Pomfort Silverstack, or YoYotta | | Media readers | Codex Compact Drive Reader TB3, USB-C, or SXR Capture Drive Dock | | Camera support | Alexa 35, Alexa Mini LF, Alexa LF, Alexa 65, Alexa SXT | | File formats | ARRIRAW .mxf and .ari (HDE is not available for ProRes) | The HDE process runs inside Codex Device Manager during the offload workflow. The DIT connects the Compact Drive reader, launches Device Manager, and selects HDE encoding as an option in the offload preset. The software reads the card, applies HDE compression to each clip, writes the compressed files to the target drive, and performs CRC verification simultaneously. Hedge Offshoot Pro and Silverstack integrate with Codex Device Manager for HDE offloads. These tools handle the file management and metadata while Device Manager handles the HDE compression and verification. ## How does HDE change the per-day storage calculation? HDE reduces the total storage requirement per shoot day by approximately 40%. For a production that would require 40 TB of ARRIRAW storage across a 20-day shoot, HDE reduces that to approximately 24 TB. | Production Scale | Standard ARRIRAW | ARRIRAW HDE (40% smaller) | Savings | | :--- | :--- | :--- | :--- | | 10-day commercial, 3 TB/day | 30 TB | 18 TB | 12 TB | | 20-day feature, 4 TB/day | 80 TB | 48 TB | 32 TB | | 40-day feature, 3.5 TB/day | 140 TB | 84 TB | 56 TB | | 60-day series, 5 TB/day | 300 TB | 180 TB | 120 TB | Storage media costs scale linearly with these reductions. At approximately $300 per TB for enterprise SSDs, a 20-day feature saves roughly $9,600 in drive costs. For productions shipping drives to post production facilities, the reduced weight and volume also lower shipping costs. The DIT should calculate storage requirements with HDE factored in before production begins. A 2 TB Codex Compact Drive that holds approximately 45 minutes of standard ARRIRAW at 4.6K Open Gate holds approximately 75 minutes of HDE-compressed ARRIRAW at the same resolution, changing card rotation strategy significantly. ## Does HDE affect cloud dailies upload and transcoding? HDE-compressed ARRIRAW files are approximately 40% smaller than standard ARRIRAW, which directly reduces cloud upload times on the same internet connection. A shoot day generating 3 TB of standard ARRIRAW produces approximately 1.8 TB of HDE-compressed ARRIRAW — a meaningful difference when uploading over a 200 Mbps hotel or production office connection. Cutsio.s enterprise camera-original ingestion can accept HDE-compressed ARRIRAW when enabled for the production. The DIT uploads the native .mxf or .ari files, and Cutsio generates review assets while retaining the original HDE files for conform and download. The upload workflow: 1. Offload cards with HDE compression enabled in Codex Device Manager 2. Verify all clips pass CRC verification 3. Upload HDE-compressed files to Cutsio through the enterprise add-on 4. Cutsio generates streamable review assets from the HDE camera originals 5. Original HDE-compressed ARRIRAW files remain attached for download The DIT does not need to decompress HDE before uploading. The platform should be verified for HDE handling before the shoot. The original HDE files remain the camera-original package for retention and conform. ## What are the risks and limitations of HDE? HDE is lossless and reliable, but it has specific limitations that the DIT must understand. Platform limitation: HDE is macOS-only. Windows-based DIT workstations cannot create HDE files. The DIT must use a Mac for the offload process if HDE compression is required. Software dependency: HDE requires Codex Device Manager and a compatible copy tool. If Device Manager is not updated to the version supporting the latest ARRI SUP (Software Update Package), HDE offloads may fail or produce incompatible files. CRC failure handling: HDE uses a strict CRC verification method. If a single frame fails CRC, the entire clip fails the offload. The DIT must re-offload that clip from the card. This is rare with properly functioning media but can cause delays if a card has read errors. No re-compression: Once ARRIRAW is compressed with HDE, it cannot be re-compressed with HDE again. The files are already in their compressed state. Attempting to re-compress HDE files produces no additional space savings. Camera compatibility: HDE is available for Alexa 35, Alexa Mini LF, Alexa LF, Alexa 65, and Alexa SXT cameras. It is not available for Alexa Classic or AMIRA. The DIT should verify camera compatibility before planning an HDE workflow. ## How does HDE compare to ARRICORE? HDE and ARRICORE serve different purposes in the ARRI ecosystem. Understanding the difference is essential for workflow planning. | Property | ARRIRAW HDE | ARRICORE | | :--- | :--- | :--- | | Type | Lossless post-capture compression | In-camera RGB recording format | | Applied when | During offload (Codex Device Manager) | In-camera during recording | | Compression type | Lossless variable-bit-rate | Visually lossless RGB compression | | Size vs ARRIRAW | ~40% smaller | ~50% smaller | | Quality | Identical to source (lossless) | RGB processed (not raw) | | Post flexibility | Full ARRIRAW control (ISO, WB, tint) | ISO, WB, tint editable non-destructively | | Camera support | Alexa 35, Mini LF, LF, 65, SXT | Alexa 35 Xtreme only | | Workflow change | Standard ARRIRAW in NLE | Requires ARRICORE-compatible software | The practical choice: HDE is the right choice for productions shooting standard ARRIRAW on existing Alexa cameras (Alexa 35, Mini LF, LF). ARRICORE is the right choice for Alexa 35 Xtreme productions that want smaller in-camera files and can work in a non-raw RGB format. Some productions use both. The Alexa 35 records ARRIRAW on-camera. The DIT applies HDE during offload. The HDE-compressed files are then uploaded to Cutsio. This gives the full raw flexibility of ARRIRAW with the 40% storage savings of HDE. ## FAQ ### Is HDE compatible with all NLEs and color grading software? In supported applications, HDE-compressed ARRIRAW is decompressed through ARRI/Codex-compatible tooling and behaves like ARRIRAW. Verify the exact NLE, grading application, and software version before committing to an HDE workflow. ### Can I upload HDE-compressed ARRIRAW directly to Cutsio? Yes, when HDE support is enabled for the production. Upload the HDE-compressed ARRIRAW package directly after verifying the workflow with a test clip; do not decompress first unless your post supervisor asks for standard ARRIRAW. ### Does HDE work with ProRes recordings? No. HDE is exclusively available for ARRIRAW files. ProRes recordings from ARRI cameras cannot be HDE-compressed. ProRes is already a compressed format, and HDE is designed for the uncompressed ARRIRAW data stream. ### How do I verify that HDE compression was applied successfully? Codex Device Manager performs CRC verification during the HDE offload process and reports the verification result for each clip. The copy tool (Hedge, Silverstack, or YoYotta) also displays the verification status. Always confirm that all clips pass CRC verification before erasing the camera card. ### Can HDE be applied retroactively to existing ARRIRAW files? HDE is designed to be applied during the initial offload from the camera card. While it is technically possible to apply HDE to existing ARRIRAW files using Codex Device Manager, the recommended workflow is to apply HDE during the primary offload to avoid additional processing time and maintain a clean file management workflow.

HDE or standard ARRIRAW. One upload pipeline.

Upload HDE-compressed or standard ARRIRAW to Cutsio. Either way, the cloud handles the transcode, Visual Intelligence indexes every frame, and originals stay attached for conform.

Try Cutsio Free

No credit card required. 60 minutes of free processing.