Unity URP Settings for Mobile That Actually Matter

The Unity URP mobile settings that matter most are render scale, HDR, MSAA, shadow distance and cascades, additional lights, depth and opaque textures, and post-processing. Those control how many pixels you shade and how many passes you run. Set them per quality tier with separate URP Assets, and test on your weakest target phone, not in the editor.

Where these settings live

Unity spreads URP settings across a few places. Knowing which is which saves a lot of clicking.

• URP Asset: quality, lighting and shadow settings. Select it in the Project window and use the Inspector.
• Renderer Data: rendering path, depth priming, and renderer features. Linked from the URP Asset.
• Project Settings > Quality: which URP Asset each quality level uses.
• Camera: per-camera post-processing, anti-aliasing and depth or opaque texture overrides.

Make one URP Asset per tier, for example Low, Medium and High, and assign each in Project Settings > Quality. Then you can switch tiers at runtime.

The big ones, in order of impact

These are the settings that most often move frame rate on mobile. Exact menu labels shift slightly between Unity versions, so look for the nearest match.

Treat the starting points as defaults to test from, not rules. Your art style decides the final values.

Render scale is the easiest win

Modern phones have very high screen resolutions. Shading every pixel at native resolution is often wasted on a small screen. Dropping render scale a little is the single cheapest frame rate gain in URP.

You can also change it at runtime, for example to drop resolution when the device gets hot.

using UnityEngine.Rendering;
using UnityEngine.Rendering.Universal;
var urp = (UniversalRenderPipelineAsset)GraphicsSettings.currentRenderPipeline;
urp.renderScale = 0.8f;

Keep UI on a Screen Space Overlay canvas so text stays crisp while the 3D scene renders at lower scale.

Shadows: the quiet cost

Shadows are often the most expensive feature in a mobile URP scene. Each shadow-casting light renders the scene again from its own view.

Practical steps that usually help:

1. Set a short Max Distance so only nearby objects cast shadows.
2. Use one cascade on mobile.
3. Turn off Cast Shadows on small props and background meshes in their Mesh Renderer.
4. Use lower Shadow Resolution on low tiers.
5. For static scenes, bake lighting and use a blob shadow under moving characters.

A simple blob shadow is a quad with a soft circle texture. It costs almost nothing and often looks better than a jagged real-time shadow on a small screen.

Post-processing: pick one or two effects

Post-processing runs full-screen passes, so each effect touches every pixel. On mobile, choose effects that do the most for your look.

• Colour grading with a baked lookup is usually affordable.
• Bloom is moderate. Lower its quality settings and keep HDR in mind.
• Depth of field, motion blur and screen space ambient occlusion are expensive. Skip them on low tiers.

Turn post-processing off on the camera entirely for the lowest tier, and check the Post-processing toggle on the Renderer Data. A disabled effect in the Volume still costs something if the pass is on.

Renderer and build settings worth a look

A few less obvious settings round things off.

• Rendering Path: Forward is a safe default for most mobile games. Forward+ helps scenes with many lights, so profile both.
• SRP Batcher: keep it on. It reduces the CPU cost of draw calls for compatible shaders.
• Shader stripping: in the URP global settings, strip unused post-processing and debug variants to cut build size and load time.
• Target frame rate: set Application.targetFrameRate deliberately. A steady 30 often feels better and drains less battery than a jumpy 60.

Test on the right device

The editor tells you very little about phone performance. Build a development build to your weakest supported Android phone and profile with the Unity Profiler and Frame Debugger attached.

Change one setting at a time and note the result. Our guide to debugging frame drops on Android in twenty minutes walks through that loop, and 12 fixes for low-end Android covers what to try outside URP.

Profile on your worst phone first. If it runs well there, the rest will look after themselves.

What we would do

We would set up three URP Assets on day one, Low, Medium and High, with render scale, shadows and post as the main differences. We would pick the tier at startup from a simple device check and let players override it in settings.

Then we would profile on a budget Android every week, not just before launch. URP settings are easy to change early and painful to change after the art is locked.

The short version

• Render scale, HDR, MSAA, shadows, extra lights and post cover most of the cost.
• Use one URP Asset per quality tier and assign them in Project Settings > Quality.
• Lower render scale first, it is the cheapest win.
• Keep shadows short, single-cascade and off on small props.
• Profile on your weakest target phone, one change at a time.

If your URP project is struggling on low-end phones and you want a hand, send us a profile capture.

Related reading: Shader Basics for Devs Who Are Not Technical Artists, Unity UI That Does Not Tank Your Frame Rate