---
title: "RED V-RAPTOR R3D Storage Calculator: How Much Footage Fits Per Shoot Day?"
author: "Cutsio Team"
date: "2026-05-06"
lastmod: "2026-05-06"
category: "Storage & Performance"
excerpt: "Calculate exactly how much RED V-RAPTOR 8K R3D footage fits per shoot day at every REDCODE compression ratio, frame rate, and resolution. Real-world storage requirements for production budgeting."
tags: ["RED RAW","R3D","RED V-RAPTOR","Storage Calculator","DIT Workflow","Post Production","REDCODE","Production Budgeting","Data Management"]
---

## How much RED V-RAPTOR R3D footage fits per shoot day?

A RED V-RAPTOR shoot day at 8K VV with 8:1 REDCODE compression generates approximately 5.5 to 6.5 GB per minute of footage, translating to 2.2 to 3.9 TB for a typical 6 to 10-hour shoot day at a 3:1 shooting ratio. Total storage requirements vary dramatically based on REDCODE compression ratio, resolution mode, frame rate, and shooting ratio — from as little as 800 GB for a 6K S35 day at 16:1 compression to over 8 TB for an 8K VV day at 5:1 compression with high frame rate intervals.

The V-RAPTOR is RED's flagship full-frame cinema camera with a 40.96 mm x 21.60 mm VV sensor capable of recording up to 8K resolution. It is also the most data-intensive camera in RED's lineup. A single production can easily accumulate 50 to 100 TB of R3D footage over a 20-day feature shoot. Producers, DITs, and post supervisors who underestimate storage requirements risk running out of drive space mid-production or overspending on RAID arrays that are never filled.

This guide breaks down the exact storage math for every common V-RAPTOR configuration, so you can calculate precisely how much storage you need before the first day of principal photography.

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).


## What are the real-world file sizes for each RED V-RAPTOR recording mode?

The V-RAPTOR offers multiple recording modes, each producing different data rates. These are the real-world file sizes based on RED's published specifications and verified by DIT field reports.

| Resolution | Sensor Mode | REDCODE | GB per Minute | GB per Hour | TB per 10-Hour Day (3:1 Ratio) |
| :--- | :--- | :--- | :--- | :--- | :--- |
| 8K VV | Full Frame 17:9 | 5:1 | ~11.2 GB/min | ~672 GB/hr | ~4.0 TB |
| 8K VV | Full Frame 17:9 | 8:1 | ~6.0 GB/min | ~360 GB/hr | ~2.2 TB |
| 8K VV | Full Frame 17:9 | 12:1 | ~4.0 GB/min | ~240 GB/hr | ~1.4 TB |
| 8K VV | Full Frame 17:9 | 16:1 | ~3.0 GB/min | ~180 GB/hr | ~1.1 TB |
| 8K VV | Full Frame 2.4:1 | 8:1 | ~5.0 GB/min | ~300 GB/hr | ~1.8 TB |
| 8K S35 | Super 35 17:9 | 8:1 | ~4.5 GB/min | ~270 GB/hr | ~1.6 TB |
| 6K S35 | Super 35 17:9 | 8:1 | ~3.2 GB/min | ~192 GB/hr | ~1.2 TB |
| 6K S35 | Super 35 17:9 | 12:1 | ~2.1 GB/min | ~126 GB/hr | ~0.8 TB |
| 4K S35 | Super 35 17:9 | 8:1 | ~1.8 GB/min | ~108 GB/hr | ~0.6 TB |

These figures represent actual recorded media — the R3D files stored on the CFexpress card. The shooting ratio (the amount of footage captured versus what ends up in the final edit) determines the total storage requirement per day. A 3:1 ratio means the production captures approximately 3 minutes of footage for every 1 minute in the final cut.

### How does frame rate affect storage?

High frame rate recording multiplies the data rate proportionally. The V-RAPTOR can record up to 120 fps at 8K VV and up to 600 fps at 2K.

| Resolution | REDCODE | Frame Rate | GB per Minute | 512 GB Card Capacity |
| :--- | :--- | :--- | :--- | :--- |
| 8K VV 17:9 | 8:1 | 24 fps | ~6.0 GB/min | ~85 min |
| 8K VV 17:9 | 8:1 | 48 fps | ~10.0 GB/min | ~51 min |
| 8K VV 17:9 | 8:1 | 60 fps | ~12.5 GB/min | ~41 min |
| 8K VV 17:9 | 8:1 | 120 fps | ~22.0 GB/min | ~23 min |
| 8K VV 17:9 | 5:1 | 120 fps | ~38.0 GB/min | ~13 min |
| 6K S35 17:9 | 8:1 | 120 fps | ~16.0 GB/min | ~32 min |

