Oraphim LogoOraphim
Beta soon

Export

Export Settings

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

Updated August 27, 2026

Export settings

The export panel keeps the primary decision visible and places less common controls under advanced settings.

Range and timing

Confirm the full sequence or selected range, output duration, and frame rate. A frame-rate change alters cadence and should be deliberate.

Dimensions

Use the project dimensions unless a delivery target requires another size. Scaling can add processing time and can expose fine-detail issues.

Quality

Compressed video exposes bitrate or quality controls appropriate to the active encoder path. Higher values usually increase file size.

Audio and captions

Include the sequence audio when required. Captions can be burned into the picture or exported to supported subtitle files from the caption workflow.

Alpha

Use a format and project result that preserve alpha when transparency is required. MP4 and the current H.264 MOV path are delivery formats, not transparent mastering formats.

Use Export Settings in a production project

  1. Open Export / Render Queue and select the intended selected exportable timeline, composition, color session, or audio mix.
  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 Export Settings 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 export settings 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

  • Open the generated deliverable independently and verify range, codec, dimensions, frame rate, audio, and file integrity.
  • 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.