Iron Gate, developers of Valheim, have not entirely written off the macOS port it seems, as pointed out by developer IronMontilyet:

We're looking into the possibilities of porting the game to MacOS, but we don't have a set timeframe for when that will happen. It's fun to see that so many people are hoping for a Mac version!

After reading an article on porting Unity games to different platforms, I started experimenting with building a custom Valheim build for macOS based on the Linux version: collecting the game data, fetching the correct dependencies and stitching it all together.

Happy to report that it actually paid off 🥳

^{The footage above has Bloom and SSAO enabled for aesthetics; turn these off for increased performance.}

The build performs surprisingly well, given that Apple deprecated OpenGL four years ago (!).

In addition, running the game on Apple Silicon hardware requires using the Rosetta 2 translation layer, which may incur an additional performance penalty.

Some statistics thanks to the kind community members of r/macgaming:

Here is to hoping that Iron Gate support macOS natively in the future with Apple Silicon and Metal support. 🍻

The build has been tested in both single / multiplayer and seems to function adequately without any negative effects.

That said, there is an inherent risk to using custom game builds. In particular, Valheim interfaces with Steam, Azure PlayFab cross-play services, and most likely Iron Gate's own services. These services could start treating this custom build as problematic (or the build itself may behave incorrectly) and put your account, characters etc. in jeopardy.

• A Steam account that owns Valheim.
• ~15GB free hard disk space. The majority of this space can be reclaimed once the build is complete.
• An internet connection to download the game data and dependencies.

These steps take between 15 to 30 minutes to complete, depending on network speed and computing power.

1. Clone this repository: git clone https://github.com/timkurvers/valheim-macos.

2. Navigate to the cloned repository in your terminal of choice.

3. Run ./build.sh and follow the instructions.

   If you would rather use the Public Test build, run ./build.sh --beta instead. Read the official Public Test FAQ to learn more.

4. Once the build script finishes, verify the presence of Valheim.app in the build folder.

5. If you are in dire need of disk space: the contents of the vendor folder can be safely deleted at this point. Those files are there to make future rebuilds faster, but are not necessary for the app to function once built.

1. Start Steam and log into an account that owns Valheim.
2. Launch Valheim.app from the build folder.

Future Valheim patches will require updates to the build script and you may not be able to play with an outdated build. Look at the top of this README to see what version of Valheim is currently supported.

To generate a new build:

1. Fetch the latest build script using git pull.
2. Optional: make a backup of the previous build by copying Valheim.app elsewhere.
3. Run ./build.sh once more.

• If a Valheim patch was newly released the script may no longer be able to produce a build altogether – not even the supported version documented here in the README. This is due to a bug in DepotDownloader. Wait for the script to be updated.

• Steam overlay is non-functional when launched directly from Valheim.app.

  • Press F2 in-game to show Valheim's built-in FPS and network details panel.
  • Alternatively: add Valheim.app as a non-Steam game and launch via Steam.

• Generating and entering worlds may seem to infinitely hang before a loading screen is shown. Be patient.

• Steam Cloud integration may misbehave: characters or worlds not syncing across devices.

  This could be since Valheim changed cloud save mechanics in version 0.209.8 in the summer of 2022. Log into Valheim on a computer which is properly synced and mark all characters and worlds as "Cloud Save" if you have not played since prior to version 0.209.8.

  Since the macOS client lacks the custom paths used by the cloud save logics of Valheim prior to 0.209.8 the cloud sync will fail silently. Technically, Valheim seems to have used Windows-specific paths and used conversion logic on Linux without any support for macOS paths, which has the effect that the macOS client cannot resolve the paths and directory structure used by the old saves (as they are saved with the old structure in Steam cloud).

  If you suspect sync trouble, check ~/Library/Application Support/Steam/logs/cloud_log.txt first.

  Notable paths for troubleshooting:

  • Local data: ~/Library/Application Support/unity.IronGate.Valheim-macOS-Custom/
  • Remote data: ~/Library/Application Support/Steam/userdata/<steam id>/892970/remote/

  The data you have stored in Steam Cloud for Valheim can be browsed online (requires login).

• Game pads / controllers may not work.

To avoid distributing copyrighted game data, the build script is provided as a means for players who own Valheim on Steam to create their own macOS build and play on their preferred hardware.

Additionally, pre-built binaries from untrusted sources could cause havoc if malicious. Having an open-source build-script available for vetting by anyone limits that risk.

As the game cannot be launched directly from macOS Steam, launch it manually with the desired arguments:

open build/Valheim.app --args -console

This is to avoid any collisions with a potential future macOS version by the official development team.

The icon is the profile image of the official Valheim Twitter account and is property of Iron Gate.

Feedback, issues, or pull requests with improvements are more than welcome! 🙏