Why does TextMeshPro break Unity Canvas batching?

TMP uses its own font atlas material; UGUI Image uses the sprite atlas. Two materials means at least two draw calls, and a TMP label sandwiched between Images forces both Image groups to draw separately.

How do I improve Canvas batching with TMP?

Group all TMP labels in sibling order so they render together. Use a single sprite atlas across UI Images. Use one TMP font asset across the canvas to avoid sub-mesh material splits. Order: all Images, then all TMP labels (or vice versa), but not interleaved.

Does using TMP_SubMeshUI add draw calls?

Yes. Each fallback font (e.g., emoji sprite, secondary script) creates a TMP_SubMeshUI with its own material, adding a draw call per submesh. Minimize fallbacks for batchable text.

Fix: Unity TextMeshPro Breaking Canvas Batching

Quick answer: TMP uses its own font atlas material; UGUI Image uses the sprite atlas. Group all Images then all TMP labels (in sibling order) to minimize material switches. One sprite atlas, one font asset across the canvas where possible.

Here is how to fix Unity UI draw calls ballooning when you add TextMeshPro labels. Each material switch breaks batching; TMP’s font material differs from sprite Atlas, so interleaving inflates draw count.

The Symptom

Stats panel shows 50 draw calls for a UI with 10 buttons (each with an Image and a TMP label). Without TMP, all 10 buttons batch to 1 draw call.

What Causes This

Material switches. Image material A → TMP material B → Image material A breaks batching at each transition.

TMP submeshes. Fallback fonts add submeshes, each with its own material.

Different sprite atlases. Multiple sprite atlases multiply Image draw calls.

The Fix

Step 1: Group siblings by material type.

// Before: bad order
ButtonGroup
  Button1: Image, TMPLabel
  Button2: Image, TMPLabel
  ...

// After: separate group
ButtonGroup
  ImagesContainer
    Button1Image
    Button2Image
    ...
  LabelsContainer
    Button1Label (TMP)
    Button2Label (TMP)
    ...

The change is structural; siblings render in tree order. Grouping by material reduces material switches.

Step 2: Use one sprite atlas. Pack all UI sprites into a single SpriteAtlas asset. Inspector confirms atlasing via Sprite Atlas Packing window.

Step 3: One font asset. Use one TMP font asset for all standard text. Different fonts = different materials.

Step 4: Inspect with Frame Debugger. Window → Analysis → Frame Debugger. Look at the Canvas batches; count material switches. Fewer = better.

Step 5: Disable Cull Transparent Mesh and other off-by-default optimizations cautiously. They can interact with TMP’s mesh generation.

Performance Impact

Going from 50 draw calls to 8 by grouping is common. On mobile with 60 FPS targets, every draw call counts.

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

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

There's almost always a less obvious case where the same problem applies. The reported case is the one a player hit; the related cases hide because they're rarer or affect fewer players. After fixing the reported case, search the codebase for the pattern - one fix often unlocks several.

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

For shipping titles with a long support window, watch for this issue resurfacing after dependency updates. Engine upgrades, driver updates, OS releases - each one can resurface a bug class you thought you'd fixed because the underlying behavior changed slightly. Regression tests catch the obvious ones; player reports catch the rest.

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

The tooling around this bug class matters as much as the fix itself. Good logging, accessible profilers, and clear error messages turn 30-minute investigations into 5-minute ones. If your project doesn't have visibility into this code path, the first fix should add the visibility - the second fix uses it.

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

Boundary conditions deserve specific testing attention. What happens when the input is zero, maximum, negative, or NaN? What happens at the start of a session vs hours in? What happens at the boundary between two systems handling the same data? These are where bugs hide and where regression tests are most valuable.

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.

“Group siblings by material. One sprite atlas. One font asset. Batching returns.”

Related Issues

For TMP emoji, see TMP Emoji. For Canvas culling, see Canvas Cull Mask.

Group siblings by material. Atlas everywhere. One font. Batching restored.