Plan R3D storage before the shoot: record time is only half the equation
Card runtime, offload throughput, duplicate storage and archive space all come from the same data-rate decision.
Start with reference throughput
For 6K 17:9 around 24 fps, RED publishes reference rates of up to roughly 280 MB/s HQ, 175 MB/s MQ and 110 MB/s LQ. Scene complexity and capture settings can change actual rates, so a planner should include safety margin rather than using the reference number as an exact promise.
Translate data into production consequences
- Minutes per card determine whether camera waits for media.
- GB per hour determines travel-drive and shuttle-drive quantity.
- Reader and destination-drive speed determine whether offload can keep up with camera.
- Number of verified copies determines real storage, not just camera-original size.
- Archive policy determines the cost that remains after the job is delivered.
A simple stress test
If the camera can fill a card faster than the data team can offload and verify it, the system will eventually stall no matter how many cards you own. Use the Actingwood R3D Media Planner to compare record time with offload time and build margin before the shoot.
Production rule
Do not ask “How much footage can this card hold?” Ask “Can the entire media cycle keep up safely for the longest expected shooting block?”
This Field Lab note is written independently by Actingwood and cross-checked against RED’s published documentation. Camera firmware, supported media and software behaviour can change; verify critical settings against the current RED guide before a production.
RED R3D Quality Guide →Actingwood is independent and is not affiliated with or endorsed by RED Digital Cinema. RED, REDCODE, R3D, KOMODO and related marks belong to their respective owners.