Export

Project archiving

Understand Oraphim's folder-based .orp and Media collection workflow and how it differs from rendering a delivery master.

Updated August 27, 2026

Archive a project

Oraphim's project archive is a folder-based collection workflow, not a rendered movie and not a proprietary database bundle. It creates a portable project copy with collected source media.

What Oraphim creates

When you archive to a destination folder, Oraphim:

  • validates that referenced media files are currently available;
  • creates a Media subfolder;
  • copies project media into that folder;
  • reuses one collected copy when multiple project items reference the same source path;
  • adds filename suffixes when different sources would collide by name; and
  • writes a copied .orp project in the archive root with media references pointing at the collected copies.

If media is missing or unavailable, archiving stops and asks you to relink it rather than silently producing an incomplete archive.

Archive safely

  1. Save the active project and resolve offline/missing media first.
  2. Choose Archive Project and select an empty or clearly named destination folder.
  3. Let collection finish before moving or deleting any originals.
  4. Open the archived .orp copy and inspect representative video, audio, images, compositions, and the final timeline.
  5. Render a short review from the archived copy before treating the archive as verified.

Storage and backup

An archive is only one copy. For long-term preservation, keep at least one independent backup and retain any external fonts, licensed assets, model packages, plug-ins, or source materials that are not part of the collected project-media operation.

Archive versus export

Use Archive Project when you need an editable project plus collected media. Use Export / Render Queue when you need a final video, image sequence, audio mix, or professional interchange master. For important jobs, keep both: an editable archive and one or more approved delivery/master files.