Exporting, versions and project history

Save and version

Every successful source replacement creates a new numeric project version. API and Agent edits include the version they inspected; if someone else saved first, the write returns a conflict instead of overwriting newer work.

This is optimistic concurrency: read the latest project, reapply the intended bounded change, then save against the new version.

Preview and export

Use preview for creative review and export for the final artifact. A video should be watched across transitions and audio boundaries; a still should be checked at its actual output aspect ratio and, when relevant, against transparent surroundings.

The public V2 output contract supports static PNG, JPEG/JPG and WebP output, plus the video format and codec combinations listed by the live OpenAPI reference. Availability can depend on the requested output kind.

Render lifecycle

Exports are asynchronous:

1. queued
2. rendering
3. completed, failed or cancelled

The finished render resource contains safe artifact metadata and a temporary download URL. Server integrations can use the authenticated artifact route or signed webhooks.

See Rendering, operations and outputs for code examples.