Download and install Cross-platform package managers Cross-platform package managers Manual download Installation location Binary location Cache location Binary location Testing your installation If you see "command not found" If you see "command not found" Building from source Deno is a single binary executable with no external dependencies. It runs on macOS, Linux, and Windows, on both x64 and arm64 architectures. Download and install Jump to heading # deno_install provides convenience scripts to download and install the binary. Using Homebrew : Using MacPorts : NOTE: Deno requires Windows 10 version 1709, or Windows Server 2016 version 1709 and up, due to requiring IsWow64Process2 . Using PowerShell (Windows): Using Chocolatey : The startup time of the Deno command gets affected if it's installed via npm. We recommend the official install script (shell or PowerShell) for better performance. Deno does not publish an official apt repository, and the versions packaged by Linux distributions (such as Debian, Ubuntu, Arch, or the Snap Store) are community maintained and often lag behind the latest release. For the most up-to-date version on any Linux distribution, use the shell installer above (or the manual download ), which always installs the current release. Cross-platform package managers Jump to heading # These version managers work on macOS, Linux, and Windows. You can also build and install from source using Cargo : Manual download Jump to heading # Deno binaries can also be installed manually, by downloading a zip file at github.com/denoland/deno/releases . Each release ships one archive per platform, containing a single executable: Unzip the archive and place the deno executable somewhere on your PATH . You will have to set the executable bit on macOS and Linux. Each asset has a matching .sha256sum file for verifying the download. On Linux a common choice is ~/.local/bin (per-user) or /usr/local/bin (system-wide). For example: Docker Jump to heading # Deno publishes official images to Docker Hub and the GitHub Container Registry , in debian , ubuntu , alpine , distroless , and bin variants. See Deno and Docker for Dockerfiles, multi-stage builds, Docker Compose, and other best practices. Installation location Jump to heading # Binary location Jump to heading # When installed via the shell or PowerShell script, the deno binary is placed in the following default location: Override the install directory by setting the DENO_INSTALL environment variable before running the install script. When installed via a package manager (Homebrew, Scoop, etc.), the binary location is managed by that package manager. Cache location Jump to heading #

Downloaded dependencies and compiled artefacts are stored in Deno's cache directory. It defaults to a platform-specific path: Override it by setting the DENO_DIR environment variable (see Environment variables ). Run deno info to print the directory currently in use. Testing your installation Jump to heading # To test your installation, run deno --version . If this prints the Deno version to the console the installation was successful. Use deno help to see help text documenting Deno's flags and usage. For a guide to every subcommand, see the CLI reference . If you see "command not found" Jump to heading # If deno --version reports command not found , the install directory isn't on your PATH yet. To fix this: Open a new terminal window or restart your shell so the updated PATH is picked up. This is the most common cause — the install script updates your shell rc file, but existing shell sessions don't see the change until they reload. Confirm the install directory is on your PATH . The shell install script defaults to ~/.deno/bin on macOS and Linux; for npm-based installs, run npm config get prefix to find the directory containing the global bin . If you customised the install location, the shell install script's install root can be overridden with the DENO_INSTALL environment variable, in which case the binary lives at $DENO_INSTALL/bin/deno . Updating Jump to heading # To update a previously installed version of Deno, you can run: Or using Homebrew (macOS): Or using Scoop (Windows): Or using Chocolatey (Windows): Or using Winget (Windows): This will fetch the latest release from github.com/denoland/deno/releases , unzip it, and replace your current executable with it. You can also use this utility to install a specific version of Deno: Uninstalling Jump to heading # If you installed Deno using the shell or PowerShell install script, first clear the Deno cache directory ( $DENO_DIR ): Then remove the Deno installation directory: Finally, remove the line that sources Deno's env file from your shell config ( ~/.bashrc , ~/.zshrc , ~/.profile , etc.). The shell install script appends a line like . "$HOME/.deno/env" — delete that line. Fish users should additionally remove ~/.config/fish/conf.d/deno.fish . Then remove the Deno bin directory from your PATH environment variable via System Settings. If you installed Deno via a package manager (Homebrew, Scoop, Chocolatey, etc.), use that package manager's uninstall command instead (e.g. brew uninstall deno , scoop uninstall deno ). Building from source Jump to heading # Information about how to build from source can be found in the Building from source guide. Last updated on July 9, 2026 Download and install Cross-platform package managers Cross-platform package managers Manual download Installation location Binary location Cache location Binary location Testing your installation If you see "command not found" If you see "command not found" Building from source