Guide:Path of Exile on Mac using Windows Client

From Path of Exile Wiki
Jump to navigation Jump to search

This is a guide on the subject of installing Path of Exile on Mac using Windows client.

Last updated on March 6, 2025.


This guide explains several ways to install and run the Windows client for Path of Exile and Path of Exile 2 on Mac systems, as an alternative to using the MacOS standalone or Mac Steam clients.

It also includes instructions on a workaround for a known patching issue and an outline of how to setup the Windows version of Path of Building (PoB) on a Mac.



Overview

This guide arose out of necessity due to issues with the Steam and Mac standalone clients on POE 1.0 that GGG were unable to resolve as of August 2024. Issues became progressively worse, especially in release 3.25 of POE 1.0. The issues include multiple login failures and disabling of multi-threading on the Steam client (with impact to overall performance), along with patch update problems, an FPS cap and long standing graphics issues on the standalone client. The guide also covers POE 2, which is currently in EA and does not have a native Mac client (neither standalone or Steam). As of January 2025 players using Monterey operating system are no longer immune from the issues mentioned. They will also need to choose an option below to run POE 1.0 and POE 2 EA smoothly. They will need to upgrade to Sonoma first to do so.


There are 4 available options for POE 1.0 on M series systems. Both Whisky and the Windows Steam client were also tested, but not recommended. At low settings and monitor resolution, both will run either game, but not at the same FPS as the options outlined. Whisky is also intentionally restricted (by the developer) to using WINE 7.7 and GPTK 1.1. It therefore misses out on a number of bug fixes and performance improvements in later versions of WINE and GPTK. The steam client can sometimes be very slow to open and to update. Users can certainly use either of these options if they prefer, but they should be aware of and understand the impact on game performance of these limitations.


The 3 free options are Kegworks (KWS), portingkit (PK) and Apple's GPTK. The 4th option is to use Crossover (CO) by Codeweaver. This option requires a license purchase after a 2 week trial (a discount code TOM23 will provide a 20% discount) All options were configured, tested and verified using an M1 series Macbook Pro using Sonoma 14.6.1. Other players have also verified the options work on an M series (Apple Silicon) Mac mini, Macbook Air and iMAC.


There are 3 options (2 free) available for Intel based systems. PK, CO and Bootcamp. Bootcamp setup is not covered here as there are plenty of guides out there on how to setup it up. A 4th option, KWS, may also be possible with Intel based systems, but this has not been tested. For Intel systems, the engine WS12WineCX64Bit22.1.1 has been verified to work with PK. Do not use D3DMetal engine options. They will not work on Intel systems. The renderer_type in production.Config.ini will also be different. You will need to use renderer_type=Vulkan on Intel systems.


Note: As of February 26th 2025 there are only 2 options for POE 2 EA on both Apple Silicon and Intel systems. Those are Kegworks and Crossover. Neither portingkit or GPTK can run POE 2 (POE 1 is unaffected). This is due to the patch update 0.1.1e


All options have similar performance with regard to FPS, with up to 140+ FPS being reported with KWS (with low settings and low resolution graphics). Performance for each option, will however, vary depending on system configurations (CPU, Memory and disk type). Given performance is roughly the same for each option, players are generally free to use any option. Both KWS and PK are simple to setup. PK has a slightly more user friendly GUI. Apple's GPTK, although free, is command line based, so more complex to configure. It also requires registering as a developer with Apple (this is free atm). Crossover is perhaps the most GUI driven and friendly but requires purchasing. If a player already has Crossover they should leverage it, otherwise use one of the other 3 options.


System Requirements

For an M series Mac, your system must be running Sonoma 14.0 or a later OS. This is because POE (both games) requires DirectX12 and DirectX12 requires Sonoma or later. It is recommended you have a Pro or higher CPU. It is also recommended to have a minimum of 16GB of memory. Lower model CPU, even with 16GB, will likely not run the game well, if at all, even at the lowest settings. Before upgrading your operating system, check Apple requirements to run Sonoma. Before upgrading do a backup of the current system. While it is technically possible to run Sonoma or later on a Mac that does not support it using Open Core Legacy Patcher (OCLP) it is beyond the scope of this wiki to detail.


