What causes a 9-slice sprite border stretching in Unity?

The SpriteRenderer Draw Mode is set to Sliced (which stretches the edges) or the sprite borders and Pixels Per Unit Multiplier are wrong, so edge texels smear instead of repeating.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix Blurry or Stretched Borders on a 9-Slice Sprite in Unity

Quick answer: Set Draw Mode to Tiled with a Tiled mode of Continuous, define the border in the Sprite Editor, and adjust Pixels Per Unit Multiplier so the border art repeats at native resolution.

A panel or platform built from a 9-slice sprite shows a stretched, blurry edge instead of a repeating texture. The Draw Mode and border setup control whether edges stretch or tile.

How to fix it

1. Set the border in the Sprite Editor

Open the Sprite Editor and drag the green border guides to mark the non-stretching corners and edges. Without borders the whole sprite scales and blurs.

2. Choose Tiled draw mode for repeating edges

On the SpriteRenderer set Draw Mode to Tiled so edges repeat instead of stretch. Use Sliced only when stretched edges are acceptable.

3. Fix the tiling scale

Adjust Pixels Per Unit Multiplier so the border tiles at its authored pixel size. A wrong multiplier makes the repeated edge oversized and soft.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Unity error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

Reproduce it once with full context and the fix writes itself. The hunt is the expensive part.