Chiip

Download

Pick your system. The buttons always lead to the latest release; a new release shows up here by itself.

The latest release is on GitHub

Windows

Windows 10 or newer, 64-bit

Download for Windows

macOS

macOS 11 or newer, Apple silicon and Intel

Download for macOS

Linux

64-bit, with a Vulkan driver

Download for Linux

If a button leads to the release page instead of a file, pick the zip for your system there. All releases.

Check your download

Every release has a file SHA256SUMS.txt with the SHA-256 checksum of each zip. Compare yours with it to be sure the file is the one that was published and arrived whole:

# macOS or Linux, in the folder with the zip and SHA256SUMS.txt
shasum -a 256 -c SHA256SUMS.txt --ignore-missing

# Windows PowerShell
Get-FileHash .\Chiip-*-windows-x86_64.zip -Algorithm SHA256

On Windows, compare the printed hash with the line for your file in SHA256SUMS.txt.

The downloads are not signed (a signing certificate costs money every year), so your system warns you the first time. That is expected; here is how to get past it.
Windows: SmartScreen
  1. Unzip the download and double-click Chiip.exe.
  2. If it says Windows protected your PC, click More info, then Run anyway.
  3. The first time you host a game, Windows Firewall asks about Chiip: tick Private networks and allow it.
macOS: Gatekeeper
  1. Unzip it and drag Chiip.app to Applications (or anywhere).
  2. Right-click the app, choose Open, then Open again.
  3. On recent macOS that button may be missing: open System Settings → Privacy & Security, scroll down to "Chiip was blocked" and click Open Anyway.
  4. If macOS says the app "is damaged" (it isn't; it is the download's quarantine flag), clear it in Terminal and try again: 
    xattr -dr com.apple.quarantine /path/to/Chiip.app
  5. The first time you host a game, macOS asks whether Chiip may accept incoming connections: click Allow.
Linux
  1. Unzip it, make the file runnable and start it: 
    chmod +x Chiip.x86_64
./Chiip.x86_64
  2. If it doesn't start, run it from a terminal to see why. A missing Vulkan driver (Mesa's mesa-vulkan-drivers, or your graphics card's) is the usual reason.

Next