✅ Updated Nov 2026
Affiliate Disclosure: As an Amazon Associate, we earn from qualifying purchases. Links marked "Check on Amazon" are affiliate links — learn more.

Buy a 4K monitor in the sizes most gamers choose, 27 to 32 inches, and unscaled native resolution makes desktop text tiny. So almost everyone runs a fractional scale factor instead, and the desktop looks perfect. Then a game launches and looks strangely soft, as if rendering below the resolution in its own settings menu.

This site has covered Wayland versus X11 and KDE versus GNOME in broader terms. This article is only about the scaling pipeline: what a Wayland compositor does to a game’s framebuffer at fractional scale factors, the three paths a game can take through it, what each costs, and which settings change the outcome.

As an Amazon Associate, we earn from qualifying purchases.

Quick answer

On a Wayland desktop at a fractional scale, a game stays sharp only if it renders at the panel’s full resolution. XWayland games usually render at the smaller logical size and are upscaled, which blurs them. Native Wayland builds render at full resolution, and Gamescope sidesteps the desktop entirely by scaling the game itself, once, on your terms.

How scaling actually works on Wayland

Wayland separates two sizes X11 mostly treated as one. The logical size is what applications lay out against. The physical size is the panel’s real pixel grid; the scale factor connects them. At a scale of 2 on a 3840 by 2160 panel, applications work in a logical 1920 by 1080 space, and every logical pixel maps to a clean two-by-two block of physical pixels. Integer scales divide evenly; nothing is resampled.

Fractional scales such as 1.25 or 1.5 break that mapping: a logical pixel no longer lands on a whole number of physical pixels, so something has to resample the image. Modern Wayland handles this through the fractional scale protocol, which tells a cooperating client its surface’s exact scale, so it renders a buffer at precisely the right dimensions. Supporting applications render at full physical resolution and lay out using the logical size.

Games mostly do not work that way: a game cares about a render resolution, not layout. Which of the three paths below it takes decides whether it stays sharp or falls into a scaling step it never asked for.

Path one: XWayland games and the blur

Most Windows games running through Proton are X11 clients, so on a Wayland session they run inside XWayland, the compatibility server presenting X11 windows to the compositor. Historically, XWayland clients render at the logical resolution. On a 4K panel scaled to 1.5, the game renders at 2560 by 1440, and the compositor upscales that finished frame to 3840 by 2160. That post-render bitmap stretch softens everything: text, HUD edges, fine detail. Selecting native resolution in the game often does not help, because XWayland’s exposed mode list may top out at the logical size.

The desktops differ in the control they offer. KDE Plasma 6 has a setting for legacy X11 applications: scaled by the system, the blurry path, or apply scaling themselves, where XWayland clients render at full physical resolution and manage their own size. That restores fullscreen sharpness, at the cost of odd window sizes in desktop applications. GNOME’s mutter compositor-scales XWayland output by default; recent versions carry an experimental native-resolution option, still opt-in. On wlroots compositors such as Sway, XWayland output is compositor-scaled traditionally.

So when a Proton game looks soft on Wayland and sharp on Windows at identical settings, suspect XWayland scaling first.

Path two: native Wayland rendering

The clean path is a game that talks Wayland directly. A native client supporting the fractional scale protocol renders its buffer at the surface’s true scale, so a fullscreen game renders at the panel’s physical resolution and the compositor passes the frame through untouched: no intermediate bitmap, no resample, no blur. Native Linux games on current SDL versions can take this path. The bigger development is Wine’s: its Wayland driver, experimental in the Wine 9 series, became the default display driver in Wine 10 on Wayland sessions, and recent Proton builds are shifting games onto it, with options to force it.

This path is not yet universal. Some games and launchers misbehave under the Wine Wayland driver, and a minority of titles need pinning back to XWayland. But the direction is documented and clear: as the driver matures, fewer games pass through XWayland at all. Until then, the third path is fully under your control today.

Path three: Gamescope, the scaling referee

Gamescope is Valve’s micro-compositor, built for the Steam Deck and usable nested in a desktop session. A game under Gamescope renders into a virtual display at the resolution you specify, and Gamescope composites that frame onto your real display at native resolution. The desktop’s scale factor is not part of the transaction, which is why Gamescope is the standard fix for XWayland blur: the game may still be an XWayland client inside it, but the only scaling is Gamescope’s own, performed once.

The controls that matter are the output resolution, which should match your panel, the game resolution, which decides rendering cost, and the scaler mode. Linear is the soft default, nearest keeps pixel-art games hard-edged, integer scaling multiplies retro resolutions by whole numbers for exact pixels, and the built-in FSR and NIS options upscale with a sharpening-aware filter rather than a plain stretch. A game rendered at 2560 by 1440 internally is upscaled once, predictably, whatever your desktop scale is.

The performance cost model

Fractional scaling itself is cheap; rendering resolution is what costs. The compositor’s resample is a single pass, minor next to rendering the frame. The real numbers are pixel counts: a 3840 by 2160 frame carries about 8.3 million pixels, roughly 2.25 times the 3.7 million of a 2560 by 1440 frame. A game rendering at native 4K does that much more shading work per frame, whatever the desktop scale says.

The expensive failure mode is accidental supersampling: a native game rendering at full panel resolution while you assumed the fractional scale had lowered its workload, or an in-game resolution scale stacked on a native mode. The opposite failure is an XWayland game capped at logical resolution: blurry, despite a frame rate suggesting better. Read every scaling complaint as a resolution question first: find the resolution the game truly renders at, then decide whether the fix is a different path, Gamescope, or an in-game upscaler such as DLSS or FSR.

Settings that matter, by desktop

