---
title: "Alexa 35 Xtreme Sensor Overdrive Workflow: 660 fps, 11 Stops, and Color Matching in Post"
author: "Cutsio Team"
date: "2026-05-08"
lastmod: "2026-05-08"
category: "Storage & Performance"
excerpt: "The complete post workflow for Alexa 35 Xtreme Sensor Overdrive footage — how to flag, review, organize, and grade 660 fps clips shot at 11 stops of dynamic range alongside standard-speed material."
tags: ["ARRI RAW","Alexa 35 Xtreme","Sensor Overdrive","660 fps","High Speed","ARRICORE","ARRIRAW","Post Production","Color Pipeline","DIT Workflow"]
---

## How do you handle Alexa 35 Xtreme Sensor Overdrive footage in the post pipeline?

Sensor Overdrive is an Alexa 35 Xtreme recording mode that enables frame rates up to 660 fps by reducing the sensor read-out time, trading 6 stops of dynamic range (from 17 to 11 stops) and raising the base sensitivity to EI 1600. In post, Sensor Overdrive clips require separate handling from standard-speed footage — flagged metadata for DIT identification, adjusted color treatment for the reduced dynamic range, and careful integration with standard-speed material in the same timeline.

The Alexa 35 Xtreme introduced Sensor Overdrive mode as part of its July 2025 launch. It is designed for situations where extreme slow-motion is required and controlled lighting environments allow for the dynamic range trade-off. The mode activates by toggling Sensor Overdrive in the camera menu, which unlocks frame rates above 330 fps. Not all recording formats support Sensor Overdrive — it is available only in specific resolutions and codec combinations.

For post production, Sensor Overdrive footage is not a problem — it simply requires awareness that these clips have different exposure characteristics, reduced highlight latitude, and higher base noise than standard-speed clips from the same camera.

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 Sensor Overdrive affect image characteristics in the grade?

The fundamental change is dynamic range. Standard Alexa 35 Xtreme footage at up to 330 fps retains the full 17 stops of the ALEV4 sensor. Sensor Overdrive footage at 330 to 660 fps operates at approximately 11 stops of dynamic range with a base sensitivity of EI 1600.

| Image Property | Standard Speed (up to 330 fps) | Sensor Overdrive (330-660 fps) |
| :--- | :--- | :--- |
| Dynamic range | 17 stops | ~11 stops |
| Base sensitivity | EI 160-6400 | EI 1600 (minimum) |
| Highlight latitude | Full (17 stops) | Reduced (6 stops lost in highlights) |
| Shadow noise | Minimal at base ISO | Higher noise floor at EI 1600 |
| Color science | REVEAL / LogC4 | REVEAL / LogC4 (same color space) |
| Sensor crop | Super 16 at max frame rates | Super 16 at max frame rates |

For the colorist, Sensor Overdrive clips require:

- No aggressive highlight recovery — the reduced dynamic range means highlights clip sooner than standard footage
- Gentle shadow grading — the higher noise floor at EI 1600 may produce visible noise if shadows are pushed
- Matching to standard-speed footage from the same scene — the color space is identical, but exposure and contrast characteristics differ

The most important rule: do not apply the same grade to Sensor Overdrive clips and standard-speed clips from the same scene. The exposure curve and noise characteristics are different. Each Sensor Overdrive clip should be graded independently, then visually matched to the scene's standard-speed reference.

## How should the DIT flag Sensor Overdrive clips during offload?

Sensor Overdrive state should be verified during offload and carried into the DIT report. Where the metadata is exposed by the offload tool, use it; where it is not obvious, add a manual tag so editorial and color can identify high-speed material quickly.

The recommended workflow:

1. During offload, verify whether Sensor Overdrive state is visible in the metadata
2. Rename or tag Sensor Overdrive clips with an "_HS" or "_SOD" suffix for quick visual identification
3. Organize Sensor Overdrive clips into a separate folder or bin in the dailies library
4. Note the base sensitivity (EI 1600) and reduced dynamic range in the DIT report
5. Upload to Cutsio with the camera metadata and manual high-speed tags preserved

When uploading to Cutsio through the enterprise raw ingestion add-on, keep the original MXF metadata intact and use project tags or notes to mark Sensor Overdrive clips for the post team.

## How do you review Sensor Overdrive footage alongside standard-speed clips in Cutsio?

Cutsio generates streamable review assets from Sensor Overdrive clips so the director and DP can review the high-speed material without opening the camera originals locally. For editorial accuracy, document the capture frame rate and intended playback frame rate in the clip notes or DIT report.

The review workflow:

1. Sensor Overdrive clips appear in the same library as standard-speed clips
2. The playback frame rate is checked against the DIT report
3. Visual Intelligence indexes the generated review assets for search and discovery
4. Collections can be used to group Sensor Overdrive clips separately from standard-speed material
5. Comments and annotations reference specific frames regardless of frame rate

For the director and DP, the review experience can sit alongside standard-speed footage in the same library, but high-speed material should still be labeled clearly so the intended playback speed is not confused with the capture speed.

## How do you color match Sensor Overdrive footage to standard-speed shots?

