Every Unity project forces the same early decision: HDRP or URP. Get it wrong and you're either shipping a mobile game that runs at 20 fps, or spending months porting a PC title to a pipeline it was never designed for. This guide cuts through the marketing and gives you a clear framework for making the call — with concrete asset and project criteria.
What each pipeline actually does
Unity ships two scriptable render pipelines for modern projects. Universal Render Pipeline (URP) replaces the old Built-in pipeline and targets the widest hardware range: mobile, WebGL, consoles, and mid-range PC. High Definition Render Pipeline (HDRP) is built for high-end PC and current-gen consoles where you can afford the GPU budget for physically correct lighting, volumetric fog, ray tracing, and sub-surface scattering.
Both are built on the Scriptable Render Pipeline (SRP) foundation, but they use different shader libraries, lighting models, and asset requirements. A material authored for HDRP will not work in URP without conversion, and vice versa — there is no free migration path.
HDRP's key features over URP:
- Volumetric lighting and fog — god rays, atmospheric scattering
- Screen-space global illumination (SSGI) and Lumen-style GI via Probe Volumes
- Ray-traced shadows, reflections, and ambient occlusion (DXR path)
- Sub-surface scattering for skin, wax, and translucent materials
- Exposure and physically-based sky for cinematic realism
URP's advantages:
- Runs on OpenGL ES 3.0+ (Android back to 2016)
- Single-pass stereo rendering for VR
- Faster iteration with simpler Shader Graph nodes
- Smaller build sizes and lower memory pressure
- Broader asset compatibility out of the box
Choosing based on your asset library and target platform
The render pipeline choice is primarily driven by target platform, then by asset complexity.
```
Target Platform Recommended Pipeline
─────────────────────────────────────────────
Mobile / WebGL URP (mandatory)
Meta Quest / PSVR2 URP (single-pass stereo)
Nintendo Switch URP (power budget)
PS5 / Xbox Series X Either (HDRP if visual fidelity matters)
High-end PC (AAA) HDRP
Indie PC (performance) URP
```
For 3D game assets from the BitSoul marketplace, the key question is: do your GLB models need HDRP-exclusive material features? If your assets rely on standard PBR (albedo, metallic, roughness, normal, AO), they will look excellent in both pipelines. If you need coat layers, fabric sheen, eye caustics, or SSS, HDRP is required.
| Feature | URP | HDRP |
|---|---|---|
| PBR (Metallic/Roughness) | ✓ | ✓ |
| Decals | ✓ (limited) | ✓ (full) |
| Volumetric fog | Limited | ✓ |
| Ray-traced GI | ✗ | ✓ |
| Sub-surface scattering | ✗ | ✓ |
| Screen-space reflections | ✓ | ✓ |
| Shader Graph | ✓ | ✓ |
| VR single-pass | ✓ | Limited |
| Mobile support | ✓ | ✗ |
Importing free GLB assets into HDRP and URP
When importing GLB files into Unity (2022 LTS+ supports native GLB import via the GLTF importer), the process differs slightly between pipelines.
In URP:
1. Import the GLB — Unity auto-generates URP/Lit materials
2. Check the normal map type in the Texture Import settings (`Normal map` not `Default`)
3. Verify the smoothness channel is mapped from the roughness texture (invert if needed)
4. Enable GPU instancing on shared materials for prop-heavy scenes
In HDRP:
1. Import the GLB — Unity generates HDRP/Lit materials
2. Open each material and set the correct Surface Type (Opaque or Transparent)
3. For metallic assets, enable Geometric Specular AA to reduce aliasing at distance
4. Check the Detail Map slot for micro-surface variation on large meshes
5. Configure Probe Volumes or Reflection Probes for correct indirect lighting
```csharp
// Force HDRP material upgrade via script for batch imports
using UnityEditor;
using UnityEngine.Rendering.HighDefinition;
public class HDRPMaterialUpgrader : EditorWindow
{
[MenuItem("Tools/Upgrade Materials to HDRP")]
static void UpgradeMaterials()
{
var materials = AssetDatabase.FindAssets("t:Material");
foreach (var guid in materials)
{
var path = AssetDatabase.GUIDToAssetPath(guid);
// Trigger HDRP upgrade wizard
AssetDatabase.ImportAsset(path, ImportAssetOptions.ForceUpdate);
}
}
}
```
Performance budgets and when to switch pipelines
A common mistake is starting with HDRP for aesthetics, then discovering the target hardware can't hit 60 fps. Establish these limits before pipeline selection:
- Mobile (URP target): 16–20 ms frame budget, max 150 draw calls, 100k–200k triangles
- Console/mid PC (URP viable): 8–11 ms, 500 draw calls, 500k triangles
- High-end PC (HDRP target): 6–8 ms with DLSS/FSR, unlimited draw calls with batching
If you're building a scene with hundreds of free 3D props from BitSoul, URP with GPU instancing will outperform HDRP at equivalent draw call counts. HDRP's tile-based deferred renderer pays off only when you have complex multi-light scenarios — a dungeon lit by 40 dynamic point lights, for example.
The honest verdict
Pick URP if: your game targets mobile, you're an indie team without a dedicated technical artist, your assets are PBR-standard, or you want faster iteration. URP in Unity 6 has closed most of the visual gap with HDRP for non-cinematic projects.
Pick HDRP if: you're targeting high-end PC or current-gen console exclusively, your art direction demands volumetric atmospheres or physically-correct skin rendering, and you have the shader authoring expertise to configure it correctly.
Browse the full library of free, game-ready GLB models optimized for both pipelines at the BitSoul 3D marketplace.
---
*This post is part of the Ultimate Guide to Free 3D Game Assets — BitSoul's complete reference for formats, texturing, rigging, optimization, and engine integration.*