Skip to Content
Export & renderingRender queue

Render queue

Window → Render Queue.

Queue several compositions, formats and resolutions, choose an output folder once, and let them render while you keep working.

The model

  • Jobs target a composition, a format and an output resolution.
  • Jobs run one at a time.
  • Each job runs the real deterministic offline renderer — the same code path as a single export. Nothing about a queued render is a shortcut.

Controls

ActionEffect
Add jobQueue the current composition
Start / Pause allPause aborts the frame loop and kills the running encoder
SkipMove past one job
RemoveTake a job out of the queue
Clear finishedTidy up
Output ModulePer-job settings dialog

Progress and failure

Jobs report true per-frame progress and elapsed time — not an animated bar that means nothing.

When a job fails, it reports the actual reason. Cancellation is enforced server-side as well as locally, so a cancelled cloud render actually stops.

Existing files are never overwritten. Pick an output folder once and the queue writes into it without interrupting you to ask.

Output resolution

Independent of composition size. A quarter-resolution review copy still frames the whole composition. Queue a full-resolution master and a quarter-resolution review copy of the same composition as two jobs.

Performance

The queue is throttled so the interface stays responsive while it works, and GIF and zip encoding happen in a worker.

On the desktop, the actual encode runs in an ffmpeg child process, so it does not compete with the editor’s UI thread or its GPU context at all.

A useful pattern

For a deliverable that needs several outputs:

  1. MP4, Full — the master.
  2. WebM, Full — the alpha version for the web.
  3. MP4, Quarter — the review copy to send round.
  4. Still frame — the thumbnail.

Queue all four, choose the output folder, start, and go and do something else.

Last updated on