---
title: "Install | Parity docs"
description: "Install Parity on Windows, macOS or Linux with one line, take a download yourself, or build it from source."
url: https://parity.apps.wayne.edu/docs/install.html
llms: https://parity.apps.wayne.edu/llms.txt
generator: Squire agent-ready
---

# Install [#](https://parity.apps.wayne.edu/docs/install.html#install)

Parity is one program, `parity` (`parity.exe` on Windows). Install it with the line for your computer, then open a new terminal and run `parity check`.

## With one line [#](https://parity.apps.wayne.edu/docs/install.html#with-one-line)

Windows

```powershell
irm https://parity.apps.wayne.edu/install.ps1 | iex
```

macOS

```sh
curl -fsSL https://parity.apps.wayne.edu/install.sh | sh
```

Linux

```sh
curl -fsSL https://parity.apps.wayne.edu/install.sh | sh
```

The installers fetch the newest release, check its sha256 against the release's `checksums.txt` before installing anything, and need no administrator:

- **Windows** puts `parity.exe` in `%LOCALAPPDATA%\Programs\parity` and adds that folder to your own (user) PATH, once. A second run updates `parity.exe` and says it is already on your PATH.
- **macOS and Linux** put `parity` in `~/.local/bin`. The script never edits your shell's profile: if `~/.local/bin` is not on your PATH, it prints the one line to add, and you open a new terminal.

```text
bash or zsh (~/.bashrc or ~/.zshrc):   export PATH="$HOME/.local/bin:$PATH"
fish (~/.config/fish/config.fish):     fish_add_path "$HOME/.local/bin"
```

A folder you name with `--dir` (or `PARITY_INSTALL_DIR`) wins. If you cannot write it (`/usr/local/bin`, say), sudo asks for your password for the copy, and only for the copy.

A version, a folder of your choosing, or no PATH change (`-NoPath` on Windows; `PARITY_NO_PATH=1` on either, which on macOS and Linux drops the hint):

Windows

```powershell
& ([scriptblock]::Create((irm https://parity.apps.wayne.edu/install.ps1))) -Version 0.1.0 -InstallDir C:\tools\parity -NoPath
```

macOS and Linux

```sh
curl -fsSL https://parity.apps.wayne.edu/install.sh | sh -s -- --version 0.1.0 --dir ~/bin
curl -fsSL https://parity.apps.wayne.edu/install.sh | PARITY_NO_PATH=1 sh
```

### What the checksum proves [#](https://parity.apps.wayne.edu/docs/install.html#what-the-checksum-proves)

It catches a corrupted or partial download. It does not prove the download is genuine: `checksums.txt` comes from the same site as the archive, so a site serving a bad archive could serve a matching sum too. Signed binaries come before the desktop app, which follows 1.0.

## A container engine [#](https://parity.apps.wayne.edu/docs/install.html#a-container-engine)

Parity drives a container engine; it does not bring one.

| Computer | Recommended | Also works |
| --- | --- | --- |
| Windows | Podman Desktop (free): `winget install --id RedHat.Podman-Desktop -e` | Docker Desktop, if you already have it |
| macOS | Podman Desktop (free): `brew install --cask podman-desktop` | Docker Desktop, if you already have it |
| Linux | Podman and Docker Compose, from your distribution (`sudo dnf install podman docker-compose` on Fedora and RHEL, `sudo apt-get install podman docker-compose-v2` on Ubuntu), then `systemctl --user enable --now podman.socket` | Docker Engine with its Compose plugin |

With both installed, Parity uses the one that is running; `parity engine podman` (or `docker`) chooses for good ([Troubleshooting](https://parity.apps.wayne.edu/docs/troubleshooting.html#which-engine-and-licenses)). On Windows the engine runs Linux containers on WSL 2. On arm64 (Apple Silicon, Windows on Arm, arm64 Linux) Citadel's amd64 images run emulated; [Troubleshooting](https://parity.apps.wayne.edu/docs/troubleshooting.html#arm64-computers) has the details. `parity check` says what, if anything, your engine still needs.

## Take the file yourself [#](https://parity.apps.wayne.edu/docs/install.html#take-the-file-yourself)

Each archive holds `parity` (`parity.exe` on Windows) with its README, license and changelog. The newest release is always at the same names:

| Computer | x64 (Intel, AMD) | arm64 |
| --- | --- | --- |
| Windows | [parity_windows_amd64.zip](https://parity.apps.wayne.edu/downloads/latest/parity_windows_amd64.zip) | [parity_windows_arm64.zip](https://parity.apps.wayne.edu/downloads/latest/parity_windows_arm64.zip) |
| macOS | [parity_darwin_amd64.tar.gz](https://parity.apps.wayne.edu/downloads/latest/parity_darwin_amd64.tar.gz) | [parity_darwin_arm64.tar.gz](https://parity.apps.wayne.edu/downloads/latest/parity_darwin_arm64.tar.gz) |
| Linux | [parity_linux_amd64.tar.gz](https://parity.apps.wayne.edu/downloads/latest/parity_linux_amd64.tar.gz) | [parity_linux_arm64.tar.gz](https://parity.apps.wayne.edu/downloads/latest/parity_linux_arm64.tar.gz) |

Check the file against [checksums.txt](https://parity.apps.wayne.edu/downloads/latest/checksums.txt). Every release also stays at `downloads/<version>/parity_<version>_<os>_<arch>`, with its own `checksums.txt`.

0.1.0 ships unsigned. A zip downloaded in a browser may meet SmartScreen on Windows ("More info", then "Run anyway", or `Unblock-File parity.exe`), and on a Mac an archive downloaded in a browser needs `xattr -d com.apple.quarantine parity`. The installers avoid both. Signed binaries come before the desktop app, which follows 1.0.

## Build it yourself [#](https://parity.apps.wayne.edu/docs/install.html#build-it-yourself)

With Go 1.26 or newer, from a clone of [the repository](https://git.wayne.edu/enterprise-apps/parity):

```text
go build -o parity ./cmd/parity          (parity.exe on Windows)
go run ./tools/build                     all six binaries into dist/, with checksums.txt
```

Or with a container engine only, using the image Parity's CI uses, pinned by digest, with Go's downloads and build cache in a named volume so a second build starts warm (with Podman, write `podman` for `docker`):

```text
docker run --rm -v "${PWD}:/src" -w /src -v parity-go-cache:/go -e GOCACHE=/go/build-cache golang:1.26.11-trixie@sha256:fa340cb59ebeb1d53ac1cccfc334201d938fe5f3458003cccb767096d8e032b8 go run ./tools/build
```

Put the binary for your computer somewhere on your PATH and run `parity version`.

## Update and remove [#](https://parity.apps.wayne.edu/docs/install.html#update-and-remove)

Run the install line again to update. To remove Parity, delete the program (and on Windows, its folder from your PATH). Parity keeps nothing else outside your apps, except downloaded image tars you asked it to keep with `parity image get --keep`, in your user cache folder.
