Fix: Unity Terrain Grass Not Rendering in URP

Here is how to fix Unity Terrain grass not rendering in URP. You migrate a Built-in Render Pipeline project to Universal Render Pipeline. The terrain itself still renders — ground textures look fine after the material upgrade. But the grass is completely gone. Trees might render as pink or invisible. URP’s terrain support is solid for the terrain itself but not for detail meshes unless you explicitly set them up.

The Symptom

After migrating to URP (or creating a new URP project), Terrain detail objects (grass, flowers, small rocks) do not render. Trees may render pink (missing shader), partially invisible, or shadowless. The terrain ground texture renders correctly thanks to automatic material upgrading, but details are skipped.

Selecting the Terrain component, you see grass prototypes configured with textures. Their “Detail Distance” is reasonable. But in-game, nothing.

What Causes This

Grass shader missing from URP. Unity’s built-in Nature/Grass and Nature/Grass (Billboard) shaders are built-in-only. URP has no drop-in replacement, and upgrade tools do not convert grass prototypes.

Tree material not upgraded. Trees are prefabs with materials. Automatic upgrade tools work on scene materials but may miss prefab-referenced materials if the prefab is outside scanning paths.

Detail mesh with Standard shader. Grass made of mesh prototypes (not billboards) uses whatever shader their material has. If that is the Standard shader, URP renders them as pink error.

URP asset not set in Graphics. Project Settings > Graphics > Scriptable Render Pipeline Settings must reference a URP asset. Without it, URP-specific shaders (including URP terrain and grass) may not resolve correctly.

Detail distance zero. The Terrain Settings > Detail Distance controls how far grass renders. If set to 0 (or something tiny), grass vanishes immediately beyond arm’s reach.

The Fix

Step 1: Upgrade terrain materials. Edit > Rendering > Materials > Convert Selected Built-in Materials to URP. This handles terrain, tree mesh, and standard materials. Trees often work after this step; grass does not.

Step 2: Replace grass prototype materials. For each grass Detail Prototype on your Terrain:

1. Open the grass Detail Prototype properties (Terrain > Paint Details > Edit Details).
2. Change Render Mode to “Vertex Lit.”
3. If you were using Billboard mode, create a custom Shader Graph grass shader or use a package like URP Grass Shader from the Asset Store.

For Shader Graph grass: create an Unlit graph, set the Render Face to Both (for two-sided grass), add Wind Vector and Texture inputs, sample the texture, use the Alpha Clip node to produce sharp edges. Assign the shader graph to a material and use that material for the grass prototype.

Step 3: Verify terrain shader on the Terrain component. Select your Terrain. In the Inspector, under Terrain Settings:

• Material: Universal Render Pipeline/Terrain/Lit (auto-assigned if upgrade succeeded)
• Detail Distance: 80 (higher = grass renders further)
• Detail Density: 1 or higher
• Tree Distance: 2000 (trees render out to this distance)
• Billboard Start: 50 (trees switch to billboards at this distance)

Re-paint grass and trees if the upgrade cleared them.

Step 4: For mesh-based details, upgrade prefab materials. If your grass uses mesh prototypes (full 3D blades) rather than texture billboards:

1. Find the mesh’s material asset
2. In the Inspector, change Shader from Standard to Universal Render Pipeline/Lit
3. Re-authenticate texture bindings (URP/Lit may reject some settings)
4. Rebuild the terrain details atlas (Terrain refresh happens automatically)

Trees with Speed Tree

SpeedTree-imported trees use custom shader code. URP supports SpeedTree via Universal Render Pipeline/Nature/SpeedTree shaders. If your trees look black or have no lighting, their materials point to the Built-in SpeedTree shader. Open each tree’s materials and swap shader to URP/SpeedTree variant (SpeedTree 7 or 8 based on your version).

In the tree asset’s Import Settings, ensure “Regenerate Materials” is checked and re-import to refresh.

Performance Considerations

Grass and detail rendering can be expensive. URP’s default detail settings aim for quality over performance. For mobile or low-end targets:

• Lower Detail Distance (40 instead of 80)
• Reduce Detail Density (0.7 instead of 1.0)
• Use billboards (cheaper) over mesh details for large areas
• Combine small grass clumps into larger mesh tiles

Profile the Terrain rendering in Frame Debugger — the detail mesh pass should take 1–3 ms on mid-range hardware.

Understanding the issue

Render pipelines have ordering: which pass runs when, what state is bound, which targets are written. Bugs at this layer are often invisible in code review and only manifest at runtime.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

This bug class disproportionately affects late-stage development. The work to surface it is interactive testing in realistic conditions, which only really happens after the gameplay is in place and assets are populated. Catching it early requires deliberate testing of conditions that look unimportant.

At the engine level, the behavior comes from a deliberate design decision in Unity. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

Verifying this fix in isolation is straightforward: reproduce the bug, apply the change, confirm the bug no longer reproduces. The harder verification is regression - did this fix introduce a new bug elsewhere? Run your standard regression suite, plus any tests that exercise the same code path with different inputs.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

There's almost always a less obvious case where the same problem applies. The reported case is the one a player hit; the related cases hide because they're rarer or affect fewer players. After fixing the reported case, search the codebase for the pattern - one fix often unlocks several.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

Live games surface this bug class at scale. What's a rare edge case in development becomes a daily occurrence once you have a few thousand concurrent players. The class isn't 'this player has a unique setup'; it's 'one in N thousand sessions will trigger this exact combination'.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

If this issue manifests under high load (many actors, many particles, many network connections), profile the post-fix code path with realistic counts. The original cost was a bug; the new cost is real work, and real work has a budget.

Diagnostic approach

Before applying any fix, gather enough context to be confident you're addressing the actual cause and not a similar-looking symptom. The cheapest diagnostic step is reproducing the bug deterministically - if you can't get the same failure twice in a row, your fix attempts will be hard to evaluate. Lock down the reproduction first.

For Unity-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

Third-party plugins often provide better diagnostics for their own behavior than the engine does. If the affected code is in a plugin, check the plugin's documentation for debug modes, verbose logging, or inspector tools - these can save hours of investigation when they exist.

Within Unity, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Boundary conditions deserve specific testing attention. What happens when the input is zero, maximum, negative, or NaN? What happens at the start of a session vs hours in? What happens at the boundary between two systems handling the same data? These are where bugs hide and where regression tests are most valuable.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

Document the fix and its rationale in the commit message or attached engineering doc. Future engineers will encounter related issues; the rationale tells them whether your fix is reusable or specific to the case at hand. Without rationale, the fix gets reverted or copied incorrectly.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“URP’s terrain support is there — but it requires a manual grass pass. Plan for it in your URP migration.”

Related Issues

For general URP shader issues, see URP Shader Not Rendering in Build. For related terrain issues, Terrain Holes at Chunk Boundaries covers seam issues.

URP-compatible grass shader, re-paint, tune Detail Distance. Terrain is easy; details are not.