Cutsio Blog

How to Package RED R3D Folders for Cloud Upload Without Losing Metadata

The practical guide to packaging RED R3D files for cloud dailies upload — preserving RDM folder structure, RMD sidecars, look files, and checksums for a complete conform-ready package.

How do you package RED R3D files for cloud upload without losing metadata?

To package RED R3D files for cloud upload without losing metadata, preserve the original RDM (RED Digital Magazine) folder structure, verify that all RMD sidecar files are present alongside their parent R3D files, embed critical metadata into the R3D headers before upload, and generate a checksum manifest for the complete package. The most common conform failures in cloud dailies workflows trace back to metadata lost during the packaging and upload process.

RED cameras organize footage into a specific folder structure: each magazine is an RDM folder containing RDC (RED Digital Clip) sub-folders, and each RDC folder contains one R3D clip file plus its associated metadata files. When this structure is flattened or reorganized during upload, the relationship between R3D files and sidecar metadata can be broken.

This guide covers the exact packaging workflow that preserves all metadata for a complete, conform-ready cloud upload.

Working with raw camera footage? Check out How to Build a Searchable Library From ARRIRAW, RED R3D, and ProRes Footage.

What is the correct RED folder structure for cloud upload?

RED's native folder structure must be preserved for metadata integrity. Each camera magazine produces an RDM folder with the following structure:

A001_RDM_240101_001/
A001_C001_240101_001.RDC/
A001_C001_240101_001.r3d
A001_C001_240101_001.RMD
Additional sidecar/look files, if created by the camera or DIT tool
A001_C001_240101_001.HTM  (metadata summary)
A001_C002_240101_001.RDC/
A001_C002_240101_001.r3d
A001_C002_240101_001.RMD
...

Each RDC folder normally contains the R3D clip and its associated metadata files. The RDC folder name matches the clip name. The RMD file can contain RAW parameter overrides and look-related metadata created during camera, DIT, or color workflows.

For cloud upload, the recommended approach is to upload the complete RDM folder structure without flattening or reorganizing it. Cutsio's enterprise raw ingestion add-on accepts the native RDM folder structure, preserving the file relationships.

What metadata files must be preserved for a complete conform package?

The critical metadata files for a RED conform package are:

| File | Required? | Purpose | Consequence If Missing |

| :--- | :--- | :--- | :--- |

| .r3d | Yes | Camera raw sensor data | No source for conform |

| .RMD | Recommended | RAW parameter overrides (ISO, WB, color science) | Default camera metadata used |

| Additional look files | If created by camera/DIT workflow | Creative look references or LUT dependencies | Look may need to be rebuilt from reference |

| DIT reports | Recommended | Human-readable camera and look notes | Metadata decisions become harder to audit |

| .HTM | No | Human-readable metadata summary | No metadata reference |

The RMD file is the most important sidecar. It stores all RAW parameter adjustments made by the DIT or colorist — ISO changes, white balance corrections, color science version selection, and look file references. If the RMD is missing, the R3D file reverts to the in-camera metadata defaults, which may not reflect the approved dailies look.

The recommended practice: preserve the complete RDM/RDC folder and keep the RMD metadata with its parent R3D. Some workflows also embed metadata into the R3D header, but that should be approved by the DIT and finishing vendor before upload.

How do you verify that all metadata is present before uploading?

Before uploading RED footage to a cloud dailies platform, verify the completeness of each clip's metadata package.

Step 1: Count files per RDC folder. Each RDC folder should contain at least one .r3d file and one .RMD file. If the .RMD is missing, the clip was probably not processed with metadata adjustments. Use a script or DIT software to scan the folder structure and report missing files.

Step 2: Verify RMD and look-package association. If the production uses creative look files or LUTs, verify that each R3D has the expected sidecars or documented references. Open a test clip in REDCINE-X PRO or Silverstack and confirm the look is applied.

Step 3: Checksum the complete package. Generate an MD5 or SHA-256 checksum for every file in the RDM folder structure. Save the checksum manifest alongside the upload package. When the files are downloaded from the cloud for conform, verify the checksums match.

