Unreal Engine Movie Render Queue Guide: Step-by-Step Setup for Architectural Rendering

Unreal Engine’s Movie Render Pipeline can export a Level Sequence as a high-quality image or video. Epic Games’ official documentation describes Movie Render Queue (MRQ) as a tool for queuing and batch-processing jobs, while Movie Render Graph (MRG) organizes render operations in a graph-based structure. Both tools can be used to manage output settings and prepare reusable jobs for architectural visualization sequences. This guide follows the workflow in Epic’s Movie Render Pipeline documentation; notes on the alpha channel also explain changes identified in the documentation for UE 5.5.

1. Enable and open Movie Render Queue

First, enable the Movie Render Queue plugin. From the main menu, go to Edit > Plugins, find the plugin in the Rendering section, and enable it. Restart the editor to apply the change. The project you render must contain a Level Sequence; the queue creates render jobs from these sequences.

To open the queue, go to Window > Cinematics > Movie Render Queue. Alternatively, click the vertical ellipsis next to the Render Movie button in the Sequencer toolbar and select Movie Render Queue. In the window that opens, use + Render to add a Level Sequence Asset. You can also drag sequences from the Content Browser into the Jobs area.

Each top-level entry in the queue is a render job. Open the job’s Settings section to choose render settings, an output folder, and an export format. The + Setting button lets you add settings to the current configuration or toggle them on and off. Check which options are available for your version and project; don’t assume a specific value that isn’t stated in the documentation.

2. Organize jobs and presets

1. Select the sequence to add to the queue using + Render. Jobs appear in the Jobs area, where you can manage multiple jobs.

2. Open a job’s settings and choose the render settings, output directory, and export format. The Output link opens the folder where the image or video will be saved.

3. Select the job and review its name, sequence, Level, author, and comment in the Job Details area. By default, the job name is the sequence asset’s name, but you can change it. The author and comment fields may be empty initially.

4. To create a reusable queue, choose Save Queue As from the Unsaved Queue menu in the toolbar and save a Queue Preset asset. You can later select this asset to load the saved job list. Subsequent changes won’t modify the asset unless you save them separately with Save Queue.

MRQ is suited to managing multiple jobs and batch rendering. Its temporal sub-sampling feature also helps create high-quality radial motion blur. With suitable project and scene settings, you can render images containing translucent pixel values; 16-bit HDR images with linear data can also be exported. These capabilities make it important to check the output format and scene configuration against the intended use.

3. Extend your setup with Movie Render Graph

MRG defines the frame range, render settings, and file types to export in a node-based graph. You can create a simple graph for a single shot or build workflows spanning multiple shots. Saving graphs as assets makes it easier to reuse and share settings across a team.

To open MRG, first use the Movie Render Queue window. In the Settings column, select Movie Render Graph (Beta) from the Unsaved Config menu. Then create a new graph asset by choosing Movie Render Graph under Create New Asset; name and save it, then open the asset from the queue to edit it. Epic recommends familiarity with MRQ and render settings before using MRG. MRQ’s legacy preset system can be used alongside MRG.

4. Choose alpha, local rendering, or remote rendering

If you need an alpha channel, check the project settings. According to the UE 5.5 documentation, a single Alpha Output checkbox replaces the older experimental alpha options. It is disabled by default, though some Film/TV/Virtual Production templates may enable it automatically. You can find the setting under Edit > Project Settings, in the Default Settings section of the Rendering category under Engine. Since its location and behavior differ in earlier versions, consult the documentation for your version if you’re using a different release.

To use holdout with the Deferred Renderer, you must also enable the Support Primitive Alpha Holdout (Deferred) project setting. Film/TV templates and examples may enable it by default; in MRG, if you configure holdout on a Modifier while the project option is disabled, the tool notifies you.

When you start a render, Render (Local) runs the job in the same process as Unreal Engine and starts a Play in Editor session. You don’t need to save changes for this method. Render (Remote) starts a separate process, so you must save project changes for the external process to access the files. The remote option can also provide a foundation for workflows such as a render farm; the launch command is written to the Output Log.

What changes in architectural and visualization workflows?

MRQ is useful for architecture firms, interior designers, and visualization teams that want to organize settings and outputs for multiple sequences in a single queue. Saved queue presets can reduce the need to recreate the same list for recurring jobs. MRG offers a more flexible structure for teams that need reusable render rules spanning different shots.

Using offline rendering to target high-quality output can offer advantages such as ray-traced global illumination and reflections, motion blur, and fewer anti-aliasing artifacts. However, the documentation provides no specific hardware requirements or render times. When choosing between local and remote rendering, consider whether the current workflow, saved state of the project files, and target output format are compatible; if you need alpha or HDR, check the result before delivery.

Common mistakes

• Forgetting to restart the editor after enabling the plugin.

• Not saving project changes before starting a remote render.

• Assuming alpha output is enabled by default or failing to check the project setting required for holdout.

• Expecting changes made in the queue to update the saved Queue Preset automatically.

• Treating the render preview as representative of final image quality. According to Epic, the preview may use the latest sample data from the GPU and appear lower quality than the final render.