For Intel series, upgrading to Sonoma is NOT required since Intel systems use Vulkan based, not DirectX based drivers for graphics. System specs for Intel systems are slightly different, but the same rule of thumb applies. The higher the CPU processor and the amount of RAM available the better. An i7 CPU with 16GB probably should run the game at a decent FPS with settings on lowest options.


Steam Users

You do not have to uninstall either Steam or the Mac standalone client to use one of the methods below. It is recommended to clean up extra installs no longer required to free up disk space if needed at some point. For Steam users, you may need to do the following to login to what will effectively be a standalone client now. If you've played POE, you have a standalone POE account. This step is not required if you know your GGG account name and password.

  1. Go to the GGG homepage and login via steam
  2. Click on your account name and click on Manage account
  3. You'll see your email. Either set up a password or reset it via the forgot your password login option.
  4. Use those credentials to log in in-game


Note: This does not apply to those who used the Mac standalone client. You will use the same credentials as you did before if you have made the swap to one of the methods below.


The GeForce Now (GFN) option

Based on player feedback, any base systems (iMAC, Macbooks or Mac mini), even with 16GB of memory, will run the games poorly, if at all. Expect FPS or 20FPS or less. POE and POE2 are resource intensive games. Even some high end Windows systems can't run fully juiced maps. The only option at this time, is to use GeForce Now. This provides a virtual system, which will emulate a Windows system with enough CPU, GPU and memory to run the game adequately. There are, as of this writing, 4 tiers of service available. A free one - which will provide a base system - and 3 tiers of paid service. The top tier provides the most powerful CPU, GPU and memory configuration.

There are a number of limitations to be aware of when using GFN

  1. The game is F2P. Using GFN is not (except for the free tier).
  2. You can have a potato system, but you need a decent internet connection. 500MB minimum (wireless or hard wired), is recommended.
  3. There are login queues for every tier, including the most expensive one. It can sometimes take a while to gain access, even for paying customers. If you are logged out for any reason, you have to join a queue again.
  4. Updates are slow. They can be several hours behind when patches are first released by GGG.
  5. You cannot use 3rd party apps, such as Exiled-Exchange. The only exception are web based filters.
  6. Unlike Steam, game time is limited to 100 hours per month, in both the free tier and most of the paid tiers. There is an additional fee if you need more game time.
  7. You may exceed your monthly bandwidth usage depending on the type of Internet plan you have with an ISP.
  8. It's an unplanned expense for a free game. You can choose to have food or a place to stay every month, but not both.


Windows Installer download

Installer download link. You generally need to be logged into the sites to get the files

  1. POE 1 Windows Installer
  1. POE 2 EA Windows Installer


POE 1 Setup options

Kegworks (KWS) Setup

