How Windows games run on Apple silicon.

Every figure here was measured by Sevoflurane on a player’s Mac, after the player chose to share run statistics. Written reports are shown separately.

A shared run carries the game’s Steam id, the engine and renderer, the Mac’s chip, GPU core count and memory tier, the window size, the frame rate and how the session ended. It carries no name, no path and no serial number.

Each install signs its runs with a key kept in the Mac’s Secure Enclave, and Apple’s App Attest and DeviceCheck vouch that it is a real Mac. Each install counts once per game: the page shows the median of every Mac’s own median, so a thousand runs from one Mac weigh as much as one.

A frame rate counts gameplay only. The app starts counting ten seconds after the game’s first frame, once five seconds pass with no frame slower than 100 ms, and leaves out every stretch in which the game’s window was not the focused app, was hidden, or the display slept, and every frame slower than a quarter second. A run needs thirty seconds of such gameplay to carry a frame rate. Runs on a virtual display, where nothing paces the frames, carry none. Each frame rate is shown beside the refresh rate of the display it was played on.

A verdict needs three runs on the newest engine that the player or the game ended. Runs a script stopped through Sevoflurane’s command-line tool count toward neither the verdict nor the frame rate; a player pressing Stop does. Playable means most sessions lasted five minutes or more and ended when the player chose. Perfect adds a frame rate within a tenth of 60 fps, or of the display’s refresh rate when that is lower, or of the game’s own cap: when every Mac fast enough holds a game to one steady rate, such as 30 fps, that rate is its target.