Using the Foliage Tool Efficiently in Large UE5 Worlds

Foliage is one of the easiest ways to destroy performance

A beautiful dense forest painted with the Foliage tool can easily become millions of instances. Nanite helps a lot, but overdraw, collision, and shadow casting will still kill you if you're not careful.

The Foliage tool itself also becomes slow when you have hundreds of foliage types or massive paint strokes on a large landscape.

This guide collects the practical habits that keep large worlds editable and running.

Instance management and streaming

Use World Partition + HLODs aggressively. Foliage can be included in HLODs so distant forests become cheap impostors or merged meshes.

Split your foliage types into 'Hero', 'Mid', and 'Far' categories. Hero types only paint near the camera or in key locations. Far types can be much lower density or use cheaper meshes.

Enable 'Cull Distance' and 'Start Cull Distance' per foliage type. Many people leave everything at default and then wonder why frame rate tanks 2 km away.

Painting workflow that doesn't melt the editor

Paint in small strokes. Large single brush strokes on a 8k+ landscape can lock the editor for minutes.

Use multiple foliage palettes (one per biome) and only have the active biome types enabled when painting that area. Disable everything else.

Save your tuned foliage settings as Foliage Type assets and reuse them. Re-creating the same density/scale/rotation settings by hand every time is slow and inconsistent.

When to stop painting and switch to PCG or Blueprints

Once you have more than ~10-15 foliage types per biome or you are painting the same rules across 10+ levels, consider moving the bulk to PCG.

Keep the Foliage tool for hero clusters and fine detail. Let procedural rules handle the repetitive ground cover.

Profile with the foliage stats and Nanite overview. The number that matters is not 'how many instances' but 'how many are actually rendered and shaded this frame'.

FAQ