Volumetric video and spatial livestream projects produce more than a finished clip. They create camera originals, edited masters, playback files, metadata, proxies, project files, permissions records, and technical notes. This reusable workflow shows creators and event teams how to store, back up, catalog, verify, and retrieve those assets so a live hologram production remains usable after the event.
Overview
A reliable archive is not simply a folder containing the final export. It is a documented collection that preserves the source material, explains how each file was created, and allows another operator to open or re-edit the project later. That distinction matters in spatial streaming because a deliverable may need to be reformatted for a different display, playback system, streaming workflow, or audience experience.
Before production begins, decide what the team must retain and who will be responsible for it. At minimum, define an owner for the archive, a primary working location, a separate backup, an off-site or cloud copy where appropriate, and a process for checking that files can actually be restored. Do not treat a cloud sync folder as a complete backup unless the service and workflow provide the versioning, retention, and recovery controls your production requires.
The workflow below applies to volumetric capture, spatial video, digital avatar performances, mixed reality live production, and recorded elements used in holographic live streaming. The exact file formats and storage capacities will vary by capture system and delivery platform. Review those requirements alongside the real-time 3D streaming formats and codec compatibility guide before locking an archive plan.
What to track
1. Asset classes and storage requirements
Separate assets by their role in the production. This makes it easier to estimate capacity, apply permissions, and retrieve only what is needed for a re-edit or repurpose. The following is a planning comparison rather than a fixed specification.
| Asset class | What it contains | Storage priority | Archive notes |
|---|---|---|---|
| Camera originals | Raw captures, sensor data, depth streams, multi-camera views, or unprocessed volumetric takes | Highest capacity and preservation priority | Keep unchanged. Record capture settings, take numbers, timecode, and any missing or corrupted media. |
| Edited masters | Approved composites, edited spatial video, clean plates, or final program versions | High availability and clear version control | Store the approved master with resolution, frame rate, audio, color, and delivery notes. |
| Playback files | Files prepared for a specific holographic display, media server, headset, projection system, or streaming platform | High retrieval priority | Record the target device, software version, playback settings, and whether the file is display-specific. |
| Metadata | Scene descriptions, camera calibration, spatial coordinates, performer releases, rights notes, cue sheets, and technical logs | Small size, critical context | Store with the related media and in a readable project index. Metadata without the media reference is difficult to use. |
| Proxies and review files | Lower-resolution previews, editorial transcodes, thumbnails, and review exports | Lower preservation priority | Useful for browsing, but never substitute proxies for camera originals or approved masters. |
| Project and configuration files | Editing timelines, 3D scenes, playback projects, plugins, scripts, cue data, and render settings | High re-editing value | Include dependency lists and software version notes. A project file may not open correctly without its linked media or plugins. |
Estimate storage from the complete production, not only the runtime of the final video. Multiple takes, camera angles, intermediate renders, duplicated exports, and temporary caches can dominate capacity. Keep a simple inventory with the approximate size, owner, location, format, and retention decision for each asset group.
2. A folder structure that survives handoffs
Use a structure that makes sense to someone who did not attend the event. A project code, date, and clear asset category are more dependable than personal desktop folders or labels such as “final-final.” For example:
PROJECT_CODE_EVENT_NAME/
00_ADMIN/
archive_index.csv
rights_and_releases/
delivery_notes/
01_CAMERA_ORIGINALS/
capture_day_01/
capture_day_02/
02_PROJECT_FILES/
edit/
playback/
scripts_and_tools/
03_MASTERS/
approved/
review/
04_PLAYBACK_FILES/
device_or_platform_name/
05_METADATA/
calibration/
scene_notes/
timecode_and_cue_logs/
06_PROXIES/
thumbnails/
review_exports/
07_CHECKSUMS_AND_LOGS/
manifests/
transfer_logs/
restore_tests/
Do not mix temporary renders with approved masters. If a folder is excluded from the archive, label it as temporary or disposable in the index rather than leaving its status ambiguous.
3. A consistent naming template
Names should identify the project, date, scene or performer, take, camera or viewpoint, version, and status without becoming unwieldy. One workable pattern is:
PROJECT_YYYYMMDD_SCENE_TAKE_VIEW_VERSION_STATUS.ext Example: AURORA_20261030_STAGEA_T03_CAM02_V02_APPROVED.ext
Define abbreviations in the archive index. Use a consistent date format, avoid spaces and unexplained punctuation, and do not overwrite an earlier approved version. If a file is replaced, create a new version and note the reason. Naming cannot replace metadata, but it reduces avoidable confusion during a live event handoff.
Cadence and checkpoints
Archiving should happen at several points rather than as one task after the show. A repeatable cadence also gives the team opportunities to catch problems while the original media and technical staff are still available.
Before capture
- Confirm the expected capture formats, camera count, audio requirements, frame rates, and estimated capacity.
- Check that the working storage has enough free space for originals, intermediate files, and recovery overhead.
- Assign an archive owner and document who may read, modify, approve, or delete each asset class.
- Prepare the folder structure, naming convention, project index, and checksum process.
- Record the software, plugins, hardware, capture settings, and playback targets expected in the workflow.
During and immediately after capture
- Copy media to the working location without changing original filenames until the transfer is verified.
- Log incomplete takes, dropped frames, calibration issues, missing audio, and other exceptions while they are fresh.
- Create a second copy as soon as practical. Keep it independent from the primary working copy.
- Generate checksums or use an equivalent integrity check for transferred files, and retain the results with the project logs.
After editorial approval
- Mark the approved master and the playback-ready files separately.
- Capture the exact export settings and target environment for each delivery file.
- Archive the project files, linked media references, metadata, cue sheets, and relevant configuration files.
- Remove only confirmed temporary material, and record any exclusions in the index.
Monthly or quarterly review
For active projects, review the archive monthly. For completed productions, a quarterly review is a practical default, adjusted for contractual, legal, or organizational requirements. Check storage health, account access, backup status, retention dates, and whether the files remain readable in the tools the team expects to use.
Storage pricing, cloud transfer limits, supported volumetric formats, and software compatibility can change. Recheck those variables every six to twelve months, or sooner when a provider, platform, codec, or playback system changes. The spatial streaming bandwidth and latency checklist can help when an archived asset is being prepared for a new live delivery environment.
How to interpret changes
An archive review is useful only if the team can distinguish a storage problem from a cataloging problem, a permissions problem, or a compatibility problem.
- Capacity is rising faster than expected: Identify which asset class is growing. Camera originals and intermediate renders may need different retention rules, while proxies can often be regenerated from preserved masters.
- Transfers are slow or repeatedly fail: Check file size, network conditions, transfer limits, and whether the workflow is attempting to move unnecessary caches. Do not solve a transfer problem by deleting originals before a verified copy exists.
- Files exist but cannot be found: Improve the index, naming pattern, and metadata fields. Searchability is part of asset preservation.
- A project opens with missing media: Record the original paths, relink the project where possible, and preserve the dependency map. Also note software, plugin, and operating-system assumptions.
- Checksums do not match: Treat the copy as suspect. Re-copy from a known-good source, retain the failed verification log, and investigate the storage or transfer path.
- A playback file works only on one system: Label it as environment-specific and preserve a higher-quality or more portable master when available. Document the required device, software, resolution, and playback settings.
- Access changes after a handoff: Review permissions rather than sharing a broad account. Remove former project access where appropriate and preserve an accountable owner for the archive.
These signals also show whether the archive supports future creative work. If a producer can locate the original capture, understand the scene, reproduce a delivery, and identify the rights status without asking the original operator, the archive is doing its job.
When to revisit the archive
Revisit this workflow after every live production, asset handoff, platform migration, or repurposing project. A scheduled monthly or quarterly check is useful between events, while a broader review every six to twelve months helps identify changes in storage costs, supported formats, transfer limits, and software compatibility.
Use this practical verification checklist:
- Confirm that the archive index lists every required asset class, including originals, masters, playback files, metadata, proxies, and project files.
- Verify that the primary copy and at least one independent backup exist in their documented locations.
- Run or review checksum results for transferred and archived media. Investigate every mismatch rather than marking it as a minor warning.
- Test access with the permissions assigned to the intended producer, editor, and archive owner. Confirm that access is neither broader nor narrower than required.
- Restore a representative original, master, project file, metadata record, and playback file to a test location.
- Open the restored files with the documented software and check that linked media, audio, spatial information, and playback settings behave as expected.
- Record the date, tester, results, exceptions, and corrective actions in the archive log.
- Update the folder guide, naming rules, compatibility notes, and retention decisions before closing the review.
For additional context when preparing assets for a new spatial delivery, compare the media requirements with the volumetric, spatial, and 360 video comparison. If the archive will support an upcoming event, also revisit the production budget and network plan rather than assuming an old playback package will remain suitable. A verified, searchable archive turns past capture work into a usable library for future 3D live streaming, virtual performers, and immersive event content.