High frame rate material is typically shot in short bursts — a 10-second slow-motion shot at 120 fps produces roughly 3.7 GB of R3D data at 8K VV 8:1. The impact on daily storage totals depends on how much HFR material the production requires. A narrative feature with minimal slow motion might shoot only 5–10 minutes of HFR per day. A commercial or action-heavy project could shoot 30–60 minutes.

<div class="not-prose my-12 rounded-2xl border border-slate-200 dark:border-white/[0.08] bg-gradient-to-br from-slate-50 to-white dark:from-neutral-900 dark:to-neutral-950 p-8 md:p-10 shadow-sm">
  <div class="flex flex-col md:flex-row md:items-center md:justify-between gap-6">
    <div class="flex-1">
      <div class="flex items-center gap-3 mb-3">
        <div class="flex h-10 w-10 items-center justify-center rounded-xl bg-indigo-100 dark:bg-indigo-500/20 text-indigo-600 dark:text-indigo-400">
          <svg class="h-5 w-5" xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M3 3v18h18"/><path d="m19 9-5 5-4-4-3 3"/></svg>
        </div>
        <span class="text-sm font-semibold text-indigo-600 dark:text-indigo-400 uppercase tracking-wider">Cutsio</span>
      </div>
      <h3 class="text-xl md:text-2xl font-bold tracking-tight text-slate-900 dark:text-white mb-2">
        Know your storage numbers. Then shoot.
      </h3>
      <p class="text-slate-600 dark:text-neutral-400 text-base leading-relaxed max-w-xl">
        Planning storage for a V-RAPTOR shoot? Cutsio helps you review, search, and share R3D footage without duplicating files or paying per gigabyte.
      </p>
    </div>
    <div class="shrink-0">
      <a href="https://studio.cutsio.com" target="_blank" rel="noopener noreferrer"
         class="inline-flex items-center justify-center rounded-full bg-indigo-600 px-6 py-3 text-sm font-medium text-white hover:bg-indigo-700 dark:bg-white dark:text-slate-900 dark:hover:bg-neutral-100 transition-colors shadow-sm">
        Try Cutsio Free
        <svg class="ml-2 h-4 w-4" xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M5 12h14"/><path d="m12 5 7 7-7 7"/></svg>
      </a>
      <p class="mt-2 text-xs text-center text-slate-400 dark:text-neutral-500">No credit card. 60 mins free.</p>
    </div>
  </div>
</div>

## How many CFexpress cards do you need per V-RAPTOR shoot day?

The V-RAPTOR records to CFexpress Type B media. Understanding card capacity and rotation requirements is essential for production budgeting.

| Card Capacity | 8K VV 8:1 24 fps (6.0 GB/min) | 8K VV 5:1 24 fps (11.2 GB/min) | 8K VV 8:1 120 fps (22 GB/min) |
| :--- | :--- | :--- | :--- |
| 512 GB | ~85 min | ~46 min | ~23 min |
| 1 TB | ~170 min | ~91 min | ~46 min |
| 2 TB | ~340 min | ~182 min | ~93 min |

For a standard 10-hour shoot day with two cameras and a 3:1 shooting ratio (approximately 180 minutes of total captured footage per camera):

| Camera Count | Total Captured Footage | 1 TB Cards Required (8K VV 8:1) | 2 TB Cards Required (8K VV 8:1) |
| :--- | :--- | :--- | :--- |
| 1 camera | ~180 min | 2 cards (rotating) | 1 card |
| 2 cameras | ~360 min | 3–4 cards (rotating) | 2 cards |
| 3 cameras | ~540 min | 4–5 cards (rotating) | 3 cards |

The recommendation is to budget for at least one spare card per camera beyond the minimum rotation. If cards are not being offloaded during the shoot day, the rotation must account for the full day's capacity without reusing cards.

## What is the total storage requirement for a full V-RAPTOR production?

For production budgeting, the total storage requirement includes the camera originals plus backup copies. The standard DIT workflow maintains a primary RAID and a backup drive.

