What causes a Construct 3 game canvas looking blurry on retina phones?

The canvas is rendered at CSS pixel size and stretched to the device's higher physical pixel density, so everything is upscaled and soft on retina displays.

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 a Construct 3 Game Canvas Looking Blurry on Retina Phones

Quick answer: Use a fullscreen scaling mode that respects device pixel ratio (High quality fullscreen) so the canvas backing resolution matches the physical pixels.

Your Construct 3 game looks crisp in the editor and on a desktop but fuzzy on a modern phone. The canvas is being drawn at logical resolution and scaled up to the dense screen. Enabling high-quality fullscreen restores sharpness.

How to fix it

1. Set fullscreen quality to high

In Project Properties set Fullscreen quality to High so the runtime allocates the canvas at the full device-pixel-ratio resolution instead of CSS pixels.

2. Avoid CSS upscaling

Do not force a fixed canvas size in HTML that the browser then stretches; let the runtime size the backing store to the physical pixels of the display.

3. Check sampling for pixel art

If your game is pixel art, pair high-quality fullscreen with point sampling so the extra resolution stays crisp instead of bilinear-smeared.

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 Construct 3 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.

Most of the time the fix is small. Seeing the failure clearly is the part that actually costs you.