WineskinServer has been replaced with Kegworks. The software can be found at Kegworks. To setup KWS do the following

  1. Install Homebrew, via a terminal session, if it is not already there. Once done execute the 3 commands outlined on the Kegworks github page. This will install Kegworks Winery.app in the Applications folder (/Applications).
  2. Go to Applications and right click -> open Kegworks Winery.app. There will be no wrapper or engines preinstalled. Update the wrapper version first. Always update to the latest version available (the app will tell you if a newer version is available. Follow the steps to update it).
  3. Next add an engine. It is recommended to use the latest engine available. The app will notify of new engines. Note: this is a bit misleading. A new engine means a new version of a specific engine. It does not mean a new version you should use for POE. Only update the same engine type that POE is already using i.e CX24.0.5 -> CX24.0.7. If you are asked for it, the Windows version for setup can be Windows 10 or Windows 11.
  4. Select Create New Blank Wrapper. Choose whatever name you want to call the wrapper (such as PoE). Click OK. This will take several minutes, depending on your system. Click OK on Wrapper creation finished message.
  5. Go to /User/<username>/Applications/Kegworks. Select the wrapper previously created. Right click -> Show Package Contents -> Contents -> KegworksConfig -> Open.
  6. Select Install Software from the options. Select Choose Setup Executable. Select the appropriate PathOfExileInstaller.exe file (where ever you downloaded it to on your system). This will then create the base POE folder and files.
  7. Another pop will display "Choose Executable" with 3 options in a drop down. Select C:\Program Files (x86)\Grinding Gear Games\Path of Exile\PathofExile.exe only.
  8. Once finished select the Advanced tab option on the Kegworks menu that should appear. Select the Direct3D to Metal option on Configuration tab.
  9. Check the wrapper and Engine versions. They should be the latest version of each. Change them if they are not (under Tools tab).
  10. From Tools menu select Test run. This should kick off the full install (all 40+GB). If it doesn't check the engine and make sure it is set correctly.
  11. If you want to see the install progress right click on the Wrapper file in the Kegworks folder. Select Show Package contents -> Contents -> drive_c -> Program Files (x86) - Grinding Gear Games -> Path of Exile. You will see each file added.
  12. Once install is done Do Not launch the game.
  13. First check that mach semaphore synchronization (msync) is enabled in the Options tab of the Kegworks menu (same menu as step 8 above). It should be the last check marked box.
  14. Skip this step for POE 2.0 EA Only do this step for POE. Go to /User/<username>/Applications/Kegworks. Right click and select Show Package Contents. Go into /Contents/Frameworks/renderer/d3dmetal. Remove the 2.0 & 2.1 directories. The wrapper will now use D3DMetal-v1.1
  15. Next go check the production_Config.ini file entry renderer_type=DirectX12 . The file path is the MacOS file path NOT the drive_c one. MacOS file path is /Users/<username>/Documents/My Games/Path of Exile. If the entry is not correct update it. If the file does not exist, start the game anyway. It will fail to start but the file should now be created. Check the file and update the renderer_type if it is not correct. Note: For Intel based systems the renderer_type=Vulkan
  16. You can launch the game by right clicking -> open or double clicking the Keg icon for the wrapper your created. This may take a minute or so as POE performs a cache cleanup on start each time. You can drag the icon to the dock for future quick access.

Note: If for some reason you no longer need KWS you can uninstall it by opening a terminal session and typing brew uninstall --cask Kegworks. This will remove the application. You will need to manually remove the Kegworks folder in the Applications folder (/Users/<username>/Applications/Kegworks). The production_Config.ini will NOT be removed as part of any process.


portingkit (PK) Setup

Note: PK is no longer an option to run POE2. You can still use it for POE and any of the other apps, such as PoB and PoB2

portingkit can be found at portingkit. This option is available for both M series and Intel based system. To setup PK do the following

  1. Download the latest version of portingkit (6.3.2 as of this writing).
  2. Select Custom port from All Games (LHS side app menu). Name the port (whatever you want).
  3. Select the Engine and Operating system. Select the engine WS12WineCXBit23.7.1-3_D3DMetal-v1.1 (if available) or WS11WineCX64Bit23.7.1_D3DMetal-v1.1 for M series. Select WS12WineCX64Bit22.1.1 for Intel series. The OS can be either Win10 or Win11.
  4. Select the appropraite PathofExile (PathofExileInstaller.exe) installer file (where ever you downloaded to on your system).
  5. portingkit will go through the wrapper setup. This may take a while depending on your system. When you see the POE install screen pop up click Install and let it run. If installed correctly you will see the "Installation complete" screen. Press close to continue.
  6. Select C:\Program Files (x86)\Grinding Gear Games\Path of Exile\PathofExile.exe only from the next pop up box. This should complete the initial install.
  7. Start POE via portingkit. This will kick off the update to install the full game (the 40+GB).
  8. Once that is done you need to check that you have renderer set to DirectX12 in the production_Config.ini file on an M series Mac. This file should be found in /Users/<username>/Documents/My Games/Path of Exile/ folder. Under the DISPLAY section find renderer_type. Change it to renderer_type=DirectX12. On Intel based systems the renderer setting must be set to renderer_type=Vulkan. Save the file once configured correctly.
  9. If the file does not exist, start the game. It will likely error out. The file should now exist though. Edit it (with whatever editor of choice you use) to have the setting outlined above depending on your system (M series or Intel). Save changes.
  10. Launch the game. It should start up as normal and you can explore Wraeclast.

Note: There is an option to change the icon however I could not get this to work.


Crossover (CO) Setup

