Fix: Unity Application.targetFrameRate Ignored in Build

Here is how to fix Unity Application.targetFrameRate being ignored in builds. You set it to 30 to save mobile battery; the player runs at 60. You set it to 144 for high-refresh monitors; the player caps at 60. The cause is the interaction with VSync — if VSync is on, your targetFrameRate request is silently overruled.

The Symptom

In editor, targetFrameRate works as expected. In build, the actual FPS does not match the value you set. Sometimes higher (uncapped), sometimes lower (capped to refresh rate), depending on platform and VSync settings.

What Causes This

VSync precedence. When QualitySettings.vSyncCount is greater than 0, Unity ignores targetFrameRate and presents at the display refresh rate divided by vSyncCount.

Platform-default behavior. Mobile defaults vSyncCount to 0; desktop usually defaults to 1. The same code produces different behavior across platforms.

Display refresh ceiling. targetFrameRate cannot exceed the display refresh rate when vsync is on, and may not exceed it even with vsync off depending on driver settings.

Wrong magic value. targetFrameRate = 0 means “use platform default”, not unlimited. -1 means “run as fast as possible”.

The Fix

Step 1: Disable VSync before setting targetFrameRate.

using UnityEngine;

public class FrameRateBootstrap : MonoBehaviour
{
    [SerializeField] private int targetFps = 60;

    void Awake()
    {
        QualitySettings.vSyncCount = 0;          // disable vsync
        Application.targetFrameRate = targetFps;
    }
}

Place this on a bootstrap object that runs first. The order matters: vSyncCount must change before targetFrameRate to take effect cleanly.

Step 2: Use vSync for tear-free if you do not need a custom cap.

QualitySettings.vSyncCount = 1;       // vsync at every refresh
Application.targetFrameRate = -1;     // ignored when vsync is on

vSync provides smooth output without configuration but you cannot pick custom rates.

Step 3: For mobile, set per-device.

int displayHz = (int)Screen.currentResolution.refreshRateRatio.value;
int chosenFps = Mathf.Min(60, displayHz);  // cap at 60 even on 120Hz

QualitySettings.vSyncCount = 0;
Application.targetFrameRate = chosenFps;

For battery savings, drop to 30 or 45 in low-power gameplay states. Bump back to 60 in combat.

Step 4: Verify the actual cap with a frame counter.

[SerializeField] private Text fpsLabel;

void Update()
{
    if (Time.frameCount % 10 == 0)
        fpsLabel.text = $"FPS: {1f / Time.unscaledDeltaTime:F0}";
}

Step 5: Confirm in build, not just editor. Editor frame rate is influenced by editor focus, scene rendering, and play mode pause. Always validate the cap in a real build on the target platform.

Per-Platform Notes

Android: Some manufacturers (Samsung, Xiaomi) have system-level FPS caps in battery saver. targetFrameRate cannot bypass those.

iOS: 120Hz support requires Info.plist CADisableMinimumFrameDurationOnPhone = true. Without it, iPhones cap to 60 even on 120Hz hardware.

Steam Deck: SteamOS exposes its own per-game FPS limit in the overlay. Players can override your in-game cap.

Understanding the issue

Build pipelines transform development assets into shipping packages. Each transformation can introduce subtle changes: compression, stripping, format conversion, code generation. A bug that only appears in the cooked build is usually one of these transformations doing something the author didn't expect.

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

For shipping games, the safest verification is a staged rollout. Apply the fix to 1% of players for 24 hours; watch the affected metric; expand if green. Skipping the staged rollout means the verification is the entire player base, which is too high a stakes for most fixes.

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

Related bug classes often share the same root cause. If you find yourself fixing this issue, look for cousins: similar symptoms in adjacent systems, the same data flow but a different value, or the same fix pattern in another module. The catalog of 'we've seen this before' becomes valuable institutional knowledge.

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

The diagnostic tools available depend on your engine and platform. Use the engine's native profilers and debug overlays before reaching for external tools. The native tools have context that external tools lack - they know which subsystem owns the code, which assets are loaded, and what state the engine is in.

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

Edge cases for this class of issue often involve specific timing: the first frame after a state change, the last frame before a transition, frames where multiple subsystems update simultaneously. Reproducing these reliably is part of what makes the bug class hard to test.

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

When this bug class affects multiple teams (often the case for cross-system issues), early communication prevents duplicate work. The team that owns the symptom may not own the cause. A 15-minute conversation at the start of triage often saves hours of independent investigation.

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.

“VSync wins over targetFrameRate. Disable vsync first if you want a custom cap. -1 for unlimited, 0 for platform default, positive for explicit.”

Related Issues

For Unity vsync issues, see VSync Not Working in Build. For Pygame CPU usage, see Pygame Clock.tick CPU.

vSyncCount = 0. Then targetFrameRate. Verify in real build. The cap holds.