What causes blurry pixel art in Godot?

Linear texture filtering is smoothing your sprites, and a non-integer stretch is sampling pixels between grid positions — both blur crisp art.

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 Pixel Art in Godot

Quick answer: Set texture filtering to Nearest on the textures or project-wide, use the viewport stretch mode with integer scaling (or pixel snapping), and keep the camera and positions on whole pixels.

Pixel art that should be sharp but looks fuzzy is being filtered and scaled like a photo. Godot defaults to smooth filtering, which is wrong for pixels. Here is how to make it crisp.

How to fix it

1. Set filtering to Nearest

In Project Settings, set the default texture filter to Nearest, or set it per-texture in the import dock. Linear filtering blends adjacent texels, which softens hard pixel edges.

2. Use integer scaling and the right stretch mode

Set the window stretch mode to canvas_items or viewport and enable integer scaling so the image scales by whole multiples. Fractional scaling samples between pixels and smears them.

3. Snap positions and the camera to whole pixels

Sub-pixel positions cause shimmering. Enable pixel snap (snap 2D transforms to pixel) and keep the camera on integer coordinates so sprites land on the grid.

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 Godot 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.

Ship the fix, watch the signature disappear from the next build. That's how you know it's really gone.