---
title: "Upload Native Camera Files Directly to Cloud Review: No Pre-Transcode Required"
author: "Cutsio Team"
date: "2026-05-08"
lastmod: "2026-05-08"
category: "Comparisons & Alternatives"
excerpt: "PIX and Frame.io require H.264 transcoding before upload. Cutsio's enterprise raw ingestion lets you upload native ARRIRAW, RED R3D, and BRAW files directly — the cloud handles the transcode automatically."
tags: ["PIX Alternative","ARRIRAW","RED RAW","BRAW","Native Raw","No Transcode","DIT Workflow","Cloud Dailies","Post Production","Enterprise Ingestion"]
---
## Can you upload native ARRIRAW, RED R3D, or BRAW files to cloud review without transcoding first?
Yes — Cutsio's enterprise raw ingestion add-on accepts native ARRIRAW (.ari, .mxf, .arx), RED R3D (.r3d), and Blackmagic RAW (.braw) files directly from the DIT's offload drive. No manual pre-transcode to H.264 or ProRes is required before upload. The cloud handles the format-specific decoding and generates streamable review assets on the backend, while the original camera files remain attached for download and conform. This is the fundamental feature that makes Cutsio a true [PIX alternative for film and TV](/blog/pix-alternative-film-tv-post-production).
PIX, Frame.io, Dropbox Replay, and Vimeo Review all require manual transcoding before upload. Every platform that does not support native raw ingestion forces the DIT to render proxies locally, manage a separate file naming convention, upload the transcoded files, and maintain a separate conform relink workflow.
This guide covers exactly which formats are supported, what the upload workflow looks like, and how the review stream quality compares to manually transcoded proxies.
## Which camera formats can you upload directly to Cutsio?
Cutsio's enterprise raw ingestion add-on supports the following native camera formats:
| Format | File Extensions | Camera Systems |
| :--- | :--- | :--- |
| ARRIRAW | .ari, .mxf, .arx | Alexa 35, Alexa 35 Xtreme, Alexa Mini LF, Alexa LF, Alexa 65, Alexa SXT |
| ARRICORE | .mxf | Alexa 35 Xtreme |
| RED R3D | .r3d | RED V-RAPTOR, RED KOMODO-X, RED Weapon, RED Gemini, RED Helium |
| Blackmagic RAW | .braw | URSA Mini Pro 12K, URSA Cine, Pocket Cinema Camera 6K |
ProRes, H.264, H.265, and DNxHR files are supported through Cutsio's standard upload pipeline without the enterprise add-on.
Sony RAW from Venice and FX series cameras is supported on a case-by-case basis through the enterprise add-on.
## What does the upload workflow look like for the DIT?
The upload workflow is designed to minimize the DIT's time spent on file management.
Step 1: Verify card offload. The DIT offloads camera cards to RAID storage using Codex Device Manager, Silverstack, or Hedge. Checksums are verified before any upload begins.
Step 2: Connect to Cutsio. The DIT opens the Cutsio upload interface from the offload workstation. The enterprise add-on is already configured for the production.
Step 3: Select native files. The DIT selects the native camera files — .mxf for ARRIRAW, .r3d for RED, .braw for Blackmagic — from the verified RAID storage. There is no need to distinguish between raw and compressed files. The enterprise add-on handles both.
Step 4: Upload. Files are uploaded at their original size. A 10-minute ARRIRAW clip at 4.6K Open Gate is uploaded as a single file — no splitting, no compression, no resolution reduction.
Step 5: Review. Cutsio processes the uploaded files and generates streamable review assets on the backend. The first clips are available for review within minutes of completing upload.
The total DIT time per shoot day with Cutsio is approximately half of what the same day would require with PIX, because the transcode step — which typically takes 2-4 hours — is eliminated entirely.
## How does the review stream quality compare to a manually transcoded H.264 proxy?
The review stream is generated from the original raw files using the correct color space and look metadata. For ARRIRAW, the stream uses the LogC4-to-video transform. For RED R3D, it uses the REDWideGamutRGB-to-Rec.709 transform with any embedded .rlm look metadata applied.
In most cases, the Cutsio review stream looks better than a manually transcoded H.264 proxy because:
- The cloud transcode uses the correct color science from the source metadata
- The bitrate is optimized for the specific source format
- Look metadata (ALF4, .rlm, CDL) is read and applied automatically
- There is no generational quality loss from an intermediate transcode
The review stream is optimized for viewing, not for finishing. The original camera files remain the source of truth for conform, grading, and finishing.
## How does direct raw upload change the DIT's workflow?
The DIT's primary value on set is data integrity and technical support. Transcoding proxies consumes time that should be spent on those priorities.
With direct raw upload, the DIT gains back 2-4 hours per shoot day. That time can be reinvested in:
- Verifying additional checksum passes on critical footage
- Managing ALF4 look files and .rlm metadata for the color pipeline
- Setting up monitoring and look creation for the DP
- Preparing camera cards for the next shoot day
- Resting between long shoot days
The DIT also eliminates the risk of uploading the wrong files. With PIX, the DIT must carefully manage two sets of files — the camera originals and the transcoded H.264 proxies — and ensure the correct proxies are uploaded for each clip. With Cutsio, the DIT uploads the camera originals directly. There is no second set of files to manage.
## FAQ
### Does Cutsio support all camera models within each raw format?
Cutsio offers ARRIRAW, RED R3D, and Blackmagic RAW ingestion through the enterprise add-on. For specific camera models within each format family, contact the Cutsio sales team to verify compatibility. The ARRI SDK, RED SDK, and Blackmagic RAW SDK handle format-specific decoding.
### Can I upload ProRes files through the enterprise add-on?
ProRes files are supported through Cutsio's standard upload pipeline. The enterprise raw ingestion add-on is specifically for native raw formats. If your production shoots ProRes as the primary format, the standard pipeline is sufficient.
### How much upload bandwidth do I need for native raw files?
The same bandwidth you would use for any cloud upload. Native raw files are larger than H.264 proxies, but you eliminate the transcode step entirely. For productions with limited upload bandwidth, HDE-compressed ARRIRAW or higher REDCODE compression ratios reduce file sizes before upload.
### What happens if my internet connection drops during upload?
Cutsio supports resumable uploads. If the connection drops, the upload resumes from the point of interruption. The DIT does not need to restart the upload from the beginning.
### Does PIX offer any form of native raw ingestion?
No. PIX only accepts H.264 compressed video. All raw footage must be transcoded to H.264 before upload. This is a fundamental limitation of the platform.
Native raw. Direct upload. No transcode queue.
Upload ARRIRAW, R3D, or BRAW directly to Cutsio. The cloud handles the transcode. Originals stay attached for conform.
Upload native .ari, .mxf, .r3d, .braw — no pre-transcode