Quick answer: Verify the variant’s Scale factor matches your intent (1.0 = full, 0.5 = half). Check Include in Build on the master atlas. Use SpriteAtlasManager.atlasRequested to confirm which atlas variant loads at runtime.

Here is how to fix Unity SpriteAtlas variant wrong resolution. You create a master atlas for your HD sprites and a 0.5x variant for mobile. On mobile, sprites look correct at half-res. On desktop, sprites look blurry — the variant loaded instead of the master. Or vice versa: mobile loads full-res and runs out of memory. Atlas variant selection is implicit and easy to misconfigure.

The Symptom

Sprites from a SpriteAtlas render at the wrong resolution — blurry when full-res expected, or full-res when low-res intended. Sprites may also appear pink (missing atlas) or as their un-atlased originals (atlas not included in build).

What Causes This

Wrong variant active. SpriteAtlas variants are registered via callbacks. If your code or Addressables loads the wrong variant tag, the wrong resolution atlas activates. Unity does not auto-select based on device capabilities.

Include in Build unchecked. The master atlas must have Include in Build checked. Without it, the atlas is not packed and sprites fall back to individual textures — which may have different import settings.

Scale factor confusion. A variant with Scale = 0.5 produces textures at half dimensions. If you expected full resolution, check the variant settings. Scale = 1.0 on a variant is essentially a copy of the master (rarely useful).

Texture compression per platform. The variant inherits compression from the master but can override per platform. If the desktop override is ASTC and your desktop GPU does not support it, sprites decompress wrong.

The Fix

Step 1: Verify master atlas settings. Select the SpriteAtlas asset. Confirm:

Step 2: Verify variant settings. Select the variant atlas. Confirm:

Step 3: Control variant loading via callback.

using UnityEngine;
using UnityEngine.U2D;

public class AtlasSelector
{
    [RuntimeInitializeOnLoadMethod(RuntimeInitializeLoadType.BeforeSceneLoad)]
    static void Init()
    {
        SpriteAtlasManager.atlasRequested += OnAtlasRequested;
    }

    static void OnAtlasRequested(string tag, System.Action<SpriteAtlas> callback)
    {
        string path = IsMobile()
            ? $"Atlases/{tag}_mobile"
            : $"Atlases/{tag}";

        SpriteAtlas atlas = Resources.Load<SpriteAtlas>(path);
        callback(atlas);
    }

    static bool IsMobile() =>
        Application.isMobilePlatform;
}

The callback fires when Unity needs an atlas. You decide which variant to load based on platform, quality settings, or device tier.

Step 4: Log which atlas loaded. After the callback fires, log the atlas name to confirm the correct one was selected during testing:

Debug.Log($"Atlas loaded: {atlas.name}, tag: {atlas.tag}, " +
    $"spriteCount: {atlas.spriteCount}");

If the wrong atlas loads, the path logic in your callback is wrong. Fix the path and rebuild.

Addressables Integration

When using Addressables with SpriteAtlas, mark the atlas as addressable and load it via the Addressables API. Variant selection happens through Addressable labels or profile variables rather than the SpriteAtlasManager callback. Both approaches work; do not mix them.

Packing Preview

Select the atlas and click “Pack Preview” in the Inspector to see the generated texture page. Verify resolution matches your expectations. If the preview shows a 512x512 page when you expected 2048x2048, the Max Texture Size setting is capping it.

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Unity Engine, the underlying behavior is shaped by how the engine layers its abstractions - the public API you call, the runtime systems that respond, and the platform-specific implementations underneath. A bug at any layer can produce symptoms that look like they originate at a different layer. Triaging effectively means recognizing which layer the symptom belongs to, even when the gameplay code is what's visible.

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

Bugs of this class are particularly easy to ship past internal QA because they often depend on specific runtime conditions - hardware combinations, network states, or asset configurations that QA didn't reproduce. Players hit them in the wild, file reports that are hard to repro, and the bug accumulates negative reviews while engineering tries to recreate the failure mode.

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

After applying the fix, the verification step has three parts: confirm the original repro is resolved, confirm no obvious regressions in adjacent functionality, and (for shipping titles) deploy to a small player cohort first and watch the crash and report rates. Each step catches something the others miss.

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

In shipping builds, this issue may interact with other production-only behavior. Stripping, encryption, asset bundling, and platform-specific code paths can each modify the symptoms. When players report a related issue, capture build SHA, platform, and any feature flags - those three fields cover most of the production-only variations.

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

Performance implications matter when this bug class scales with player count or asset count. A bug that fires once per session is annoying; a bug that fires once per frame compounds. After fixing, profile the affected code path under realistic load. The fix that's correct for one entity may be too slow for ten thousand.

Diagnostic approach

Diagnosing this class of bug benefits from a structured approach: confirm the symptom, isolate the variables, hypothesize the cause, and verify the hypothesis before writing fix code. Skipping the isolation step is the most common mistake; without it, fixes often address symptoms while the underlying cause continues to produce other variations.

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

Modern engine versions ship better tooling for this kind of issue than older versions. If you're on an older release, the diagnostic step may take significantly longer because the tools you'd want don't exist yet. Sometimes the right answer is upgrading rather than fighting through limited tooling.

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

Document the fix and its rationale in the commit message or attached engineering doc. Future engineers will encounter related issues; the rationale tells them whether your fix is reusable or specific to the case at hand. Without rationale, the fix gets reverted or copied incorrectly.

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.

“Atlas variants are a quality slider. Make sure you are holding the right end of the slider for each platform.”

Related Issues

For sprite rendering issues, see Sprite Renderer Not Visible. For wrong sprite loading from atlases, SpriteAtlas Wrong Sprite Loading covers related bugs.

Include in Build checked, Scale factor correct, callback selects variant. Three things.