Unreal Engine Nanite Guide: Using High-Detail Geometry in Architectural Scenes

Nanite is Unreal Engine’s virtualized geometry system, designed to render high-polygon models and dense scenes in real time. According to Epic Games’ official documentation, the system builds hierarchical clusters of triangles from imported geometry, then selects the detail required from the camera’s perspective during rendering and loads data as needed. For architectural visualization teams, this can simplify workflows, especially for models with many details that appear small on screen and for repeated assets. However, results should be measured based on content, materials, output resolution, and hardware.

When does Nanite make sense for a model?

The first step is to assess the geometry in the scene rather than enabling Nanite indiscriminately on every asset. Epic lists models with many triangles, triangles that appear small on screen, numerous instances, geometry that occludes other geometry, or models that cast shadows using Virtual Shadow Maps among suitable candidates. Sculptural details viewed up close, photogrammetry scans, and dense facade or environment models may meet these criteria.

Nanite aims to let you use high-polygon source geometry and reduce the need to bake detail into normal maps or prepare LOD chains for each model. The system manages detail level automatically based on screen resolution. This can simplify scene setup, but it doesn’t mean project performance no longer matters. Epic Games recommends evaluating instance count, triangles per model, material complexity, output resolution, and hardware together.

How to enable Nanite

1. Identify suitable assets. Start by selecting models with high geometric detail or many instances in the scene. A simple, standalone sky sphere that appears large on screen is given in the documentation as a less suitable example. The goal is not to flag every asset, but to find models where Nanite may reduce the workload.

2. Enable the option when importing new models. When importing a model prepared for Nanite, check the Build Nanite box. Unreal Engine spends processing time per asset to convert it and build its data; account for this time when importing many assets into large projects.

3. Enable it in bulk or for individual existing assets. Select a group of Static Meshes or Skeletal Meshes in the Content Browser and right-click; then choose Nanite > Enable. To enable it for a single asset, open the relevant asset editor and turn on the support option in the Nanite settings in the Details panel. In the Static Mesh Editor and Skeletal Mesh Editor, the option is called Enable Nanite Support; in the Geometry Collections Editor, it is called Enable Nanite.

4. Check whether lightmap UVs are needed. Epic recommends turning off Generate Lightmap UVs in projects that don’t use precomputed lighting with Lightmass. Enabling Nanite can increase dense-geometry import and Static Mesh build times; automatic lightmap UV generation also creates an extra UV channel and additional data for dense models. If your project doesn’t need these UVs, avoid unnecessary processing and data overhead.

Version, hardware, and known limitations

Check version requirements against the Unreal Engine version you’re using. The Unreal Engine 5.0 release notes state that Nanite on Windows requires DX12 and that DX11 is not supported. The Unreal Engine 5.1 notes specify DirectX 12 and Shader Model 6 for Nanite; according to the same documentation, no additional setting changes are required when using Vulkan. If you plan to upgrade a project or open it on different workstations, also verify the official requirements for the version you’re using.

Nanite documentation recommends using an SSD for geometry data streamed by the system. Also, don’t assume every technical limitation has been eliminated: the official documentation specifies an upper limit of 16 million streamed instances in a scene and says Morph Targets and deformation are not supported. World Position Offset also has limitations. In Unreal Engine 5.3, Nanite can optionally store custom tangent data; this choice can increase the memory and disk footprint of the asset by approximately 10 percent. Consider this cost, especially if low-polygon models require custom tangents.

The Unreal Engine 5.3 notes describe orthographic rendering as experimental; Nanite is intended to work with modern features such as Lumen and shadows in this projection. This is useful for architectural sheet-style views with fixed, parallel projection, but because the feature is experimental, don’t assume it will be production-ready without testing it in your scene.

Impact on architecture and visualization workflows

Nanite is worth considering for architecture firms, interior designers, and visualization artists who want to use highly detailed models, particularly when scenes contain many instances or geometry that appears small on screen. Automatic LOD management and less need to bake detail into normal maps can reduce some work during preparation. Nanite supports static meshes with Lumen for global illumination and reflections, as well as Virtual Shadow Maps.

On the other hand, importing and building assets can take time, and material complexity and resolution also affect performance. Before bringing assets into a scene, test a small number of representative models, check near and distant camera angles, and measure performance on the hardware you use. Factor the SSD recommendation and your project version’s DX12, Shader Model 6, or Vulkan requirements into the workflow. This lets you evaluate the benefits of high geometric detail alongside its production costs.

Common mistakes

• Assuming that enabling Nanite will improve scene performance regardless of content; Epic recommends measuring each content and hardware combination.

• Leaving Generate Lightmap UVs enabled when the project doesn’t use precomputed lighting with Lightmass.

• Planning to use DX11 or a different rendering path without checking the platform requirements for your Unreal Engine version.

• Assuming Nanite supports Morph Targets or every type of deformation; the official documentation notes limitations for these features.