Oraphim LogoOraphim
Beta soon

Assets

Importing Assets

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

Updated August 28, 2026

Importing assets

Select Import on an asset card to begin a managed background download.

Visual reference

Asset Browser import workflow

After an asset finishes downloading, confirm it appears in the project before depending on it in an edit or composition.

Progress

The card and task status report transfer progress. You can continue editing while the download runs.

Duplicate handling

Oraphim checks the destination and asset identity before creating another project item. Reusing an existing local asset avoids unnecessary downloads.

Completion

When the transfer and file validation succeed, the asset appears in the Media Pool. It can then be previewed, placed on the Edit timeline, or used in a composition.

Cancellation and recovery

Canceling stops the active transfer without adding an incomplete file. A failed transfer can be retried from the asset card.

Use Importing Assets in a production project

  1. Open Asset Browser and select the intended asset search or imported result.
  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 Importing Assets 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

Use importing assets only where it solves a defined creative or technical problem, and compare the result against the untreated state.

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

  • Confirm the downloaded asset appears in the Media Pool with usable metadata and preview.
  • 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.