In brief
- SVT streams only the texture tiles needed on screen into memory, in fixed-size chunks.
- Texture samples in materials using SVT must match the Virtual Sampler Type.
- RVT generates shading data on the GPU at runtime and can be used with terrain materials.
- You can measure virtual texture memory and performance costs with in-project stats commands.
What you’ll learn in this guide
Unreal Engine offers two different approaches to virtual texturing: Streaming Virtual Texturing (SVT) and Runtime Virtual Texturing (RVT). SVT manages texture streaming from disk according to the portions visible in the scene, while RVT generates texture data on the GPU as the scene runs. In this guide, you’ll learn how to prepare SVT textures and materials, import UDIM textures, set up the scene components required for RVT, and assess the resulting costs.
Virtual texturing does not automatically mean better performance in every project. Material sampling costs, memory use, visual quality, and texture loading during camera movement should all be evaluated together.
Requirements
You’ll need an Unreal Engine project and editable texture, material, or terrain content. Epic’s documentation on this subject does not specify a particular Unreal Engine version, user account, or hardware requirement, so no additional version or hardware requirements are assumed here. Creating an alternative material for platforms that do not support virtual texturing is one of the options documented for RVT.
For SVT, Virtual Texture Streaming must be enabled on the texture asset, and the Texture Sample nodes in the material must use a Virtual Sampler Type compatible with virtual texturing. The RVT workflow requires a Runtime Virtual Texture asset, a Runtime Virtual Texture Volume assigned to it in the scene, and correctly prepared materials.
1. Prepare textures and materials for SVT
First, select the texture asset you want to use in the project in the Content Browser. Right-click the texture and choose Convert to Virtual Texture. The Convert To window that opens shows the selected textures and the materials that reference them. Click Ok to enable Virtual Texture Streaming for the texture; the Texture Sample nodes in the relevant materials are also converted to the virtual sampling type.
If you want to change the settings manually instead of using the conversion menu, double-click the texture asset to open the Texture Editor. Under Details > Texture, enable Virtual Texture Streaming. However, manual conversion can invalidate materials that use the texture. Open those materials and set the Sampler Type value on their Texture Sample nodes to the appropriate Virtual type. For example, a virtual color texture requires Virtual Color; the Color type does not match.
If the sampling type in a material is incorrect, Unreal Engine may display an error in the Stats panel and below the relevant node. Adding a virtual texture directly to the Material Graph automatically assigns the Virtual sampler type. If you use Material Instance parameters, make sure the sampler type in the parent material is also compatible with the virtual texture.
2. Import UDIM textures and measure SVT
To import UDIM images, use a shared base name, a four-digit coordinate, and a supported image format in the filenames. The naming pattern given in the documentation is:
BaseName.####.[Support Image Format]For example, files named MyTexture.1001.png are scanned alongside other images with coordinate numbers and the same base name. Unreal Engine can import these images as a single Virtual Texture Asset. Different UDIM tiles can have different resolutions; smaller images can be sampled in the same space as larger tiles without converting the source texture into a large, high-resolution image.
Rather than estimating performance and memory use, measure them in the project. Open the console and run these commands:
stat virtualtexturing
stat virtualtexturememoryThe first command shows the virtual texturing scene cost in milliseconds, along with counters for page tables. The second displays virtual texture memory counters for the current scene. To see tile boundaries in materials using SVT, run r.VT.Borders 1; to turn the display off, enter r.VT.Borders 0.
3. Set up an RVT asset and scene volume
In the Content Browser, right-click or use the Add New button to create an RVT Asset via Materials & Textures > Runtime Virtual Texture. Open the asset and configure its size, tile size, and supported material properties. Choose the material type based on which properties you want to store; options range from Base Color only to types that also include normal, roughness, and specular information.
Next, add a Runtime Virtual Texture Volume to the scene. The volume places the RVT Asset in the scene and should cover the components that will write to the RVT. With the volume selected, use the Source Actor field in the Transform from Bounds section of the Details panel to select the terrain or a suitable scene actor; click Set Bounds to fit the volume to the selected actor.
Materials that write to the RVT must be correctly prepared for it. In material expressions, Runtime Virtual Texture Output is used for writing, while Runtime Virtual Texture Sample is used for sampling. Add the relevant RVT Asset to the Render to Virtual Textures field in the Details panel for the scene components. For a component to write to the RVT, the asset must be assigned to a volume in the scene, and the materials must also be set up correctly.
4. Use it in terrain and architectural visualization workflows
RVT is suitable for components such as Landscape, Landscape Splines, static meshes, and instanced static meshes. Blending decal-like materials, splines, and different surfaces across terrain is one of its key use cases. Since RVT content is not fully updated every frame, animated or moving components are not good candidates; static components are preferable.
In architecture, interior design, and archviz projects, this distinction matters particularly in scenes where terrain and surfaces around a building are rendered together. SVT can be considered for managing the visible portions of large-resolution textures, while RVT can be explored for blending terrain materials, splines, and scene components. However, the right approach depends on the project’s materials and measured costs. RVT sampling is more expensive than traditional texture sampling; stacks of samples using the same UVs and sampler source can be merged. Using different UVs can result in more virtual texture stacks and higher sampling costs.
Common mistakes and next steps
Failing to update materials that reference a texture after manually converting it to SVT can cause errors due to an incorrect sampler type. Also, limiting low-resolution mip levels in highly detailed or noisy textures can cause aliasing or a Moiré effect. SVT can only load a required tile after a frame has been rendered, so high-resolution tiles may appear on screen after the camera has moved.
Don’t assume virtual textures have the same cost and quality characteristics as traditional textures. Texture dimensions in the project must be powers of two; increasing the edge tile setting can increase memory use. Although mip transitions with TAA generally look similar to conventional texture filtering, noise can occur under some conditions.
After the initial setup, review the scene’s virtual texture and memory counters; enable boundary visualization to inspect the tiles. If you’re using RVT, verify that the volume covers the scene components, the materials use the correct RVT Asset, and moving components are not writing to the RVT unnecessarily.
Source and license
This tutorial has been adapted into Turkish from Epic Games’ Unreal Engine documentation on virtual texturing, Streaming Virtual Texturing, and Runtime Virtual Texturing. The sources were provided as lisans=serbest. The example naming pattern and commands are reproduced to illustrate the technical usage in the documentation.
Sources
3 sourcesSource texts are not republished; short quotes are marked, everything else is our own summary and commentary.
For architecture and visualization teams in Turkey, virtual texturing is worth considering, especially for managing large textures and terrain materials. However, adding SVT or RVT to a project solely in the hope of saving memory is not advisable; material costs, potential visual artifacts, and loading behavior during camera movement should be measured in the scene.
The sources do not specify any additional licensing or hardware requirements, but performance results depend on the project. Teams should therefore create a small test scene with their existing materials and review the measurements before converting production files. For RVT, static components and correct volume bounds require particular attention.
Frequently asked questions
How do you enable Streaming Virtual Texturing in Unreal Engine?
Right-click the texture and choose Convert to Virtual Texture, or enable Virtual Texture Streaming in the Texture Editor. Also check that the material’s Texture Sample nodes use the appropriate Virtual Sampler Type.
What is Runtime Virtual Texture used for?
RVT generates texel data on the GPU at runtime and caches shading data across large areas. It can be used for Landscape, splines that conform to terrain, and decal-like materials.
How do you measure virtual texture costs in Unreal Engine?
`stat virtualtexturing` shows scene costs and page table counters, while `stat virtualtexturememory` displays virtual texture memory counters.