| Production Length | Resolution / REDCODE | Total R3D Originals | With 1 Backup (2×) | With 2 Backups (3×) |
| :--- | :--- | :--- | :--- | :--- |
| 5-day commercial | 8K VV 12:1 | ~7 TB | ~14 TB | ~21 TB |
| 10-day indie feature | 8K VV 8:1 | ~22 TB | ~44 TB | ~66 TB |
| 20-day feature | 8K VV 8:1 | ~44 TB | ~88 TB | ~132 TB |
| 30-day feature | 8K VV 5:1 | ~120 TB | ~240 TB | ~360 TB |
| 40-day feature | 8K VV 8:1 | ~88 TB | ~176 TB | ~264 TB |

These figures assume a 3:1 shooting ratio with 10-hour shoot days. Productions with higher shooting ratios (documentary, unscripted, or heavy coverage) will require proportionally more storage.

### How much RAID storage should a DIT cart carry for V-RAPTOR?

For a V-RAPTOR production, the DIT cart should carry a minimum of 2× the projected total R3D originals to maintain a primary and backup during production. Additional storage is needed for proxies if the production is running a traditional proxy pipeline.

| Production Type | Recommended RAID Capacity | RAID Configuration |
| :--- | :--- | :--- |
| Commercial shoot (5 days) | 24 TB usable | 4× 12 TB in RAID 5 |
| Indie feature (15 days) | 80 TB usable | 8× 14 TB in RAID 6 |
| Feature film (30+ days) | 200+ TB usable | 12× 20 TB in RAID 6 |

Cutsio eliminates the need to store proxies on the RAID because the review stream is generated in the cloud. The DIT only needs to store the original R3D files locally plus the cloud-based review assets accessible through Cutsio.

## How does REDCODE compression ratio affect review quality and storage?

REDCODE compression is RED's proprietary wavelet-based compression system. It is visually efficient — higher compression ratios save significant storage space with minimal perceived quality loss, but the tradeoffs matter for specific workflows.

| REDCODE Ratio | Storage Savings vs 5:1 | Typical Use Case | Visual Difference |
| :--- | :--- | :--- | :--- |
| 5:1 | Baseline | VFX-heavy work, green screen, high-end commercials | Maximum data retention for keying and compositing |
| 8:1 | ~46% less storage | Narrative features, general production | Visually indistinguishable from 5:1 in most scenes |
| 12:1 | ~64% less storage | Day-for-day narrative, low-compression priority | Minimal difference in well-exposed footage |
| 16:1 | ~73% less storage | Documentary, B-roll, high-volume shooting | Slight compression artifacts visible in gradients and noise |
| 22:1 | ~82% less storage | Extended recording, interview-only setups | Visible compression in challenging scenes |

The practical recommendation for most V-RAPTOR narrative productions: shoot 8:1 for A-cam and 12:1 for B-cam. The storage savings are significant, and the visual difference is negligible in normal viewing conditions. Reserve 5:1 for VFX plates and green screen work.

## How does Cutsio's storage model compare to traditional R3D storage costs?

Traditional cloud storage charges per gigabyte, which makes storing V-RAPTOR R3D files prohibitively expensive. A single 20-day feature at 8K VV 8:1 generates approximately 44 TB of R3D originals. At Google Drive or Dropbox prices, that is $800 to $1,600 per month just to keep the files online.

Cutsio's pay-for-minutes model decouples storage cost from file size. The same 44 TB of R3D footage costs based on the total minutes of duration, not the gigabyte footprint. The review assets remain streamable and fully searchable through Visual Intelligence at all times. The original R3D files are retained as attachments for download and conform when needed.

| Storage Model | 44 TB R3D Library (per month) |
| :--- | :--- |
| Google Drive Enterprise | ~$800–$1,200 |
| Dropbox Advanced | ~$800–$1,000 |
| AWS S3 Standard | ~$900–$1,100 |
| Cutsio pay-for-minutes | Significantly less for equivalent duration |

The Cutsio model is particularly efficient for V-RAPTOR productions because the review assets (which are the files accessed most frequently during the edit) remain streamable without downloading the massive R3D originals. The R3D files are downloaded only when needed for conform — typically once per scene during the online edit.

## How do you calculate your exact V-RAPTOR storage budget?

Use this formula to calculate your production's total storage requirement:

