World Partition UE5

World Partition is the open-world level management system introduced in Unreal Engine 5 that replaces the older sublevel and level-streaming workflow. Instead of manually carving a map into sublevels and writing streaming logic, World Partition divides the world into a configurable grid of cells and streams them in and out automatically based on camera distance and loading range. For environment artists and technical directors at studios like Sinfull Studios working on large virtual production environments or game levels in Saskatchewan and beyond, it fundamentally changes how you structure, collaborate on, and optimize a project.

What Problem Did the Old Sublevel System Actually Have?

The classic UE4 workflow had you splitting a large map into sublevels — essentially separate .umap files — and writing level-streaming volumes or blueprint logic to load and unload them at runtime. It worked, but it created real friction. Merging sublevels in source control was painful, artists frequently locked each other out of the same sublevel, and managing the boundaries between cells was manual and error-prone. The larger the environment, the worse the organizational overhead became. World Partition was built to solve that at scale.

How Does the Grid-Based Streaming Actually Work?

When you enable World Partition on a level, UE5 overlays a uniform grid across the entire world. Each cell in that grid has a loading range — the distance from the streaming source (typically the player or camera) within which its contents are loaded into memory and rendered. You tune cell size and loading range per project. A large open-world environment might use 128-meter cells with a 512-meter loading range; a smaller dense environment might use tighter settings. The engine handles all the async loading, unloading, and transition logic automatically. You do not write any streaming volumes or logic by hand.

What Are Data Layers and When Should You Use Them?

Data Layers are a World Partition feature that lets you tag actors with a named layer and then toggle that layer on or off at runtime — or even at edit time. They are the replacement for the old “always loaded” sublevel pattern. Common uses include day/night state variations, season variants of the same landscape, story-phase-dependent props, or separating gameplay-critical actors from purely aesthetic ones. You can stack multiple Data Layers on a single actor and control them independently. In a virtual production context, Data Layers are a clean way to manage scene state changes without duplicating geometry.

What Are HLODs and Why Do They Matter for Performance?

Hierarchical Level of Detail (HLOD) in World Partition generates simplified proxy meshes for regions of the world that are outside the full streaming range. As the camera moves away from a cell, rather than popping to empty space, the engine substitutes a low-poly imposter that represents the visual mass of everything inside that cell. This keeps distant landscapes, cities, and forests readable without the full geometry cost. In UE5, HLOD generation is automated — you configure it per World Partition level and let the HLOD builder cook the proxies. Nanite handles per-object LODs at close range; HLODs handle region-level culling at distance. They work together, not in opposition.

How Does One File Per Actor Change Team Collaboration?

One File Per Actor (OFPA) is the source control model that World Partition depends on. Each actor in the level is stored as its own small file on disk rather than being packed into a single monolithic .umap. The practical result is that two artists can work in the same level simultaneously without constantly locking or conflicting, because they are editing different files. Merges become granular — a conflict on actor A does not block actor B. For any team beyond a single person, OFPA is the feature that makes World Partition genuinely practical. It does require a source control setup that handles large numbers of small files efficiently; Perforce and Git LFS both handle it, but you need to configure file counts appropriately.

When Do You Actually Need World Partition?

Not every project needs it. For a contained virtual production stage environment — a single interior, a stylized set piece, a bounded exterior — a standard persistent level with good LOD discipline and culling will perform fine and is simpler to manage. World Partition becomes worth the setup cost when:

  • The world is large enough that no single camera position can see all of it at once
  • Multiple artists need to work in the same level simultaneously
  • You are generating the environment procedurally at scale (PCG, landscape layers, instanced foliage)
  • Runtime streaming is needed — open-world games, large architectural walkthroughs, or expansive virtual location scouts

How Does It Interact with Lumen, Nanite, and PCG?

World Partition is designed to work alongside UE5’s other large-scale systems. Nanite provides continuous LOD on individual meshes so streamed-in actors render efficiently regardless of polygon count. Lumen’s software ray tracing operates within the loaded cells and degrades gracefully at the world boundary — you may need to tune the Lumen scene range to match your streaming radius on very large worlds. Procedural Content Generation (PCG) integrates directly with World Partition: you can run PCG graphs that write actors into the partition grid, with those actors automatically partitioned and streamed like anything else. For environment art at Sinfull Studios, this combination — PCG populating a World Partition level with Nanite meshes lit by Lumen — is the current production-ready pipeline for large environment builds.

What Are the Tradeoffs and Gotchas to Know Before You Start?

World Partition introduces complexity you need to budget for. Cook times are longer because the engine must build HLOD proxies and partition data. Not every actor type streams correctly by default — Blueprint actors with complex construction scripts, some AI controllers, and certain gameplay systems need explicit handling to work with streaming. The editor can feel slower on very large worlds when loading the full partition grid. And migrating a legacy project from sublevels to World Partition is a non-trivial conversion — plan for it early, not as an afterthought. If you are starting a new large environment project from scratch in UE5, enable World Partition from day one. Retrofitting it is always harder than designing for it.

Explore Environment Art in Unreal Engine at Sinfull Studios for more.

Frequently Asked Questions

What is World Partition in Unreal Engine 5?

World Partition is UE5’s open-world level management system that divides a level into a configurable grid of cells and automatically streams them in and out based on camera distance. It replaces the older manual sublevel and level-streaming volume workflow, removing the need to write custom streaming logic and enabling large teams to collaborate on a single level simultaneously through the One File Per Actor (OFPA) storage model.

How does World Partition differ from the old UE4 sublevel streaming system?

In UE4, developers manually split large maps into sublevels (.umap files) and wrote streaming volumes or Blueprint logic to load and unload them. World Partition automates this entirely using a spatial grid — the engine streams cells based on proximity to the camera or player with no manual streaming volumes required. One File Per Actor also means individual actors are stored as separate files, eliminating the source control bottlenecks that came from multiple artists editing the same sublevel file.

When should a virtual production or game development project use World Partition in UE5?

World Partition makes sense when the environment is large enough that streaming is necessary, when multiple artists need to work in the same level concurrently, or when procedural content generation (PCG) is being used to populate the world at scale. For contained, single-room or bounded set environments common in virtual production LED volume work, a standard persistent level with good LOD discipline is often simpler and sufficient. World Partition adds the most value on open-world games, large architectural visualizations, and expansive environment scans or location-scout assets.

Related reading from Sinfull Studios

Planning a virtual production, Unreal Engine, or VFX project in Regina or anywhere in Saskatchewan? Request a quote from Sinfull Studios.