The short answer
If your game still uses the Built-in Render Pipeline, you do not have to panic, but you do need a plan. Unity 6.5, released in June 2026, officially deprecated Built-in. It will keep receiving fixes until at least Unity 6.7 LTS, which Unity expects at the end of 2026, and is then supported for two more years before it is removed. Unity has also said development will concentrate on the Universal Render Pipeline (URP), with HDRP in maintenance mode. For most mobile, PC and XR games, the destination is URP, and the best time to move is between releases, not the month before a launch.
What actually changed in 2026
- Built-in Render Pipeline deprecated (Unity 6.5). No new features, fixes until at least 6.7 LTS, then a two-year support window, then removal.
- HDRP in maintenance mode. Unity announced in February 2026 that rendering development will focus on URP. HDRP keeps working but stops gaining features.
- Conversion tools. Unity 6.5 added a command-line tool for converting Built-in assets to URP, on top of the existing Render Pipeline Converter in the editor.
- Higher Android floor. Unity raised the minimum Android API level to 26 (Android 8.0) in the 6.5 cycle.
- Releases moved fast. 6.4 arrived in March 2026 with the Entity Component System and Project Auditor built into the editor, 6.5 in June, and 6.6 builds were shipping by October. Unity's forum now tells 6.5 users to move to 6.6 or later.
- Havok no longer bundled. From Unity 6.3, Havok Physics is no longer included in Pro, Enterprise or Industry plans. Projects that rely on it need a separate arrangement with Microsoft's Havok team.
Who needs to act, and how soon
| Your project | Risk | What we would do |
|---|---|---|
| Live game on Unity 2021 or 2022 LTS with Built-in | High over 12–24 months | Plan a Unity 6 LTS upgrade and a URP move as one project, between content updates |
| Unity 6.0 LTS with Built-in | Medium | Stay on 6.0 LTS for now; convert to URP before you jump to 6.7 LTS |
| New project starting today | None if you choose well | Start on URP; do not start anything new on Built-in or HDRP |
| HDRP PC or console game | Low short term | Keep shipping; no new HDRP features are coming, so weigh URP for the next title |
| Already on URP | Low | Upgrade engine versions on a schedule and test on your lowest target device |
A rule of thumb: never combine an engine upgrade, a render pipeline change and a big content update in one release. Each of them can break builds on its own.
What breaks when you move from Built-in to URP
Standard materials convert automatically. The expensive parts are the things Unity cannot convert for you:
- Custom shaders. URP has no surface shaders. Hand-written Built-in shaders must be rebuilt in Shader Graph or rewritten as URP HLSL. On stylised games this is usually the biggest line item.
- Post-processing. The old Post-Processing Stack v2 is replaced by URP's Volume system. Bloom, colour grading and vignette look slightly different and need re-tuning by an artist.
- Camera code.
OnRenderImage,GrabPassand command buffers attached to cameras do not work in URP. Effects built on them move to Renderer Features. - Lighting. Lightmaps must be rebaked, light counts per object are limited differently, and shadows need new settings to look and perform the same.
- Projectors and old effects. Projectors become Decal Projectors; some legacy image effects have no direct equivalent.
- Asset Store packages. Every third-party shader, water, sky or VFX package needs a URP version. Some were abandoned and have to be replaced.
A safe upgrade plan in seven steps
- Audit. Run Project Auditor and list every custom shader, camera effect, render callback and third-party package. This list is your real estimate.
- Branch. Do the work on a separate branch in version control with a frozen content scope. Unity Version Control no longer charges per seat on its public cloud, so there is no excuse to skip it.
- Upgrade the engine first. Move to the target Unity 6 LTS on Built-in, fix compile errors and deprecated APIs, and ship nothing until the game plays exactly as before.
- Convert the pipeline. Install URP, run the Render Pipeline Converter, then rebuild custom shaders and camera effects one by one.
- Re-light and re-grade. Rebake lighting and have an artist compare screenshots side by side, scene by scene.
- Profile on real devices. URP is usually faster on mobile, but only after tuning. Measure frame time on your weakest supported phone or headset, not on a development PC.
- Regression test and stage the release. Full QA pass, then a staged rollout so a rendering bug reaches 5% of players, not all of them.
How long it takes
| Project type | Typical scope of a Built-in to URP move |
|---|---|
| Small 2D or simple 3D mobile game, standard materials | About 1–3 weeks including testing |
| Mid-size 3D game with custom shaders and post-processing | About 4–8 weeks |
| Large game, many custom shaders, several platforms or XR | Two months or more, planned as its own milestone |
These are rough guides, not quotes. The audit in step one turns them into a real number, and it is the step most teams skip.
When not to upgrade yet
If a game is near the end of its life, earns little and will not get major updates, staying on its current LTS until Built-in support ends is a legitimate choice. The same goes for a game shipping in the next few weeks: launch first, upgrade after. What is not a good choice is starting a brand new project on Built-in in 2026.
Where we fit
We upgrade and convert Unity projects for studios that would rather keep their own team on new content. Our senior engineers work inside your repository, start with the audit, and give you a fixed price before the pipeline work begins. See co-development and project rescue and Unity game development, or read what Unity costs in 2026 if licensing is part of the decision.
Sources: CG Channel on Unity 6.5 · Unity: planned breaking changes in 6.5 · Unity plans and pricing changes. Checked October 12, 2026.
Related: Co-development and rescue · Unity game development · Unity vs Unreal for mobile
Quick answers ❓
Is the Built-in Render Pipeline being removed from Unity?
Yes, eventually. Unity 6.5 deprecated it in June 2026. It keeps receiving fixes until at least Unity 6.7 LTS, expected at the end of 2026, is supported for two more years after that, and will then be removed.
Should I use URP or HDRP for a new Unity project?
For almost every new project, URP. Unity has said rendering development will concentrate on URP and HDRP is in maintenance mode, so it still works but will not gain new features.
Will my game look different after converting to URP?
Slightly, unless an artist re-tunes it. Standard materials convert automatically, but post-processing, lighting and shadows behave differently, and custom shaders must be rebuilt, so plan time for side-by-side visual comparison.
How long does a Built-in to URP conversion take?
Roughly one to three weeks for a small mobile game with standard materials, four to eight weeks for a mid-size 3D game with custom shaders, and two months or more for large multi-platform projects. An audit of shaders, camera effects and packages gives the real figure.
Can I upgrade Unity and switch to URP at the same time?
You can, but it is safer to upgrade the engine first, confirm the game plays exactly as before, and only then convert the render pipeline, so each problem has one cause.
Related guides
Unity pricing in 2026 explained → Unity vs Godot for mobile games →Need your Unity project upgraded? 🔷
Send us the project details and you'll get an audit plan and a fixed price for the upgrade within 48 hours, with your own team free to keep shipping content.