Gamescope session and presentation overview

Scope

This page covers Gamescope as a presentation component. It does not replace Proton, Wine, a graphics driver, or the desktop compositor in every deployment.

Session models

ModelPresentation path
Embedded gaming session
Gamescope can present through DRM/KMS
Nested desktop session
Gamescope presents through the host Wayland or X11 session

Upstream calls Gamescope a micro-compositor and documents both models.

Responsibilities

Gamescope can provide a controlled game-facing resolution, scaling, frame-rate behavior, and presentation boundary. Actual HDR, VRR, scaling, and latency behavior depends on the build, driver, session, display, and command line.

Verification

Identify whether the session is embedded or nested, then capture the Gamescope version, command line, display mode, driver, and observed frame-time behavior.

Known issues

Do not copy flags between SteamOS Gaming Mode and an arbitrary desktop session without checking upstream support. Similar visible output does not imply the same DRM/KMS path.

Frequently asked questions

Does Gamescope make an unsupported display feature work?
Does Gamescope make an unsupported display feature work?
Not by itself. HDR, VRR, scaling, and presentation support also depend on the Gamescope build, session type, kernel, graphics driver, connector, and display.
Is a nested Gamescope window identical to SteamOS Gaming Mode?
Is a nested Gamescope window identical to SteamOS Gaming Mode?
No. A nested session presents through a host compositor, while the embedded SteamOS session can use DRM/KMS directly. Their behavior and available flags can differ.

Sources

Version history

  • 2026-07-15: Phase 3 reviewed edition with embedded and nested session boundaries.