Whisky, the community fork keeping a Mac Wine wrapper alive

An upstream archive turned into a maintained fork

The original whisky-app/whisky repository was archived on April 9, 2025 with a final maintenance notice, and the fork carries that history in its own README. The description calls Whisky an active community fork maintained by frankea, and the repository itself is not archived. The last push was on 2026-10-01, and the release list shows app-v3.7.0 (Whisky 3.7.0) on 2026-08-30 alongside two Wine Libraries builds, v4.6.4-beta.1 and v4.5.105-beta.1, which pair GPTK with Wine 11.16 and Wine 11.15.

That pairing of a shipping app release with beta-tagged Wine library releases is a useful signal about how this project ships. The app and the runtime move on separate tracks, so a user can be on a current Whisky build while the bundled Wine and graphics libraries are still on a beta.

The fork also states its own scope plainly: it is not affiliated with the original project or with getwhisky.app, and it says it continues upstream work by addressing the backlog of upstream issues. The README names version 3.0.1 as the release that shipped 54 requirements covering the ten categories of upstream issue tracking, referenced as issues 40 through 50. For someone deciding whether to move, that backlog is the concrete argument, since the alternative is an archived build with no path to fixes.

Bottles are the unit of management and they live inside the container

The core object in Whisky is the bottle: a self-contained Wine prefix that holds an installed Windows application, its files and its configuration. The app lets you make and manage bottles, install and run Windows apps and games, and the README describes one-click bottle creation and management as a headline capability.

Where bottles live matters more than usual here. The default bottle location sits inside the app container at `~/Library/Containers/com.franke.Whisky/`, and the app supports a custom folder location instead. The Bottle, then Reveal in Finder menu item exists specifically so you can check where a bottle actually lives before you delete anything, and the uninstall instructions repeat the warning that removing the container deletes every bottle stored in its default location.

Bottles can also be exported and imported by hand through the old Bottle, then Export and File, then Import Bottle route, which the README points at as the option if you would rather move a bottle to another Mac yourself. Keeping a portable, inspectable artefact like that is the reason some people prefer the manual route even when the in-app importer would do the job.

DXMT first, DXVK over MoltenVK as the fallback

Graphics translation is the part of running Windows games on a Mac that usually breaks, and Whisky's answer has two layers. DirectX 11 goes through native Metal translation with DXMT out of the box, and DXVK over MoltenVK serves as the universal fallback. The README lists Wine 11.0 as the latest stable Wine it ships with, described as having improved compatibility and networking.

Two smaller features sit alongside that. Launcher compatibility is built in for Steam, Epic, EA App, Rockstar, Battle.net and others, which is what makes the wrapper useful for games distributed through storefronts rather than for stand-alone executables. Controller support is handled through SDL environment variable controls for gamepad detection and mapping issues, a detail that matters more for the launcher use case than for ordinary desktop apps.

There is also a stability side. The feature list names one-click diagnostic reports for troubleshooting crashes and freezes, and the repository carries a `WhiskyKit` target with a coverage badge, plus `WhiskyUITests` and a `scripts/` directory. A diagnostic report is the kind of feature that only matters once something has already failed, which makes it a good sign about how the project treats debugging rather than a headline.

The cask name is the trap: the default still installs the archived build

Installation is a single Homebrew cask, and the README is emphatic about which form to use.

brew install --cask frankea/whisky/whisky

That qualified form taps frankea/homebrew-whisky and installs the latest signed and notarized DMG, and `brew upgrade --cask` picks up new releases from there. The unqualified `brew install --cask whisky` still installs the archived original, whose last release was in April 2025, and the README says that will always be the case until that cask is updated. Anyone who reads the app name and types the short command gets the dead build with no warning from Homebrew.

