Install JetBrains Rider on Linux

JetBrains Rider supports Linux, and the installation path changes how you update the IDE. Install it with Snap for a package-managed route, use JetBrains Toolbox when you manage several JetBrains tools, or unpack the official archive when you need control over the install directory.

JetBrains documents the Linux Snap route, while its download and Toolbox pages supply the current desktop distributions. I checked those sources on August 20, 2026 and kept the commands below within their documented scope.

Choose the Rider installation path

Pick the path that matches who owns updates and where the IDE lives. The three routes serve different desktop setups.

Install path	Use it when	Tradeoff
Snap	Your distribution supports Snap and you want a package-managed installation.	It runs with Snap confinement and tracks the selected Snap channel.
Toolbox App	You use more than one JetBrains IDE or want Toolbox to manage IDE updates.	You still need the Toolbox App itself on your desktop.
Manual archive	You need to choose the install location and manage upgrades yourself.	You must replace the archive when you upgrade.

A manual archive is not a package-manager replacement. Choose it when the directory and upgrade procedure need to stay under your control.

Check the Linux desktop first

Rider needs a supported Linux desktop and a .NET SDK for the projects you build. Install the SDK that matches your project separately, then open the solution in Rider.

If you are unsure which package system your distribution uses, start with Linux package management. The install command below requires Snap support, not apt, DNF, or Pacman alone.

Install Rider with Snap

JetBrains and the Rider Snap listing document this stable-channel command. Use the edge channel only when you deliberately want pre-release builds.

sudo snap install rider --classic

Start Rider from the desktop application launcher or run rider from a terminal after the package installation finishes. The retained terminal capture shows the Snap installation command as it appears in the workflow.

Ryder Snap Install — The Rider Snap installation command is the package-managed route.

Use this route when Snap is already part of your distribution. JetBrains and Snapcraft document the command above.

Install Rider with JetBrains Toolbox

Toolbox manages installation and updates for Rider and other JetBrains IDEs, so it fits a desktop that uses more than one JetBrains product.

Download the Linux Toolbox archive from JetBrains Toolbox.
Extract the archive in a directory under your home folder that permits execution.
Run the extracted Toolbox launcher, sign in if your licensing path requires it, then select Rider from the Toolbox catalog.
Let Toolbox install Rider and use its update settings for future IDE releases.

Rider ToolBox App from JetBrains — JetBrains Toolbox presents Rider as one of the IDEs it can manage.

Keep Toolbox when it owns Rider updates. Removing it does not make an existing Rider directory easier to maintain.

Install Rider from the official archive

Download the Linux archive from the Rider download page when you need to control the location, then extract it in a directory you can maintain.

tar -xzf JetBrains.Rider-*.tar.gz
cd JetBrains.Rider-*/bin
./rider.sh

Rider Extracting — Extract the downloaded Rider archive before starting its launcher.

Do not extract an IDE into a directory mounted with noexec. If the launcher is not executable or the ownership is wrong, review chmod and chown and Linux users, groups, and permissions before changing access settings.

Finish the first launch

Rider asks you to accept its terms and choose appearance, keymap, and data-sharing settings on the first launch before you create or open a solution.

Rider Themes — Choose the Rider theme during first-launch setup.

Rider Keymappings — Select a keymap that matches the shortcuts you already use.

Rider Plugins — Review plugins after the IDE opens, not before the base installation succeeds.

Rider License — The licensing screen appears during initial setup when your selected Rider edition requires it.

Rider New Project Config — Create a project only after Rider has completed its first-launch configuration.

Rider .net Project — A .NET project opens after you select its template and SDK settings.

Rider Adding Files — Add project files from Rider after the solution opens.

Use the Linux command line if you need to confirm the directory where you unpacked a manual archive. The Linux file system explains the tradeoff between a home-directory install and a shared system location.

Verify the installation

Open or create a .NET solution, then confirm that Rider finds the SDK your project expects. Build and run actions depend on the toolchain configured for that project.

Launch Rider from the route you installed.
Open a solution or create a small .NET project.
Check the configured SDK in the project settings before you add packages or run a build.
Use the same installation route for updates, especially when Toolbox or Snap owns the IDE.

FAQ

Does Rider run on Linux?

Yes. JetBrains provides Linux distributions for Rider, and its Linux installation documentation includes the Snap installation path.

Which Rider installation method should you use on Linux?

Use Snap for a package-managed installation, Toolbox when it should manage several JetBrains IDEs, and the official archive when you need to choose and maintain the install directory yourself.

Do you need the .NET SDK before installing Rider?

You can install and launch Rider first, but a .NET project still needs a compatible SDK before you can build or run it.

Keep the installer that owns updates. Snap, Toolbox, and a manual archive each solve the installation step, but mixing their update paths makes the next Rider upgrade harder to reason about.