Skip to content
Verjuice

Docs

Getting started

Install Verjuice, log in with your key, and point it at a Windows app. It detects your hardware, picks Wine, Proton or Whisky, and launches the app in its own prefix.

Verjuice hasn't launched yet, so there's nothing to download today. Join the launch list to get an email when the first builds are out.

Install

Download the package for your system from the download section or from GitHub Releases.

macOS (Apple Silicon)

Open the .dmg and drag Verjuice into Applications. DirectX 12 titles on macOS need Apple Silicon: they run through Apple's D3DMetal, which Verjuice uses only if it's already on your Mac.

The app is the primary interface on macOS. If you prefer the command line, the installer also places a verjuice command on your PATH; open a new terminal after installing so your shell picks it up.

Linux (AppImage)

Make the file executable, then run it:

$chmod +x verjuice-linux-x86_64.AppImage && ./verjuice-linux-x86_64.AppImage

Debian and Ubuntu (.deb)

$sudo apt install ./verjuice-linux-amd64.deb

Verify the download

Every release lists a SHA-256 digest for each file. Compare it with the one you compute locally before running anything:

macOS$shasum -a 256 ~/Downloads/verjuice-macos-arm64.dmg
Linux$sha256sum ~/Downloads/verjuice-linux-x86_64.AppImage

Log in with your key

Your Verjuice key is your account. Get a free one on your account page (no card needed), then log in on each machine:

$verjuice login

Verjuice prompts for the key and stores it locally. Keep it in a password manager. We only store a hash of it, so add a recovery email on the account page if you want to be able to get back in after losing it.

Run your first app

Point Verjuice at an installer or an executable:

$verjuice run ./Setup.exe

Verjuice then works through four steps and prints each one: detect your CPU, GPU, driver and installed runtimes; query the compatibility ratings for that executable on your kind of host; route it to Wine, Proton or Whisky with the right translation layer; and launch it in an isolated prefix. If there's no working path on your host, it says so and explains why instead of trying anyway.

On macOS you can do the same from the app window instead of the terminal.

Where Verjuice keeps things

  • Prefixes: ~/.verjuice/prefixes/, one per app, never shared.
  • Logs: ~/.verjuice/logs/, with the exact configuration each launch used. Attach the log when you report a problem.

Tracked apps and plans

A free key tracks up to 3 apps. Removing an app on the account page frees its slot. Pro and Lifetime remove the limit and add priority compatibility updates and early builds; see pricing.

Troubleshooting and help

  • An app won't start: check its log in ~/.verjuice/logs/, then open an issue with the log attached.
  • It works on your machine and isn't rated yet: submit a compatibility report.
  • Titles with DRM or kernel anti-cheat that block translation layers are marked Unsupported. Verjuice never works around them.
  • Lost your key: use “Lost your key?” on the account page if you added a recovery email.
  • Anything else: support@verjuice.app.