Step 4: Test a single clip through the full pipeline. Upload one R3D clip with its complete metadata package to Cutsio and verify that:

• The review stream displays the correct look
• The RMD metadata is readable in the download package
• The R3D file checksum matches the original

Step 5: Document the metadata state. Create a DIT report that documents which RED SDK version was used, which R3D files have embedded vs sidecar metadata, and which clips have creative look files applied.

What should you avoid when packaging RED footage for cloud upload?

Common mistakes that break RED metadata integrity:

• Flattening the folder structure: Moving R3D files out of their RDC folders and into a flat list can break the association with RMD and look sidecars. Upload the complete RDM folder structure whenever possible.
• Renaming files: R3D files should never be renamed. The file name encodes the reel ID, clip number, and date, which are used for conform relinking. If renaming is required, create a rename manifest that maps old names to new names.
• Using compression archives: ZIP, RAR, or TAR archives can corrupt or omit sidecar files. Upload the raw folder structure directly.
• Skipping checksum verification: Always verify file integrity before and after upload. Network interruptions during upload can corrupt files without warning.
• Forgetting look files: look sidecars, LUTs, and DIT reports are small and easy to overlook. Verify they are present in the package or documented in the conform notes.

| Action | Safe? | Why |

| :--- | :--- | :--- |

| Upload RDM folder as-is | Yes | Preserves all metadata relationships |

| Flatten RDC folders into single directory | No | Loses R3D-to-RMD association |

| Rename R3D files | No | Breaks conform relinking |

| Embed RMD into R3D header | Yes | Eliminates sidecar dependency |

| Upload individual R3D without RMD | No | Loses all RAW parameter overrides |

| Compress RDM into ZIP | No | Risk of corruption and missing sidecars |

How does Cutsio handle RED folder structure and metadata?

Cutsio's enterprise raw ingestion add-on accepts RED footage uploaded in the native RDM folder structure. The platform reads the R3D files and their associated metadata, generates streamable review assets with the correct look applied, and retains the original folder structure in the downloadable package.

The upload workflow:

1. DIT preserves the RDM/RDC folder structure on the offload drive
2. The complete RDM folder is uploaded to Cutsio through the enterprise add-on
3. Cutsio indexes the R3D files and reads the embedded or sidecar metadata
4. Review streams are generated with the correct color space and look metadata
5. The original RDM folder structure is preserved in the download package
6. The online editor downloads the complete RDM structure for conform

The online editor downloading the conform package receives the same RDM/RDC folder structure that the DIT uploaded. The R3D files, RMD sidecars, look files, reports, and checksums remain in their expected locations when they were included in the upload.

FAQ

Can I upload individual R3D files without the RDM folder structure?

Yes, but metadata integrity is improved when the RDM structure is preserved. If uploading individual files, ensure that the RMD sidecar is either present alongside the R3D or embedded into the R3D header. Cutsio accepts both flat uploads and RDM-structured uploads.

What happens if the RMD file is missing from the upload?

If the RMD file is not present and the metadata is not embedded in the R3D header, Cutsio falls back to the available camera metadata and standard viewing transform configured for the project. The clip may display without DIT-applied RAW parameter adjustments or creative look files.

How do I verify that the cloud download package matches the original upload?

Compare the checksum manifest from the upload to the checksums of the downloaded files. Cutsio provides checksum verification for downloaded files. If the checksums match, the metadata and file integrity are preserved.

Does Cutsio support RED LTO archive restoration for upload?

Yes. RED footage restored from LTO tape can be uploaded to Cutsio as long as the original RDM folder structure is preserved. Verify that the LTO restoration includes all sidecar files and that the checksums match the original archive.

Should I embed RMD metadata before or after upload?

Embed RMD metadata into the R3D headers before upload. This eliminates the sidecar file dependency and ensures the metadata travels with the R3D file regardless of how it is handled during upload and download. Silverstack and REDCINE-X PRO both support metadata embedding.