Color matching Sensor Overdrive footage to standard-speed Alexa 35 Xtreme footage is achievable but requires deliberate effort from the colorist. The color space and color science are identical — both use REVEAL with LogC4 encoding. The differences are in exposure latitude, noise floor, and contrast response.

| Matching Step | Standard Speed | Sensor Overdrive | Adjustment Required |
| :--- | :--- | :--- | :--- |
| Exposure | Normal exposure curve | EI 1600 base, highlight-limited | Reduce highlights, avoid clipping |
| Contrast | Full 17-stop range | ~11-stop range | Flatter contrast curve, reduced specular |
| Noise | Clean at base ISO | Higher noise floor | Gentle noise reduction if needed |
| Color | LogC4 / REVEAL | LogC4 / REVEAL | Same color space — no color shift |
| Grain | Sensor noise | Higher sensor noise | May need grain reduction for matching |

The practical approach in DaVinci Resolve:

1. Grade the standard-speed master clip first
2. Copy the grade to the Sensor Overdrive clip
3. Reduce highlight gain to prevent clipping (the Sensor Overdrive clip has 6 fewer stops of headroom)
4. Adjust midtones to match the standard-speed contrast
5. Apply gentle noise reduction if the Sensor Overdrive shadow noise is visible
6. Verify the match with the standard-speed clip side by side

For productions where Sensor Overdrive clips are intercut with standard-speed footage in the same scene, the colorist should budget additional time for matching. For productions where Sensor Overdrive is used for dedicated slow-motion shots that are not intercut — for example, a product splash shot in slow motion while interview footage is standard speed — the matching requirement is less strict.

## What storage impact does Sensor Overdrive have on the dailies pipeline?

Sensor Overdrive at 660 fps produces far more data per minute of real-time recording than standard 24 fps footage. The exact storage impact depends on sensor mode, codec, compression behavior, and project frame rate, so storage should be estimated from ARRI's current recording-format tables or from a camera test.

| Planning Variable | Why It Matters |
| :--- | :--- |
| Sensor mode | Open Gate, 4K, 2K S16, and HD modes have very different pixel counts |
| Codec | ARRICORE, ProRes 4444, and ProRes 422 HQ have different data-rate profiles |
| Capture FPS | 330 fps and 660 fps consume media much faster than 24 fps |
| Playback FPS | A 10-second capture can become a much longer slow-motion clip in editorial |
| Take discipline | High-speed resets, false starts, and pre-roll can dominate storage use |

For the DIT planning storage for a high-speed day, budget from the camera's current recording-format chart and add a safety margin for repeated takes. Do not extrapolate from 24 fps Open Gate data rates unless the sensor mode and codec are the same.

When uploading to Cutsio, Sensor Overdrive clips should be uploaded after standard-speed footage so the editorial team can begin reviewing the primary coverage first. The high-speed clips can process in the background.

## FAQ

### Can Sensor Overdrive footage be mixed with standard-speed footage in the same Cutsio library?

Yes. Sensor Overdrive and standard-speed clips from the same production can coexist in the same Cutsio library. Keep the capture/playback frame-rate notes with the clip so directors, editors, and colorists understand whether they are reviewing real-time capture, slow-motion playback, or an editorial transcode.

### Does Sensor Overdrive affect look file (ALF4) compatibility?

No. Sensor Overdrive clips use the same ALF4 look file system as standard-speed Alexa 35 Xtreme footage. Look files created for standard-speed material can be applied to Sensor Overdrive clips, though the reduced dynamic range may cause the look to behave differently in the highlights.

### Is Sensor Overdrive available in ARRIRAW or only in ARRICORE and ProRes?

ARRI lists Sensor Overdrive with specific recording-format combinations on the ALEXA 35 Xtreme. Check the current ARRI recording-format chart for the exact sensor mode, codec, and frame-rate combination before shoot day; do not assume every ARRIRAW, ARRICORE, or ProRes mode supports Overdrive.

### How does the Super 16 sensor crop affect the conform workflow?

At maximum frame rates, the Alexa 35 Xtreme uses a Super 16 sensor crop. This means Sensor Overdrive clips have a different resolution and field of view than standard-speed Open Gate footage. The conform should account for the crop — the timeline resolution should accommodate the S16 frame size, or the S16 clips should be upscaled to match the project resolution.

### Do I need special storage or infrastructure for Sensor Overdrive shoot days?

Yes. Budget extra storage and transfer time on high-speed days based on the selected recording mode. Use fast, verified offload workflows, and consider uploading standard-speed coverage first so editorial can begin reviewing primary material while high-speed clips process in the background.

<div class="not-prose blog-large-cta">
  <div class="max-w-3xl mx-auto text-center">
    <h3>
      660 fps slow-motion. Standard dailies pipeline.
    </h3>
    <p>
      Upload Sensor Overdrive clips alongside standard-speed footage to Cutsio. Review high-speed material in the same library. Originals stay attached for conform.
    </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 Sensor Overdrive clips — any frame rate</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>Mixed frame rates in one library — 24 fps to 660 fps</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>Originals attached — download for conform in any NLE</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>
