Create High-Quality Archviz Renders with Unreal Engine Movie Render Queue

What will you learn in this guide?

Real-time rendering in Unreal Engine is useful for quickly reviewing and editing a scene. But when you need more control over output for an animation or presentation, Movie Render Queue (MRQ) lets you queue sequences and render them offline. Because offline rendering isn’t subject to the same constraints as real-time performance, you can use settings designed to deliver higher quality in areas such as ray-traced lighting and reflections, motion blur, and anti-aliasing.

In this walkthrough, you’ll add a Level Sequence to MRQ, choose an output format, and save your settings. In the final section, we’ll cover when to consider MRQ’s node-based alternative, Movie Render Graph (MRG), and what its current limitations are. Epic Games’ guides also include steps for Windows 10 64-bit users. Since the interface and project settings can differ between Unreal Engine versions, compare the options on screen with the version you’re using.

Requirements and preparation

First, you’ll need an Unreal Engine project to render and a Level Sequence in it. Epic’s ArchViz Interior sample project features a photorealistic scene that uses ray tracing. To use this sample, you’ll need a graphics card that supports ray tracing and DirectX 12 ray tracing. If you’re working in another project, you don’t need the sample project; you can use your own sequence.

MRQ must be enabled as a plugin. From the top menu, open Edit > Plugins, search for Movie Render Queue or Movie Render Pipeline, and enable the plugin. Then restart the editor. Epic’s documentation shows that the plugin names may appear differently in some versions, so check the options listed in your project.

The sources don’t specify an account requirement. They also don’t give a single minimum hardware requirement that applies to every project. Don’t confuse the compatible graphics card requirement for the ray-traced ArchViz Interior sample with general MRQ use.

Epic’s Windows guide describes a registry setting to help prevent Windows from resetting the driver during long GPU operations as an optional but recommended preparation step. This requires administrator permissions and involves editing the registry; consider it only if you’re experiencing the relevant issue, and follow the guide’s warnings. The guide specifies a TdrDelay value of 60 seconds.

Rendering with MRQ: step by step

1. Check the sequence in Sequencer. Open the Level Sequence you want to render from the Content Browser. If there are multiple cameras or shots, review the timeline and decide which range to render. In the ArchViz Interior sample project, sequences are in the Content > Cinematic folder; the guide names the main sequence archviz_cine_MASTER.

2. Open the Render Queue window. From the top menu, go to Window > Cinematics > Movie Render Queue. Alternatively, use the menu next to the Render Movie button in Sequencer. In the window, click + Render and select the Level Sequence. You can also drag the sequence from the Content Browser into the window.

3. Open the job settings. Open the sequence job’s settings and use the + Setting button to add the options you need. You can enable or disable settings for a specific render. Options such as the output folder and file format are configured in the job settings. Save your settings as a preset to reuse the same configuration.

4. Choose an output format for your needs. PNG uses lossless compression and supports an alpha channel, making it suitable for work that requires a transparent background; files may be larger than JPGs. EXR is intended for compositing workflows involving 16-bit HDR and linear data, and can carry an alpha channel. JPG is lossy and produces smaller files; the guide recommends it for previews. BMP is lossless but uncompressed, so its files are large. When choosing, consider the delivery format, whether you need transparency, and file size together.

5. Review sampling and quality settings. The Anti-aliasing setting in MRQ controls the number and types of samples used for the final image. Camera settings can affect results such as exposure and motion blur. If needed, add the Console Variables setting to run console variables during rendering; the right variables depend on the project and desired result. Since the sources don’t recommend a single value for every scene, run test renders for your project.

6. Start the render and verify the output. A local render in MRQ runs in the same process as Unreal Engine; the remote option launches a separate process and requires project changes to be saved to disk. You can add multiple jobs to the queue. A preview window appears during rendering; Epic notes that this preview may not match the quality of the final output. Check the final files in the output folder specified in the settings.

When should you use Movie Render Graph?

MRG is a system for defining render operations with nodes. You can build a simple graph for a single shot, or create reusable graph assets for multi-shot workflows. For those familiar with MRQ, the key difference is that settings are configured through nodes in a graph, giving you more detailed control over render layers.

When moving MRQ settings to MRG, keep these changes in mind:

• File naming is managed by the File Type Output node.

• Temporal sampling is configured in the Sampling Method node; spatial sampling and the anti-aliasing method are set in the Renderer node.

• The render path is selected by connecting Deferred or Path Tracer nodes to the render chain; you can make the selection per render layer.

• Color output settings have moved to the File Type Output node.

MRG doesn’t support every MRQ feature. Epic’s migration guide lists high-resolution rendering, UI Renderer, nDisplay Rendering, the Apple Pro Res plugin, Final Cut Pro XML, and Prestreaming Recorder among the unsupported features. So, if your current workflow depends on any of these options, confirm the requirements before moving to MRG. MRQ’s settings and preset structure and MRG’s graph-based approach are not fully interchangeable.

Considerations for architecture and archviz workflows

For architects, interior designers, and visualization teams, MRQ’s main benefit is the ability to batch-process sequences in the same project and standardize output settings with reusable presets. Teams producing stills for presentations, animation sequences, or images with alpha channels for compositing can save different configurations for each delivery format. MRG may be a good fit for more complex, repeatable production workflows where settings for individual render layers are managed in a graph.

High sample counts, ray tracing, and long sequences can affect render times; the sources don’t provide time or performance guarantees for any hardware. So, before rendering an entire animation, test a short range and assess the quality in the output file. If you need a transparent background, the project and scene settings must also support alpha output. Unreal Engine 5.5 documentation says alpha support has been simplified to a single Alpha Output checkbox in project settings, while another Epic guide describes an older settings path. Use the setting for your version; don’t assume both paths should be available in the same version.

Common mistakes and next steps

• Enabling the plugin without restarting the editor: Enable the MRQ plugin and restart the editor.

• Trying to achieve transparency with the file format alone: Selecting PNG or EXR may not be enough; alpha support also depends on project and scene settings. You may need to hide opaque scene elements to get a transparent background.

• Assuming the preview shows final quality: The MRQ preview displays the latest samples from the GPU and may look lower quality than the final render.

• Assuming every MRQ feature is also available in MRG: Before migrating, check for unsupported features, especially high-resolution rendering and UI Renderer.

• Not saving project changes before remote rendering: The remote option runs in a separate process and uses files saved to disk.

As a next step, choose a format such as PNG or EXR based on your delivery requirements and run a short test render. Then save your render settings as a preset. If your project has a multi-layer or multi-shot setup, explore the MRG example; decide whether to migrate based on the features you need and the list of supported features.

Sources and licensing

This guide has been adapted into Turkish from Epic Games’ documentation on the Movie Render Pipeline, creating high-quality images with Movie Render Queue, and migrating to Movie Render Graph. The sources are official Epic Games documentation pages, and their source records list the licenses as free.