```
Daily Storage = (Minutes of Footage Captured per Day) × (GB per Minute at Your REDCODE/Resolution)
Shoot Total = Daily Storage × Number of Shoot Days
With Backup = Shoot Total × Number of Backup Copies
```

Example calculation for a 20-day feature at 8K VV 8:1:

1. **Daily captured footage**: 6 hours (360 minutes) at 3:1 shooting ratio
2. **GB per minute at 8K VV 8:1**: ~6.0 GB/min
3. **Daily storage**: 360 × 6.0 = 2,160 GB (2.16 TB per day)
4. **Shoot total**: 2.16 × 20 = 43.2 TB
5. **With one backup**: 43.2 × 2 = 86.4 TB total storage required

This calculation assumes no high frame rate material. If the production includes HFR intervals, add the HFR footage separately using the frame rate multipliers in the table above.

## FAQ

### Does REDCODE compression affect the Cutsio review stream quality?

No. Cutsio generates the review stream from the R3D file regardless of the REDCODE compression ratio used during recording. The review asset quality is independent of the compression setting.

### Can I shoot at 16:1 REDCODE and still get good search results from Visual Search?

Yes. Visual Search indexes the review stream, which is generated at a consistent quality level regardless of the source REDCODE compression. The search accuracy is not affected by the compression ratio.

### How much storage do I need if I'm shooting 5:1 for VFX plates?

VFX plates are typically short in duration — a few minutes per setup. Even at 5:1 REDCODE, a day of VFX plate shooting rarely exceeds 500 GB to 1 TB per camera. Budget extra storage for VFX-heavy days but do not let the VFX requirement dictate your entire storage plan.

### What is the most storage-efficient REDCODE ratio for V-RAPTOR dailies?

12:1 REDCODE at 8K VV offers the best storage-to-quality ratio for dailies review. The visual difference from 8:1 is minimal in normal viewing conditions, but the storage savings are approximately 33%.

### Is RED R3D ingestion available for V-RAPTOR footage in Cutsio?

Yes. RED R3D ingestion is available as an enterprise add-on for qualified production accounts. Contact the Cutsio sales team to enable raw format support for your V-RAPTOR production.

<div class="not-prose blog-large-cta">
  <div class="max-w-3xl mx-auto text-center">
    <h3>
      Know your storage. Never pay per gigabyte again.
    </h3>
    <p>
      V-RAPTOR R3D footage is massive. Cutsio's pay-for-minutes model means you store, review, and search terabytes of footage without the per-gigabyte cloud storage bills.
    </p>
    <ul>
      <li>
        <svg class="h-6 w-6 text-emerald-400 shrink-0 mt-0.5" xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><polyline points="20 6 9 17 4 12"/></svg>
        <span>Upload native R3D — no manual proxy render required</span>
      </li>
      <li>
        <svg class="h-6 w-6 text-emerald-400 shrink-0 mt-0.5" xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><polyline points="20 6 9 17 4 12"/></svg>
        <span>Visual Search finds any frame by describing what the camera saw</span>
      </li>
      <li>
        <svg class="h-6 w-6 text-emerald-400 shrink-0 mt-0.5" xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><polyline points="20 6 9 17 4 12"/></svg>
        <span>Pay for minutes, not gigabytes — even at 8K</span>
      </li>
    </ul>
    <div class="flex flex-col sm:flex-row items-center justify-center gap-4">
      <a href="https://studio.cutsio.com" target="_blank" rel="noopener noreferrer"
         class="no-underline inline-flex items-center justify-center rounded-full bg-indigo-600 px-8 py-3.5 text-sm font-semibold text-white hover:bg-indigo-700 dark:bg-white dark:text-slate-900 dark:hover:bg-neutral-100 transition-colors shadow-sm">
        Try Cutsio Free
        <svg class="ml-2 h-4 w-4" xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M5 12h14"/><path d="m12 5 7 7-7 7"/></svg>
      </a>
      <button type="button" onclick="window.dispatchEvent(new CustomEvent('open-contact-modal'))"
              class="inline-flex items-center justify-center rounded-full border border-white/20 px-8 py-3.5 text-sm font-medium text-white hover:bg-white/10 transition-colors">
        Book a demo
      </button>
    </div>
    <p class="mt-4 text-xs text-slate-500">No credit card required. 60 minutes of free processing.</p>
  </div>
</div>