The manual path exists for people who do not want Homebrew at all. You download the latest `Whisky-X.Y.Z.dmg` from the releases page, open it and drag `Whisky.app` into `/Applications`, then launch. On first run the app downloads the Wine runtime, which is roughly 330 MB, and sets up your default bottle. In-app updates arrive through Sparkle from an appcast file hosted with the project documentation.

Migrating bottles in place from the original app

Existing users of the archived original are the audience the migration path is built for. The README states plainly that running the original today means running a stale build with no path forward for new fixes, and that bottles are referenced in place rather than moved or copied, so the original app keeps working if you want it around.

The steps are short. Install the fork, open it, and choose File, then Migrate from the Original Whisky. The app looks in `~/Library/Containers/com.isaacmarovitz.Whisky/` for the bottles the original left behind and imports the ones you pick. Removing the original afterwards is a separate move, either dragging `/Applications/Whisky.app` to the Trash or running `brew uninstall --cask whisky`, and your bottles stay where they are.

The reason bottles are not shared automatically is bundle identifiers. The original app uses `com.isaacmarovitz.Whisky` and this fork uses `com.franke.Whisky`, so the two apps keep separate containers. The README also notes that with no critical bottles you can skip migration entirely, because the new app creates a fresh bottle on first launch.

Uninstalling leaves the Wine runtime and bottles in place

Removal is deliberately incomplete, and the README explains why. Dragging `Whisky.app` to the Trash, or running `brew uninstall --cask frankea/whisky/whisky`, removes the app but leaves the Wine runtime, your bottles and app data behind, by design, so that reinstalling does not re-download roughly 330 MB and does not lose your bottles.

A complete removal means deleting the app and then several paths under `~/Library`, and the README warns that removing the container deletes every bottle stored in its default location.

rm -rf "/Applications/Whisky.app"          # or: brew uninstall --cask frankea/whisky/whisky
rm -rf ~/Library/Containers/com.franke.Whisky
rm -rf ~/Library/Application\ Support/com.franke.Whisky
rm -rf ~/Library/Caches/com.franke.Whisky
rm -rf ~/Library/Logs/com.franke.Whisky

Bottles created in a custom folder live wherever you put them and must be deleted separately. Migrated bottles that still belong to the original app live under the older `com.isaacmarovitz.Whisky` container and are not touched by those steps.

Apple Silicon and macOS Sequoia are hard requirements

Whisky is not a general Wine installer for Macs. The system requirements section names Apple Silicon M-series chips for the CPU and macOS Sequoia 15.0 or later for the operating system. There is no Intel path listed, and the project targets Apple Silicon outright, which is also why the graphics stack is built around native Metal translation rather than a compatibility layer for older GPUs.

The licence is GPL-3.0, and the repository carries a LICENSE file plus a SECURITY.md and a CODE_OF_CONDUCT.md. The GPL-3.0 identifier matters for anyone thinking about redistributing the app or a build of it inside a product, and the text of the licence governs that question rather than anything the README says.

On privacy, the README states that Whisky sends no data by default. During first-run setup you can opt in to anonymous usage telemetry through a checkbox that is off unless you tick it, and there is a toggle under Settings, then Privacy that you can change at any time. When enabled it sends five events covering the first-run funnel, and the README section on telemetry is where the detail lives.

Editorial conclusion

Whisky fits Mac owners on Apple Silicon who want to run Windows applications and games without living in a terminal, and who are willing to accept that it is a fork carrying a GPL-3.0 licence and a manual migration path from the archived original. It does not fit Intel Macs, macOS versions below Sequoia 15.0, or anyone who needs a commercial distribution agreement. Before adopting it, run `brew install --cask frankea/whisky/whisky` rather than the unqualified cask, confirm your machine is an M-series chip on macOS 15.0 or later, and if you are moving from the original app, use File, then Migrate from the Original Whisky so bottles are referenced in place instead of copied.

Frequently asked questions

Official sources

1. frankea/Whisky on GitHub
2. License: GPL-3.0
3. Project website
4. README
5. Releases