Wine is a free, open-source compatibility layer that runs Windows applications on Unix-like operating systems such as Linux, macOS and BSD. It lets people use a Windows program on those systems without rebooting into Windows or running it inside a virtual machine.
Translation instead of emulation
The name originally stood for “Wine Is Not an Emulator”, and that describes the design. Wine does not simulate a PC or boot Windows. It is its own implementation of the Windows API. When a Windows program calls a system function, Wine answers that call by translating it into the equivalent POSIX request on the host system. A request to create a window, for example, becomes a request to the host’s display system.
Because no guest operating system runs underneath, Wine avoids most of the memory and speed overhead that comes with a virtual machine. Windows programs open in ordinary windows on the Linux or macOS desktop, next to native applications. They can read and write the user’s normal files.
What kinds of Windows software it can run
Wine loads 64-bit and 32-bit Windows programs, older 16-bit Windows software and DOS programs. Graphical programs draw through the host’s display system, and DirectX support lets many Windows games run. Wine connects other Windows functions to the matching services on the host:
- sound output and input through the host audio system, such as PulseAudio or ALSA on Linux and CoreAudio on macOS
- printing through CUPS
- Windows networking (Winsock) through the host’s network stack
- serial and parallel ports, which appear to programs as COM and LPT devices
- scanners, by passing TWAIN requests to the Unix SANE system
- database access, by forwarding ODBC calls to a Unix driver manager
Compatibility is not universal. Some programs run without changes, some need specific settings, and some fail, particularly titles that depend on copy protection. WineHQ keeps an Application Database with instructions and tips for running individual programs.
Starting programs and installers
Users can usually open a Windows .exe file by double-clicking it in the file manager, or from a terminal with a command such as wine setup.exe. MSI installer packages run through Wine’s own msiexec. Programs installed this way normally get entries in the desktop’s applications menu. These entries let users start them again like any other application.
Wine also ships its own versions of familiar Windows utilities. These include a Notepad clone, an uninstaller for removing installed programs, a Control Panel, a registry editor and an Explorer-style file manager. Text-mode console programs can run directly in the terminal or in a separate Wine console window that handles full-screen output and colors.
Prefixes: separate Windows environments
Wine keeps everything a program installs inside a directory called a prefix. By default it is a hidden .wine folder in the user’s home directory. It contains a drive_c folder that programs see as their C: drive, along with the Windows registry files. Users can create more prefixes and choose one through the WINEPREFIX variable. This keeps programs apart, so one application can get its own settings. Users can delete a broken setup without touching the rest. Each prefix is created as either 32-bit or 64-bit and stays that way.
Drive letters are mappings to Unix folders. C: points to the prefix’s drive_c, and Z: points to the root of the Linux or macOS file system. This lets Windows programs open files anywhere the user has access. Users can map network shares and extra drives to further letters.
Configuring Wine with winecfg
Wine keeps most of its settings in its Windows-style registry. The usual way to change them is winecfg, a graphical configuration tool organized into tabs:
- Applications sets which Windows version Wine reports, either for the whole prefix or for one program. This helps software that refuses to run on a version it does not recognize.
- Libraries holds DLL overrides. For each library, the user chooses whether Wine loads its own built-in implementation or a native Windows DLL supplied with the program. The user also chooses the loading order. The core system libraries must stay built-in.
- Graphics controls window behavior, including confining the mouse to a program and running programs inside a virtual desktop window. The virtual desktop helps games that change the screen resolution.
- Desktop Integration installs Windows visual styles, which change the look of standard controls in all programs.
- Drives and Audio manage the drive-letter mappings and choose the sound devices.
For finer control, environment variables can set DLL overrides or switch on Wine’s debug output channels. These channels record what a failing program was doing before it stopped.
Release branches and CrossOver
WineHQ maintains three lines of Wine. The stable branch gets a major release once a year, followed by bug-fix updates, and suits programs that already work. The development branch is released every two weeks and carries most new work. Wine Staging adds several hundred experimental patches on top of development builds for programs that need fixes not yet merged. Wine is also the basis of CodeWeavers’ CrossOver, a paid product that adds simpler setup and commercial support.





