Stop Hand-Authoring LODs: Nanite Killed the Low-Poly Hero

Here's a claim that gets pushback from veteran artists: hand-authored level-of-detail chains are a waste of your time. Not in every engine, and not for every platform, but if you ship on Unreal Engine 5, the low-poly hero is dead. Nanite, Epic's virtualized geometry system, imports film-quality meshes with hundreds of millions or billions of polygons, streams and scales them in real time, and removes polygon budgets, draw count budgets, and the need to hand-author LODs or bake normal maps (Unreal Engine documentation). That's not a tweak. It's a paradigm shift. And most art teams are still clinging to workflows built for 1996.

The Old Religion: Poly Counts as Currency

For decades, game art was a discipline of scarcity. You had a polygon budget, and you spent it like a miser. Unity's own optimization guide tells artists to spend the polygon budget on silhouette and large forms rather than small triangles, and to use textures and normal maps for fine detail (Unity mobile optimization guide). That's sound advice for mobile, but it's a reflex born of necessity, not a law of nature. The high-poly-to-low-poly pipeline—sculpt a dense mesh, retopologize a low-poly game mesh, unwrap UVs, bake detail onto the low-poly—exists because real-time engines couldn't afford millions of polygons per character (Game art pipeline). The hero asset was a 15,000-triangle LOD0 with a 2048x2048 texture and 2-3 draw calls, scaling down to an 800-triangle LOD3 (Technical artist roles). That spec sheet was your bible. But the bible was written for hardware that no longer exists.

Nanite Kills the Low-Poly Hero

Unreal Engine 5's Nanite virtualized geometry doesn't just raise the polygon ceiling—it vaporizes it. It imports film-quality meshes containing hundreds of millions or billions of polygons, streams and scales them in real time, and removes polygon budgets, draw count budgets, and the need to hand-author LODs or bake normal maps (Unreal Engine documentation). Think about what that means. The entire reason you retopologized, the entire reason you hand-placed edge loops around a character's mouth, the entire reason you baked normal maps—that reason is gone. Nanite renders the high-poly sculpt directly. You still need a clean mesh for deformation if it's a character, but for static props and environments, the low-poly mesh is an anachronism. The artist who spends a week hand-authoring five LODs for a rock is wasting time that could be spent sculpting more detail or painting better textures.

The Counter-Argument: Not Everyone Ships on UE5

I hear the pushback: "Nanite is only for high-end PC and next-gen consoles. What about mobile? What about Unity?" Fair point. Unity's dynamic batching only works for small meshes of roughly 225-300 vertices (up to 900 vertex attributes) depending on the shader (Unity Manual: Draw call batching). Mobile still demands brutal LOD discipline. The global game industry pulled in over $184 billion in 2024 with more than 3 billion active players (Newzoo), and a huge chunk of that is mobile. So yes, if you're shipping a mobile game in Unity, you still need your LOD chain. But here's the thing: that's a platform constraint, not a universal truth. The industry is bifurcating. On one side, you have the Nanite world where polygon counts are irrelevant. On the other, you have the mobile world where every triangle counts. The mistake is treating the mobile workflow as the default for all game art. It's not. It's a specialized discipline for a specific target.

What the Smart Artist Does Now

So what's the smart move? First, if you're working in UE5, stop hand-authoring LODs for static meshes. Let Nanite handle it. Spend your time on the high-poly sculpt and on PBR textures. The modern texturing pipeline uses Physically Based Rendering with maps like diffuse/albedo, normal, specular, opacity, and ambient occlusion, typically created in Substance Painter (Game art pipeline). Those maps still matter—Nanite may remove the need for baked normals, but you still need roughness, albedo, and the rest. Second, double down on stylized art direction. Stylized art tends to age better than chasing photorealism: cel-shaded games like The Legend of Zelda: The Wind Waker still hold up decades later, while realism-heavy games from the same era look dated (Stylized art longevity). Nintendo has long favored stylized art over realistic graphics, treating art direction rather than raw graphical fidelity as the primary visual goal (Stylized art longevity). Photorealism is a moving target; style is a constant.

A Concrete Example

Let's make this real. Imagine you're building a ruined temple environment for a UE5 game. Under the old pipeline, you'd block out the shape, sculpt a high-poly mesh in ZBrush, retopologize a low-poly game mesh, unwrap UVs, bake detail onto the low-poly, then texture and integrate into the engine (Game art pipeline). That's a week of work for one pillar. With Nanite, you sculpt the pillar in ZBrush, add every crack and chip, then export the high-poly directly into the engine. No retopology. No baking. No LODs. You can import a film-quality mesh with hundreds of millions of polygons and let Nanite stream and scale it in real time (Unreal Engine documentation). The time you save is enormous. You can spend it on making more assets, or on making the ones you have even more detailed.

The Skills That Still Matter

Does this mean retopology and UV mapping are dead? No. Characters still need clean topology for skeletal animation. Skeletal animation drives a character's skin with a hierarchy of bones: rigging places the bone structure and controls, and skinning assigns each vertex weights that determine how the bones deform it (Skeletal animation). A dense sculpt with millions of polygons won't deform well, so you'll still retopologize characters. And UV unwrapping is still essential for texturing—UV coordinates are stored per vertex, and the texture spans from (0,0) at its lower-left corner to (1,1) at its upper-right corner (UV mapping). But for static environment assets, the low-poly mesh is no longer a necessity. The artist who masters ZBrush sculpting, Substance Painter texturing, and Unreal's Nanite system will be the one who thrives. The artist who spends hours hand-authoring LODs for a rock will be the one who falls behind.

Bottom line

If you're working in Unreal Engine 5, stop hand-authoring LODs for static meshes. Let Nanite handle the polygon scaling, and put your effort into sculpting and texturing. That's the single best move you can make to future-proof your art skills.

Sources

• Unreal Engine documentation (Epic Games) - https://dev.epicgames.com/documentation/en-us/unreal-engine/nanite-virtualized-geometry-in-unreal-engine
• Game art pipeline (Wikipedia) - https://en.wikipedia.org/wiki/Video_game_art_design
• Technical artist roles (gamesindustry.biz) - https://www.gamesindustry.biz/technical-art-roles-what-they-are-and-how-to-get-one
• Unity mobile optimization guide - https://unity.com/how-to/mobile-game-optimization-tips-part-1
• Stylized art longevity (Creative Bloq) - https://www.creativebloq.com/art/character-design/the-new-star-fox-shows-how-easy-it-is-to-overdesign-a-beloved-character
• Newzoo (Global Games Market) - https://newzoo.com/