Last reviewed 31 Jul 2026

Applies to

Unity URP projects Non-VRChat Unity applications Material and shader migration

Difficulty Beginner

URP

Start here when a Unity project uses Universal Render Pipeline or needs to migrate toward it. The linked guides cover URP setup, renderer data, material conversion, renderer features, optimization, and common migration mistakes.

What URP actually changes

URP is not only a graphics toggle. Once a project uses URP, it changes the expectations around:

• material shaders
• renderer configuration
• lighting and post-processing workflow
• imported asset compatibility
• performance tuning decisions

That is why many Unity problems that look random are really render-pipeline mismatch problems.

URP concept	Why it matters
URP Asset	Stores project-level URP settings such as rendering quality, shadows, HDR, render scale, and renderer list.
Renderer Data	Controls how cameras render, including renderer features and forward/deferred-style choices where available.
Quality settings	Different quality levels can use different render pipeline assets.
Materials and shaders	Materials must use shaders compatible with the active render pipeline.
Renderer features	Effects such as decals, fullscreen passes, or screen-space features can add cost across cameras.

Best starting path

If you are new to URP, move through these pages in order:

1. Read Set Up and Verify URP in Unity 6.
2. If imported materials look broken, go to Convert Built-In Materials to URP in Unity 6.
3. If URP materials were imported into a VRChat project, use Fix URP Materials Imported into a VRChat Project.
4. Once the project is stable, review Optimize URP Performance: 7 Measurable Changes.

Quick Diagnosis

Situation	Best next step
Materials are pink or missing	Confirm the active render pipeline, then convert or replace incompatible shaders.
Only some imported assets look wrong	Convert those materials selectively before changing global project settings.
Post-processing or outlines stopped working	Check the Renderer Data and URP renderer features.
Performance became worse after enabling URP	Review render scale, shadows, HDR, post-processing, renderer features, and material complexity.
The desktop build works but mobile does not	Build a simpler platform-specific material and effect path.

Common URP problems creators run into

Pink or broken materials

This usually means the assigned shader does not match the render pipeline the project is using. Confirm the active URP Asset before converting materials in bulk.

Imported assets look wrong

Many imported packages were authored for Built-in Render Pipeline or for a different custom shader stack. Convert a copy or a small material set first.

Post-processing or special effects stop working

Renderer features and custom shader logic often need URP-specific setup instead of direct reuse from older tutorials. Check the Renderer Data assigned to the active URP Asset.

Performance drops after switching pipelines

URP can help performance, but only if project settings, renderer features, materials, lighting, and scene complexity are tuned intentionally.

URP Migration Order

URP changes are safest when you:

1. confirm the project pipeline before troubleshooting visuals
2. back up the project before conversion work
3. test one scene or material set at a time
4. verify the result inside the real scene, not only in isolation
5. optimize after the migration is stable

That order prevents a lot of blind trial-and-error.

Before You Convert A Project

Before migrating or repairing a URP project, check:

• the Unity version the project targets
• whether every required package supports the target Unity version
• the active URP Asset in Project Settings
• the active render pipeline asset for each Quality level
• whether imported assets depend on Built-in shaders
• whether the application targets desktop, mobile, or both
• whether you have a backup or source-control checkpoint

That short review can save hours of guessing later.

References

• Unity Documentation

• Unity Manual

• Unity URP Manual

• Unity's URP documentation describes the URP Asset as the place where Universal Render Pipeline settings are configured for a project.

• Unity's URP reference separates project-level URP Asset settings from Renderer Data and renderer features.

• Do not apply URP migration steps to VRChat projects; VRChat requires its Creator Companion project setup and the Built-in Render Pipeline.

Key follow-up routes

Setup and migration

• Set Up and Verify URP in Unity 6
• Convert Built-In Materials to URP in Unity 6
• Fix URP Materials Imported into a VRChat Project

Optimization and advanced workflow

• Optimize URP Performance: 7 Measurable Changes
• Upgrade a Custom Built-In Shader to URP
• Use URP Renderer Features in Unity 6

Broader Unity support

• Unity3D Version Differences
• Optimizing Unity3D Worlds for Performance
• Lighting

Confirm the Target Render Pipeline

Before you try to repair materials or performance, answer this first:

Is the project already meant to be URP, or are you trying to force URP onto a project that was built around another pipeline?

That one decision usually tells you whether you should migrate, convert selectively, or stop and reassess the project setup.

Help! My material or shader looks wrong after changing it.

Check the assigned shader, texture slots, render pipeline, and platform target. Revert to the backed-up material if the conversion changed more than expected.

Help! Will this work on mobile hardware?

Use shaders appropriate for the target hardware and test a platform build. A successful desktop Editor test does not validate mobile performance or compatibility.

Related Navigation

• Unity3D Documentation
• Unity Troubleshooting
• VRChat Documentation