This method should work on both M series and Intel based systems. The Intel based configuration settings are provided but have not been tested.

  1. Install CrossOver (Paid).
  2. Install CXPatcher (optional).
  3. Install PathOfExile client (Installer file) into bottle (Windows 10 or Windows 11). The appropriate PathOfExileInstaller.exe file can be downloaded from the links in the overview section.
  4. You can also install the steam client in CO, however this is not recommended for reason outlined in the overview section.
  5. Enable D3DMetal and MSync for M series Mac's. For Intel systems leave D3DMetal option off. It is not known if you need to have DXVK option on or off for Intel systems. Select Msync.
  6. Locate and open the configuration file in ~/Documents/My Games/Path of Exile/production_Config.ini for M series systems. If the file has text, change the renderer_type setting from Vulkan to DirectX12. If the file is empty, add "[DISPLAY]" in one line, and "renderer_type=DirectX12" in another line underneath it. For intel-based systems, this step may not be necessary. For Intel systems the file location is the same however the renderer_type MUST be set to Vulkan.


Apple GPTK Setup

This guide covers configuring POE 1.0 using GPTK (Apple Game Porting Kit) v1.1 on Sonoma 14.5 via the command line. It can only be used on a M series mac. Command line syntax can either be pure Unix commands or a mixture of Unix and Windows syntax. Both commands types are valid. Both are included here. All commands in the guide are run in a terminal window (either the default terminal or a program such as iterm2, which is free), except for the script that automates starting the game via a shortcut.

Note: You cannot use GPTK for POE 2 EA.

It is assumed that users have configured their system to use GPTK. If not head over to Apple Gaming wiki or use the Outcoldman's guide, which outlines another game (with a better name gaming convention then "my-game-prefix").

