Proton · Valve

Also known as: Steam Play

On this page 7

Proton is the compatibility layer developed by Valve that allows games built for Microsoft Windows to run on Linux-based operating systems through the Steam client, without the game being ported. In the field of OS compatibility, it belongs to the family of translation-based approaches: instead of emulating a whole computer, it reimplements the Windows application programming interfaces on top of Linux and converts graphics calls into a form that Linux drivers understand.

Inside Steam, the feature is exposed under the name Steam Play, and it is the technology that makes the Steam Deck handheld practical, since that device runs the Linux-based SteamOS. Proton is open source and combines several established projects, most notably Wine, with Valve’s own patches and graphics translators.

How Proton translates Windows games for Linux

Proton works by intercepting the calls a Windows program makes and answering them with Linux implementations, so the game believes it is running on Windows. The executable itself is not modified or recompiled; the same x86-64 machine code runs directly on the processor at native speed, which is why Proton is a compatibility layer rather than an emulator.

The translation happens in several specialized layers, each responsible for one part of the Windows platform. The following table lists the main components and what each one replaces.

ComponentWindows function it replacesRole in the stack
WineWin32 and NT system interfacesLoads executables, handles files, threads, windows and the registry
DXVKDirect3D 9, 10 and 11Translates Direct3D calls into Vulkan
VKD3D-ProtonDirect3D 12Translates Direct3D 12 into Vulkan
Media foundation supportWindows video and audio decodingPlays in-game cutscenes through GStreamer
Steam integration layerSteamworks client functionsConnects achievements, overlay and cloud saves
Main components bundled in Proton

The graphics path is the most demanding part. A Direct3D shader must be converted into SPIR-V shaders for Vulkan, and the first conversion can cause brief stutter. Steam reduces this with shader pre-caching, distributing already compiled shaders collected from other players with the same hardware and driver.

Each game gets its own prefix, a directory that mimics a Windows installation with a C: drive, registry hives and system libraries. Keeping prefixes separate means that a fix applied for one title cannot break another.

Proton versions and release channels

Valve ships Proton in several parallel branches, and Steam lets the user pick the version per game from the Compatibility tab of the game properties. Choosing a branch is a trade-off between stability and newer fixes.

BranchUpdate paceBest suited for
Numbered stable releaseMajor versions a few times per yearDefault choice for most games
Proton ExperimentalFrequent, sometimes weeklyNew releases and freshly fixed titles
Older numbered releasesFrozenGames that regressed in a later version
Proton HotfixTargeted, short-livedSpecific titles flagged by Valve
Community buildsIndependent of ValveExtra patches and codecs not yet upstream
Proton branches and when to choose them

Community builds such as GE-Proton are not maintained by Valve and are installed manually into the Steam compatibility tools folder. They often fix individual games earlier, but they carry no official support and may introduce regressions.

Proton is best understood as a packaged, game-focused distribution of Wine. It differs from emulation, dual boot and native porting in cost, performance and maintenance, as the following comparison shows.

ApproachHow it worksPerformanceMain drawback
ProtonAPI translation inside SteamClose to native, sometimes fasterAnti-cheat and some media fail
Plain WineSame translation, manual setupSimilar to ProtonConfiguration effort per game
Native Linux portGame compiled for LinuxNativeRequires developer investment
Virtual machineFull Windows guestGPU access is limitedLicensing and overhead
Dual bootReal Windows installationNativeRebooting between systems
How Proton relates to other ways of running Windows games

Proton does not perform binary translation between processor architectures. On x86-64 hardware it runs code directly; running Proton on ARM devices requires an additional instruction-set translator, which adds overhead and complexity.

Unlike a classic compatibility mode in Windows, which adjusts behavior for older Windows versions, Proton bridges two entirely different operating systems with different kernels, driver models and file systems.

Using Proton in practice

Steam enables Proton automatically for verified titles, while other games require the user to switch on Steam Play for all titles in the client settings. Valve’s Deck Verified program and the community database ProtonDB both report how well a given game runs.

SituationRecommended choiceReason
Game rated Verified or PlatinumDefault stable ProtonTested configuration, fewest surprises
Recently released gameProton ExperimentalFixes arrive there first
Cutscenes show a placeholderExperimental or a community buildBetter media codec coverage
Game broke after an updatePin an older numbered versionAvoids the regression
Game needs a launch tweakAdd a launch option variableToggles a specific workaround
Typical situations and recommended Proton choices

Launch options accept environment variables that change Proton behavior, for example PROTON_LOG=1 to write a diagnostic log or PROTON_USE_WINED3D=1 to fall back to the older OpenGL renderer. A working Vulkan driver is a firm requirement; without it, the DXVK and VKD3D-Proton paths cannot run.

Limitations and common failure modes

The biggest obstacle is kernel-level anti-cheat software. Easy Anti-Cheat and BattlEye both offer Proton support, but the game developer must enable it; when they decline, multiplayer access is blocked even if the game itself runs perfectly.

  • Shader compilation stutter appears on first launch or after driver updates until the cache is rebuilt.
  • Proprietary video codecs in cutscenes may not play in the stable branch.
  • Launchers from other publishers sometimes fail to log in or update inside the prefix.
  • Kernel drivers used by DRM or peripherals cannot run, because Proton only translates user-space interfaces.
  • Performance varies by GPU vendor and driver version, so results reported by others may not repeat on different hardware.

A frequent misconception is that Proton is an emulator and therefore slow. In reality, CPU-bound code runs natively, and overhead comes mostly from graphics translation and synchronization, typically small and occasionally negative when Vulkan drivers outperform the original Direct3D path.

In plain words

Most PC games are written to talk to Windows. Proton acts like a skilled interpreter standing between the game and Linux: whenever the game asks Windows for something, Proton quietly answers in the language Linux understands.

The game never notices the difference. For the player, the result is simple: click Play in Steam on Linux and the Windows game starts, often running just as smoothly as it would on Windows itself.

A real-world example

A university computer lab switches its gaming club machines from Windows to a Linux distribution to cut licensing costs. The club owns about forty Steam titles, and only six have native Linux versions. The administrator enables Steam Play for all titles and checks each game against ProtonDB ratings before the semester begins.

Thirty-one games run with the default stable Proton without any changes. Four need Proton Experimental because their cutscenes otherwise show a test pattern, and one older strategy game is pinned to an earlier numbered release after a regression. Three competitive shooters remain unavailable because their developers have not enabled anti-cheat support for Proton.

The outcome is that about ninety percent of the library works on the new systems, and the club keeps a single short list of exceptions instead of maintaining separate Windows machines.