On GNOME, display scale is set per monitor in Settings. XWayland applications follow mutter’s compositor scaling, so the game levers are the Wine Wayland driver and Gamescope. On KDE Plasma 6, display configuration offers a fine-grained per-monitor scale slider plus the legacy application scaling choice above; letting X11 applications apply scaling themselves is the most effective desktop-side change for fullscreen games. On Sway and other wlroots compositors, output scale is set per output in the configuration file, and Gamescope is the common answer. Per-monitor scales remain a genuine Wayland strength that X11 never matched.

Five high-DPI monitors and their scaling sweet spots

The monitors below sit in the density range where fractional scaling is a daily decision; each entry notes the scale posture its density leads to.

LG UltraGear 27GP950-B

The classic case: 4K in 27 inches, about 163 pixels per inch, usually run at a 1.5 scale.

  • Panel: 27-inch Nano IPS, 3840 x 2160
  • Refresh rate: 144 Hz, 160 Hz overclocked
  • Adaptive sync: FreeSync Premium Pro, G-Sync compatible
  • HDR: DisplayHDR 600

GIGABYTE M28U AE Arm Edition

The same density class at 28 inches, about 157 pixels per inch and the same 1.5 posture.

  • Panel: 28-inch Super Speed IPS, 3840 x 2160
  • Refresh rate: 144 Hz
  • Adaptive sync: FreeSync Premium Pro
  • Extras: KVM switch, monitor arm included

Dell G3223Q

At 32 inches, 4K density falls to about 140 pixels per inch; many owners settle at a 1.25 scale.

  • Panel: 32-inch Fast IPS, 3840 x 2160
  • Refresh rate: 144 Hz
  • Adaptive sync: FreeSync Premium Pro, G-Sync compatible
  • HDR: DisplayHDR 600

Samsung Odyssey Neo G8

A curved Mini LED panel at the same 32-inch 4K density, but at 240 Hz.

  • Panel: 32-inch VA, 1000R curve, Quantum Mini LED
  • Resolution: 3840 x 2160, 240 Hz
  • Adaptive sync: FreeSync Premium Pro, G-Sync compatible
  • HDR: Quantum HDR 2000 tier

LG UltraGear 32GS95UE-B

A 4K OLED whose dual mode is itself a scaling statement: its 1080p presentation at 480 Hz is an exact two-times relationship with the native grid.

  • Panel: 31.5-inch WOLED, 3840 x 2160
  • Refresh rate: 240 Hz at 4K, 480 Hz in 1080p dual mode
  • Adaptive sync: FreeSync Premium Pro, G-Sync compatible
  • HDR: DisplayHDR True Black 400

How to choose

Start from the panel, not the software. With a 27 or 28 inch 4K monitor, assume a 1.5 desktop scale and plan around it: budget the GPU for native 4K rendering, or make Gamescope at a lower internal resolution your default launch pattern. With a 32 inch 4K monitor, a 1.25 scale keeps the logical desktop roomy and the blur penalty smaller. With a 27 inch 1440p monitor at native scale, none of this applies. With mixed-density monitors, per-output scaling is the reason to be on Wayland at all, and Gamescope keeps games out of the mixed-scaling equation.

Then pick a default path: if most of your library runs well under the Wine Wayland driver, native rendering is the zero-maintenance answer. If you rely on XWayland titles, standardise on Gamescope rather than debugging blur per game.

Who should skip this

Skip this topic if you game at an integer scale or native resolution on a 1080p or 1440p display, where no fractional resample happens. Skip it on an X11 session, which uses a different global scaling model. Skip it if your games are already native Wayland builds that look sharp, or if you play only on a Steam Deck or Gamescope session box.

FAQ

Why is my desktop sharp at fractional scaling but my games are blurry?

Desktop applications support the protocol and render at full physical resolution. Your game most likely runs through XWayland, renders at the smaller logical resolution, and is upscaled afterwards. Same display, two pipelines.

Does fractional scaling reduce game performance?

Not by itself; the compositor’s scaling pass is a small, fixed cost. Performance follows the resolution the game renders at: native 4K costs roughly 2.25 times the pixel work of 1440p.

How do I make a Proton game render at full resolution on a scaled desktop?

Three documented routes: use the Wine Wayland driver where your Proton build supports it, set KDE’s legacy application scaling so X11 applications apply scaling themselves, or wrap the game in Gamescope with output at native resolution and game resolution set to what your GPU sustains.

Is integer scaling better for games?

For pixel-art and retro titles, yes: integer scaling in Gamescope keeps every pixel exact. For modern 3D games, render resolution and filter quality matter far more.

Final verdict

Fractional scaling on Wayland is not broken; it is specific. Protocol-aware desktop applications are flawless, XWayland games inherit a blurry bitmap upscale, native Wayland games bypass the issue, and Gamescope removes the desktop from the equation. Identify which path each game takes, standardise on native rendering or Gamescope, and a high-DPI Wayland desktop stops being a gaming compromise.

LG UltraGear 27GP950-B 27-inch 4K Nano IPS Gaming Monitor

LG UltraGear 27GP950-B 27-inch 4K Nano IPS Gaming Monitor

Check price on Amazon

GIGABYTE M28U AE Arm Edition 28-inch 4K IPS Gaming Monitor

GIGABYTE M28U AE Arm Edition 28-inch 4K IPS Gaming Monitor

Check price on Amazon

Dell G3223Q 32-inch 4K IPS Gaming Monitor

Dell G3223Q 32-inch 4K IPS Gaming Monitor

Check price on Amazon

LG UltraGear 32GS95UE-B 32-inch 4K OLED Gaming Monitor

LG UltraGear 32GS95UE-B 32-inch 4K OLED Gaming Monitor

Check price on Amazon

Explore Our Guides & Free Tools