After you have completed the GPTK setup via one of the guides, download the appropriate Path of Exile Windows installer file from the links in the overview section. It should be in the Downloads folder in /Users/<username> AND in the game prefix directory you setup (mine is Users/<username>/Games/GGG//drive_c/users/crossover/Downloads).


To run the installer enter a similar command to that below in the terminal window

"gameportingtoolkit ~/Games/GGG ~/Games/GGG/drive_c/users/crossover/Downloads/PathOfExileInstaller.exe" OR "gameportingtoolkit ~/Games/GGG "C:\users\crossover\Downloads\PathOfExileInstaller.exe"""


This will run the installer program. You can choose a different folder to install the game in or leave it at the default (it will take a few seconds before it starts). This will install Content.ggpk, PathOfExile.exe and Redist (folder) in the default directory, or the directory you provided during setup.


Change to the directory where PathOfExile.exe was installed. Typically it will be similar to the following

"cd ~/Games/GGG/drive_c/Program\ Files\ \(x86\)/Grinding\ Gear\ Games/Path\ of\ Exile"


Run the following command (substitute in your own directory names) to have Path of Exile perform a full install

"gameportingtoolkit ~/Games/GGG ~/Games/GGG/drive_c/Program\ Files\ \(x86\)/Grinding\ Gear\ Games/\Path\ of\ Exile/PathofExile.exe" OR "gameportingtoolkit ~/Games/GGG "C:\Program Files (x86)\Grinding Gear Games\Path of Exile\PathOfExile.exe"""


This will perform a full install of Path of Exile into the correct directory. After the install is finished DO NOT click Launch. Exit the program.


Next go to production_config.ini (it will likely be empty). Add the line and save the file [DISPLAY] renderer_type=DirectX12

This files is usually found in /Users/<username>/Documents/My Games/Path of Exile/ . It will also be in /Users/<username>/Games/GGG/users/crossover/Documents/My Games/Path of Exile


Your almost there. Now cd (change directory) to the directory that PathofExile_x64.exe resides in, which will be /Users/<username>/Games/GGG/drive_c/Program\ Files\ \(x86\)/Grinding\ Gear\ Games/\Path\ of\ Exile or the directory you specified at install time. You MUST cd to the directory, otherwise the game will not run. Run the following command (change the directory name to whatever you set up)


"arch -x86_64 /usr/local/bin/gameportingtoolkit-no-hud ~/Games/GGG ~/Games/GGG/drive_c/Program\ Files\ \(x86\)/Grinding\ Gear\ Games/\Path\ of\ Exile/PathOfExile_X64.exe" OR "arch -x86_64 /usr/local/bin/gameportingtoolkit-no-hud ~/Games/GGG "C:\Program Files (x86)\Grinding Gear Games\Path of Exile\PathOfExile.exe"""


After a few seconds there should be a flash on screen followed by the game starting up as per normal. You will then be able to login and play. You can go into options and change the settings to whatever is appropriate to your system. You should achieve 60+FPS in game and in HO (hideout), far more than the native Mac client allows.


You can set the commands up in an Automator script. How to do that is outlined in outcoldman's guide (including how to change the icon). Included below is what my script looks like.


#!/bin/zsh

export PATH="/usr/local/bin:${PATH}" # This isn't strictly necessary if you have already set this path in your profile

cd ~/Games/GGG/drive_c/Program\ Files\ \(x86\)/Grinding\ Gear\ Games/\Path\ of\ Exile ; (arch -x86_64 /usr/local/bin/gameportingtoolkit ~/Games/GGG ~/Games/GGG/drive_c/Program\ Files\ \(x86\)/Grinding\ Gear\ Games/\Path\ of\ Exile/PathOfExile_X64.exe) || true OR cd ~/Games/GGG/drive_c/Program\ Files\ \(x86\)/Grinding\ Gear\ Games/\Path\ of\ Exile ; (arch -x86_64 /usr/local/bin/gameportingtoolkit-no-hud ~/Games/GGG "C:\Program Files (x86)\Grinding Gear Games\Path of Exile\PathOfExile.exe") || true


The cd line above will show HUD in the top RH corner of screen. The second cd line gives the option to mask HUD. You only need 1 of these options in the script not both (or just comment one out if you feel like swapping between the 2 modes).


POE 2.0 EA Setup options

POE 2.0 EA setup processes are essentially the same as those outlined above for POE 1.0. However, you cannot use portingkit or GPTK to run POE2 EA. Your options are Kegworks (free) and Crossover (paid).

The main differences between POE 1 and POE 2 installs to be aware of are as follows:

  1. The installer file is PathOfExile2Installer.exe. Substitute this in KWS at step 6 and CO at step 3. Also note that the full install of POE 2 EA will be around 90GB, not the 40GB that POE is.
  2. The game executable is the same as POE 1 (not confusing at all ...) but lives in the folder Path of Exile 2. Substitute this path and run in KWS at step 7.
  3. The POE 2.0 EA config_ini file lives in Documents -> My Games -> Path Of Exile 2. Make the change in that folder as per KWS at step 13 and CO at step 6
  4. Update the production_Config.ini file with the appropriate configuration based on your Mac model:

For M series Mac: 

[DISPLAY]
renderer_type=DirectX12

For Intel series Mac: 

[DISPLAY]
renderer_type=Vulkan

Patch Update Workaround for POE 1.0 & POE 2.0 EA

Occasionally you might run into an issue that the update process can't overwrite the Path of Exile executable using one of the Windows clients. It occurs if using either KWS, PK or CO. To fix this (and sadly you will need to do so every time it happens) follow the steps below. The process is slightly different for KWS and PK. If someone does encounter this issue In GPTK, the fix is the same. You will need to access the Path of Exile directory where-ever it has been installed and change the files as per instructions below

Kegworks (KWS)

  1. You need to change 2 files in the Path of Exile directory (usually found in C:\Program Files (x86)\Grinding Gear Games\Path of Exile. For POE 2 EA the directory will be C:\Program Files (x86)\Grinding Gear Games\Path of Exile 2).
  2. To get to this directory in KWS right click on the game icon and choose "Show Package Contents".
  3. Under the Contents folder go to drive_c -> Program Files (x86) -> Grinding Gear Games -> Path of Exile OR drive_c -> Program Files (x86) -> Grinding Gear Games -> Path of Exile 2.
  4. Rename the PathOfExile.exe or PathOfExile_x64.exe to PathOfExile.old (in the appropriate game folder. Note: Both games use the executable name PathOfExile. Make sure you are in the correct game folder)
  5. Rename the PathOfExile.tmp to PathofExile.exe
  6. You can now either double click the new PathOfExile executable or launch the game again to start the update. It should now update without encountering the error.

portingkit (PK)

  1. You need to change 2 files in the Path of Exile directory (usually found in C:\Program Files (x86)\Grinding Gear Games\Path of Exile. For POE 2 EA the directory will be C:\Program Files (x86)\Grinding Gear Games\Path of Exile 2).
  2. To get to this directory in PK right click on the game icon and choose "Show in Finder".
  3. Under the Contents folder go to drive_c -> Program Files (x86) -> Grinding Gear Games -> Path of Exile.
  4. Rename the PathOfExile.exe or PathOfExile_x64.exe to PathOfExile.old.
  5. Rename the PathOfExile.tmp to PathofExile.exe
  6. You can now either double click the new PathOfExile executable (this may not work) or launch the game again to start the update. It should now update without encountering the error.

Crossover (CO)

  1. Select Open C: Drive in the bottle menu for POE 1.0 or POE 2.0 EA
  2. Go to Program Files (x86) -> Grinding Gear Games -> Path of Exile OR Program Files (x86) -> Grinding Gear Games -> Path of Exile 2.
  3. Rename the PathOfExile.exe or PathOfExile_x64.exe to PathOfExile.old (in the appropriate game folder. Note: Both games use the executable name PathOfExile. Make sure you are in the correct game folder)
  4. Rename the PathOfExile.tmp to PathofExile.exe
  5. You can now either double click the new PathOfExile executable (this may not work) or launch the game again to start the update. It should now update without encountering the error.

GPTK

GPTK does not seem to be affected by this patch issue. If it were to happen the fix would be the same steps as above. Find the Program Files (x86) -> Grinding Gear Games -> Path of Exile. Rename the appropriate files. Restart the game update.

Path of Building - Community Fork (PoB) Setup

Players can run the Windows version of PoB using KWS, PK or CO instead of the Mac port of PoB. The advantage of doing so is that updates are provided sooner and functionality is smoother. It's likely the Windows version of PoB will also run under GPTK but it would be overkill when the other apps are far easier to setup in this case. The process to setup PoB is straight forward.

Note: It seems that when using PK you can only have one WINE process at a time running. You can't run both POE and PoB simultaneously. It is therefore recommended not to use PK for PoB if you want to have both game and application open at the same time. To setup the Windows version of PoB do the following

POB using Kegworks (KWS), portingkit (PK) or Crossover (CO)

  1. Download the latest version of PoB from either the PoB on github page or PoB community build website
  2. Create a wrapper with an appropriate name.
  3. For engine in KWS use the latest CXxx.x.x . For PK use WS11WineCX21.2.0 (or something similar). CO will automatically choose an engine.
  4. Do not select DXVK, D3DMetal, Mysnc or Esync options. See the exception to this for POB2 below.
  5. Follow the onscreen install instructions. Defaults will generally do. If you wish to change the directory on the C: drive (not to be confused with the Application path on the Mac) you can do so (C:\PoB for example, instead of the lengthy path which is usually in the C:\username\appdata folder on Windows).
  6. A screen asking which executable to use should pop up near the end of install. Make sure to select the PathOfBuilding.exe file !
  7. Create or drag the icon to the dock for easy access.
  8. You should now be able to start up PoB and run it side by side with POE if needed.


Path of Building 2 - Community Fork Setup

The setup of PoB2 is exactly the same as POB, with one exception. D3DMetal must be enabled for POB2 to work. You can download the latest version of POB2 at POB2 on github After downloading, follow the setup guide for POB, EXCEPT for step 4. You will need to enable D3DMetal


Trade App for POE 2 EA

Awakened POE has been replaced with a new program for POE 2 EA called Exiled-Exchange-2. To use it do the following

  1. Install POE 2 via one of the methods described above for your system
  2. Download and install the latest release of the universal dmg file Exiled-Exchange-2
  3. Run the following commands in a terminal session using whichever terminal app you are comfortable with
    xattr -d com.apple.quarantine /Applications/Exiled\ Exchange\ 2.app
    codesign --force --deep --sign - /Applications/Exiled\ Exchange\ 2.app
    /Applications/Exiled\ Exchange\ 2.app/Contents/MacOS/Exiled\ Exchange\ 2 (This command runs EE2. You will need to run this each time, so save the command or build a script to run it.)
  4. Start POE 2 EA.

External links

Retrieved from "https://www.poewiki.net/index.php?title=Guide:Path_of_Exile_on_Mac_using_Windows_Client&oldid=1535878"