Render queue; pre-rendering or baking
The queue holds multiple exports; pre-rendering or baking turns heavy live effects into fixed results that play and render faster.
See it
What it is
A render queue is a list of export jobs with their own render settings, output modules, and destinations. Pre-rendering turns a heavy nested composition into an intermediate movie and uses that movie in later work. Baking is the broader idea of committing live calculations, effects, or animation to fixed pixels or cached data.
Reach for the queue when several versions or deliverables can render unattended. Pre-render or bake a finished, expensive section when particles, blurs, nested comps, or dynamic links make previews and repeated exports slow. Unlike a temporary preview cache, a named intermediate file can be moved, reviewed, and reused. Adobe Media Encoder exists for the same reason: it takes the queue into a separate application so After Effects stays usable while jobs run.
Gotcha: baked pixels are less editable. A change upstream means baking again, and the intermediate must preserve everything later stages need: resolution, frame rate, bit depth, color management, and alpha. Do not bake to a low-bitrate delivery codec or discard transparency just to save a little disk space.
Ask AI for it
Set up this Adobe After Effects project for unattended rendering. Add each final comp to the Render Queue with Best Settings and a clearly named output path. Pre-render the heavy nested particle comp to QuickTime Apple ProRes 4444 with RGB + Alpha and Straight alpha, then set Post-Render Action to Import & Replace Usage so later renders use the baked movie. Keep the source comp in the project, match its frame rate and dimensions exactly, and use ProRes 422 HQ instead for opaque intermediates that do not need alpha.