Unity games on the Mac: what plays, the first launch and where saves live
SavePoint for Mac 1.0.7 plays Windows builds of Unity games through a built-in Windows compatibility layer. Mac only, one game at a time.
SavePoint for Mac plays Windows builds of Unity games you already own. It does this with a Windows compatibility layer built into the app: Wine, with FEX to run x86 code and DXMT to draw Direct3D 11 on the Mac’s graphics. Nothing is downloaded and there is nothing to install.
What plays
- A Windows build of a Unity game: a
.exebeside its_Datafolder andUnityPlayer.dll. Add the folder or the zip as you would any game. - Mono and IL2CPP games both play. 64-bit (x86-64) games are the tested case; 32-bit games are best effort.
- Games draw with Direct3D 11. A game that tries Direct3D 12 first falls back to Direct3D 11 where Unity allows it.
- Mac builds of Unity games are not supported. iPhone and iPad do not play Unity games either; they say “Unity games play in SavePoint for Mac.”
What you need
SavePoint for Mac 1.0.7 or later, on a Mac with Apple silicon running macOS 26.4 or later. Otherwise SavePoint says why: “Windows games need macOS 26.4 or later.” or “Windows games need a Mac with Apple silicon.” The compatibility layer is part of the app, so it takes some disk space: about 1 GB for the app’s engine, and roughly 770 MB more for the Windows environment once it is made.
The first launch
The first time you press Play on a Unity game, SavePoint prepares the Windows environment. The game’s page says “Preparing Windows compatibility…” and it takes 10 to 30 seconds. Wine may show a small window of its own, “The Wine configuration is being updated”, for a few seconds; leave it alone. Later launches skip this step. A game’s first picture can take a little while to appear, the first time you start it above all.
One game at a time
Windows games share one environment, so SavePoint plays one of them at a time. If you press Play on a second one, it tells you which game is running; quit that one first. Games of the other engines play as usual beside it.
Where saves live
Unity games save the way they do on Windows, inside SavePoint’s Windows environment, and not in the game’s folder. Most keep them under the environment’s AppData/LocalLow folder, and settings in its registry. A game that saves to its Documents folder saves to your Mac’s Documents folder.
SavePoint’s own save tools do not cover these saves yet. Deleting a Unity game from the library leaves its saves where they are.
What is not supported yet
- Game Assist: cheats, speed and translation.
- Sync Play and save backups for Unity games.
- Per-game settings.
- Game controllers beyond what Wine’s own controller support gives.
Reporting a game that does not play
Tell us which game and where you got it. In SavePoint, choose Export Diagnostics and send us the zip. Write to support@savepointrpg.com, or post it on SavePoint’s Discord, where other players can add what they found. If the game keeps its own log (Unity writes Player.log), attach it too: the diagnostics do not include it.