What causes tile seams from linear filtering in WebGL?

The atlas texture uses gl.LINEAR filtering with no gutter, so sampling near a tile's UV edge blends in the neighboring tile, producing seams at non-integer zoom.

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 Tile Seams in a WebGL Tilemap From Linear Texture Filtering

Quick answer: Set the texture to gl.NEAREST for pixel art (or add padding and inset UVs by half a texel), and disable mipmaps so distant tiles do not blend across regions.

Your WebGL tilemap (PixiJS, Phaser, or raw) shows flickering lines between tiles when the camera zooms or scrolls. Linear filtering is sampling past each tile's UV rect.

How to fix it

1. Use nearest filtering for pixel art

Set gl.texParameteri(gl.TEXTURE_2D, gl.TEXTURE_MIN_FILTER, gl.NEAREST) and the mag filter to NEAREST so texels are read exactly without cross-tile blending.

2. Pad the atlas and inset UVs

If you need linear filtering, add a duplicated-edge gutter between tiles and inset each tile's UVs by half a texel so the sampler stays inside the region.

3. Turn off mipmaps

Do not generate mipmaps for the tile atlas; lower mips average across tile boundaries and create seams at smaller zoom levels.

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