What Wine does and why you might need it
Wine is a compatibility layer that lets you run Windows programs on macOS without needing Windows itself or a virtual machine. It translates Windows system calls into macOS equivalents in real time, so a Windows application sees what it expects while your Mac runs the code natively. This is different from virtualization, which runs a full copy of Windows inside a separate environment.
Wine works best with older Windows software and command-line tools. Modern games and professional software often fail because they rely on features Wine hasn't replicated yet. Before you install Wine, check whether the specific program you want to run has a known working status — the WineHQ AppDB database lists thousands of programs and how well they run.
On Apple Silicon Macs (M1, M2, M3 and newer), Wine support is still developing. Intel-based Macs have better compatibility and more straightforward installation. If you have an Apple Silicon Mac, you may need to use Rosetta 2 translation or choose an alternative like UTM or Parallels Desktop instead.
Key Takeaways
- Wine requires either Homebrew or a pre-built installer like WineBottler or CrossOver to run on macOS, since Apple does not include it by default.
- Intel-based Macs have much better Wine compatibility than Apple Silicon Macs, which require additional translation layers and may not work reliably.
- Before installing Wine, check the WineHQ AppDB to see whether your specific Windows program is known to work and what configuration it needs.
- Wine runs programs in isolated environments called prefixes, so you can have different versions of Windows libraries for different applications without conflicts.
- Installation takes 30 minutes to an hour on Intel Macs, but troubleshooting a program that does not run can take much longer.
Installing Wine on an Intel Mac using Homebrew
The fastest route on an Intel Mac is Homebrew, a package manager that handles downloading and compiling Wine for you. Open Terminal (in Applications > Utilities) and paste this command:
brew install wine
If you do not have Homebrew installed yet, Homebrew's website has a one-line installer you can run first. The Wine installation will take 10 to 20 minutes depending on your internet speed and Mac's processor, because Homebrew compiles Wine from source code rather than downloading a pre-built version.
Once installation finishes, verify it worked by typing wine --version in Terminal. You should see a version number like "wine-8.0" or similar. If you see "command not found", the installation did not complete — try running the Homebrew install command again.
Using WineBottler or CrossOver for a graphical installer
WineBottler is a free graphical tool that wraps Wine and makes it easier to create isolated environments for different programs. Download it from the WineBottler website, drag it into Applications, and launch it. WineBottler will download and configure Wine automatically the first time you use it.
If you want a more polished experience with technical support, CrossOver is a commercial product built on Wine that costs around $60 for a perpetual license. It includes a graphical installer, one-click setup for popular programs, and customer support. CrossOver often works with programs that plain Wine does not, because the developers test and patch it specifically for those applications.
Both WineBottler and CrossOver create separate prefixes (isolated Windows environments) for each program you install, so you can have different versions of Windows libraries without them conflicting. This is more reliable than running everything in a single shared prefix.
Checking compatibility before you install
Visit the WineHQ AppDB at appdb.winehq.org and search for the Windows program you want to run. The database shows a status for each version — Platinum (runs perfectly), Gold (runs well with minor issues), Silver (runs with some problems), or Bronze (runs but with significant issues). Some entries include detailed notes about what does not work and what configuration steps are needed.
If your program is not listed, search for similar programs in the same category to get a sense of whether Wine can handle that type of software. Games, for example, often fail because they use DirectX graphics libraries that Wine does not fully support. Older Windows utilities and command-line tools usually work better.
Check the comments section on the AppDB page for your specific program version. Users often post workarounds for common problems, like which Windows libraries to install or which Wine version works best. If the most recent comment is several years old, the program may work better or worse now depending on what Wine has added since then.
Running a Windows program with Wine
Once Wine is installed, right-click the Windows .exe file and select "Open With" > "Wine". Wine will create a prefix (a folder containing Windows libraries and settings) in your home directory under .wine, then launch the program. The first run takes longer because Wine is setting up the prefix.
If "Open With Wine" does not appear in the context menu, open Terminal, navigate to the folder containing the .exe file, and type wine program.exe (replacing "program.exe" with the actual filename). You can also drag the .exe file into Terminal and Wine will run it.
Some programs need additional Windows libraries to run. If the program crashes or shows an error, check the AppDB page again for notes about which libraries to install. You can install them by running winetricks library-name in Terminal — for example, winetricks dotnet48 installs the .NET Framework 4.8.
Troubleshooting common problems
If a program runs but displays incorrectly, try changing the graphics driver. Open Terminal and type WINEARCH=win32 winecfg to open Wine's configuration window. Go to the Graphics tab and uncheck "Allow the window manager to decorate the windows" or try switching between OpenGL and Direct3D rendering.
If a program crashes immediately, check whether you need a specific Windows library. Search the AppDB for your program and look at the comments — users usually mention which libraries are required. Install them with winetricks, then try running the program again.
If Wine is very slow, you may be running a 64-bit prefix when a 32-bit one would work better, or vice versa. Create a new prefix with a different architecture by typing WINEARCH=win32 WINEPREFIX=~/.wine32 winecfg for 32-bit or WINEARCH=win64 WINEPREFIX=~/.wine64 winecfg for 64-bit, then run your program in that prefix instead.
Apple Silicon Macs and compatibility limitations
Wine on Apple Silicon requires Rosetta 2, Apple's translation layer that converts Intel code to ARM code. This adds overhead and reduces performance. Some programs work, but many do not because Rosetta 2 cannot translate certain low-level Windows features that Wine relies on.
If you have an Apple Silicon Mac and Wine does not work for your program, consider UTM (free, open-source virtualization) or Parallels Desktop (paid, more polished). Both run a full copy of Windows ARM edition or Windows 11 on your Mac, which gives you better compatibility at the cost of higher resource use and slower performance than Wine would provide on an Intel Mac.
Check the WineHQ website for the latest status on Apple Silicon support. The Wine project is actively improving ARM compatibility, so a program that does not work now may work in a future version.
Frequently Asked Questions
Do I need to buy Windows to use Wine?
No. Wine does not require a Windows license or installation. It is a free compatibility layer that replicates Windows behavior without needing Windows itself. You only need Wine and the Windows program you want to run.
Can I run modern games with Wine on Mac?
Most modern games do not work well with Wine on Mac because they use DirectX 12 or newer graphics libraries that Wine does not fully support. Older games and indie games sometimes work. Check the WineHQ AppDB for your specific game before installing Wine.
What is the difference between Wine and Parallels Desktop?
Wine translates Windows calls to macOS calls without running Windows itself, so it is faster and uses less disk space. Parallels Desktop runs a full copy of Windows inside a virtual machine, which is slower but has better compatibility with any Windows software. Wine is free; Parallels costs around $80 per year.
Can I uninstall Wine if a program does not work?
Yes. If you installed Wine with Homebrew, type brew uninstall wine in Terminal. If you used WineBottler, drag it to Trash. You can also delete the .wine folder in your home directory to remove all prefixes and settings. Uninstalling Wine does not affect other programs on your Mac.
Why is my program running very slowly in Wine?
Wine adds translation overhead, so Windows programs are always slower than they would be on Windows itself. If a program is unusually slow, try creating a new 32-bit prefix instead of using the default 64-bit one, or check the AppDB for notes about performance settings. Some programs need specific graphics driver changes to run at reasonable speed.