Oraphim LogoOraphim
Beta soon

Project management

Autosave

Use autosave in Oraphim with a production-safe workflow, practical example, verification steps, and common failure checks.

Updated August 27, 2026

Autosave

Use autosave to keep local Oraphim projects recoverable and their linked media available.

Workflow

  1. Save the active project before making structural changes.
  2. Keep project files, source media, autosaves, and exports in clearly named folders.
  3. Avoid moving or renaming source files outside Oraphim during an active edit.
  4. Use recovery or relink controls when Oraphim reports an unavailable project or source.
  5. Open the recovered or copied project and verify several representative shots.

Verification

Confirm that the project opens, media is online, timelines and compositions are present, and a short export completes from the restored state.

Use Autosave in a production project

  1. Open Project Hub / project services and select the intended current .orp project and referenced media.
  2. Establish the correct input state first—timing, media link, layer/node enable state, project settings, or source selection as relevant.
  3. Apply or adjust Autosave with one clear goal. Change the smallest set of controls needed to reach that goal so the result remains understandable and reversible.
  4. Review the complete affected range in context. Scrub difficult frames and also play at normal speed when motion or audio is involved.
  5. Save a named milestone before moving into another major operation, especially after graph changes, tracking, AI processing, relinking, simulation, or delivery setup.

Practical guidance

Autosave is a recovery layer, not a replacement for deliberate saves and versioned milestones. Save manually before risky structural changes or long renders.

A useful test is a short 5–10 second section containing both an easy case and a difficult case for this feature. Tune against the difficult moment without breaking the easy one. If two approaches are plausible, duplicate/version the project state and compare them rather than stacking both together blindly.

Verify the result

  • Reopen the result from disk and confirm project identity, media links, and the intended version.
  • Toggle/bypass the operation where possible and make sure the change you intended is actually responsible for the result.
  • Check selection, visibility/mute/solo state, node connections, track locks, range, and source identity when the result appears missing.
  • Save and reopen before treating a complex setup as reusable.
  • If this feature changes final pixels or audio, render a short review and inspect the file outside Oraphim.