---
title: Install
description: Install the tide command on Windows, Linux or macOS, with built-in
  clang for native and web games, and learn how to update it.
source_url: https://tide-engine.dev/guide/install
source_file: docs/guide/install.md
source_revision: 36904d8e07dd044bd665de823e6b8022ed4f4248
source_worktree: modified
documentation_sha256: ea38a553efadfaf8a016c33e947825b8c4d3d2005abcf32eb4f4a64094909e97
documentation_scope: Website source checkout; not matched to an installed Tide
  release. Check tide version and the project toolchain.
---

<a id="install"></a>

# Install

Tide comes as one command, `tide`, which builds and runs games. It has its C compiler built in (clang), for native and web games alike.

<a id="windows"></a>

## Windows

In PowerShell:

```powershell
Invoke-RestMethod https://tide-engine.dev/install.ps1 | Invoke-Expression
```

Windows needs nothing else: `tide` brings the headers and libraries games build with.

<a id="linux-and-macos"></a>

## Linux and macOS

```sh
curl -fsSL https://tide-engine.dev/install.sh | sh
```

The installer uses `curl`, `tar` and `python3`. Native games also need the system's own headers and libraries:

- **Linux** (x64): your distribution's C development files, which come with gcc: `sudo apt install build-essential` on Debian and Ubuntu, `sudo dnf install gcc` on Fedora. Playing in [rooms](https://tide-engine.dev/multiplayer/matches.md#rooms) needs OpenSSL's `libssl` too, which nearly every distribution has, and so do the players of your game.
- **macOS** (Apple Silicon): Apple's command-line tools, `xcode-select --install`. Install them before tide: they bring the `python3` the installer uses.

<a id="what-the-installer-does"></a>

## What the installer does

It installs `tide` for your user, in `%LOCALAPPDATA%\Tide` on Windows or `~/.tide` elsewhere, and puts its `bin` folder on your `PATH`: the user's `PATH` on Windows, and elsewhere a line in your shell's profiles (`~/.zshrc`, `~/.bashrc`, `~/.profile` and the like, or fish's `conf.d`). It needs no admin rights. Open a new terminal afterwards so the `PATH` change applies, then check it worked:

```sh
tide version
```

This shows tide's version and channel, where it's installed, and which compilers it found.

The installer also adds Tide to VS Code, Cursor, VSCodium and Windsurf when it
finds them, and to existing JetBrains IDE profiles (2024.2+). JetBrains gets
the plugin bundled with your Tide version, including LSP4IJ when missing;
restart the IDE to load it. Open a new JetBrains IDE once before running
`tide editors`. If you run the installer again when `tide` is already there,
it upgrades it instead, on the channel it's on unless you set `TIDE_CHANNEL`,
and adds Tide to editors installed since.

<a id="set-up-your-editor"></a>

## Set up your editor

See [Editor setup](https://tide-engine.dev/tools/editors.md) for VS Code, JetBrains, Emacs, Vim and
Neovim. Tide includes the Emacs and Vim/Neovim modes. Run the command for your
editor, then copy its output into your init file:

```sh
tide ide emacs
tide ide vim
tide ide neovim
```

Prefer your existing package manager? Install the MIT plugins through
[Emacs's built-in package-vc](https://tide-engine.dev/tools/editors.md#emacs) or
[vim-plug/lazy.nvim](https://tide-engine.dev/tools/editors.md#vim-and-neovim). Those instructions link
the official public repositories and explain how to connect to Tide's language
server. The Emacs mode installs directly from GitHub; it is not on MELPA yet.

<a id="nightly-versions"></a>

## Nightly versions

Stable versions come out now and then. Nightly versions are previews published when ready. For a nightly version, set `TIDE_CHANNEL` before running the installer:



```powershell [Windows]
$env:TIDE_CHANNEL = 'nightly'
Invoke-RestMethod https://tide-engine.dev/install.ps1 | Invoke-Expression
```

```sh [Linux and macOS]
curl -fsSL https://tide-engine.dev/install.sh | TIDE_CHANNEL=nightly sh
```



**Tip**
This site follows development, so it describes the nightly version. Some of what it shows may not be in the stable version yet.


<a id="stay-up-to-date"></a>

## Stay up to date

```sh
tide upgrade            # the newest version of your channel
tide upgrade --nightly  # switch to nightly versions
tide upgrade --stable   # back to stable ones
```

`tide` also tells you, at most once a day, when a new version is out. Upgrades check every download against the release's checksums.

`tide upgrade` only ever moves forward. Switching channels, or `tide upgrade --version <v>`, installs what you ask for, even an older version.

An upgrade replaces tide while your editor and your games keep running. When it can't replace a file, because another program is reading it, it stops and says which one. Until it's finished, `tide` builds no games and says the installation isn't whole: close what had the file open and run `tide upgrade` again, which installs the version again even when it's the newest already.

<a id="uninstall"></a>

## Uninstall

Delete the folder tide is in (`tide version` says where), and the line that puts its `bin` folder on your `PATH`: on Windows, in **Edit environment variables for your account**; elsewhere, the lines after `# tide` in your shell's profiles, or fish's `conf.d/tide.fish`. Remove the Tide extension from your editors as you would any other.

If you opted into Windows prefab registration, remove
`HKEY_CURRENT_USER\Software\Classes\Tide.Prefab` and the `Tide.Prefab` value
under `HKEY_CURRENT_USER\Software\Classes\.tprefab\OpenWithProgids` in Registry
Editor. Keep any other applications' values.
