Install .NET on macOS

• Install on Windows
• Install on macOS
• Install on Linux

This article teaches you about which versions of .NET are supported on macOS, how to install .NET, and what the difference is between the SDK and runtime.

The latest version of .NET is 8.

Download .NET

Supported versions

The following table lists the supported .NET releases, and which macOS they're supported on. These versions remain supported until either the version of .NET reaches end-of-support or the version of macOS is no longer supported.

macOS Version	.NET
macOS 15 "Sequoia"	8.0, 6.0
macOS 14 "Sonoma"	8.0, 6.0
macOS 13 "Ventura"	8.0, 6.0

The following versions of .NET are ❌ no longer supported:

• .NET 7
• .NET 5
• .NET Core 3.1
• .NET Core 3.0
• .NET Core 2.2
• .NET Core 2.1
• .NET Core 2.0

Runtime or SDK

The runtime is used to run apps created with .NET. When an app author publishes an app, they can include the runtime with their app. If they don't include the runtime, it's up to the user to install the correct runtime.

There are two runtimes you can install on macOS, and both are included with the SDK.

• ASP.NET Core Runtime
  Runs ASP.NET Core apps. Includes the .NET runtime. Not available as an installer.

• .NET Runtime
  This runs normal .NET apps, but not specialized apps, such as apps built on ASP.NET Core.

The SDK is used to build and publish .NET apps and libraries. The latest SDK supports building apps for previous versions of .NET. In normal circumstances, you would only need the latest SDK installed.

Installing the SDK includes both the standard .NET Runtime and the ASP.NET Core Runtime. For example, if you have .NET SDK 8.0 installed, then .NET Runtime 8.0 and ASP.NET Core 8.0 Runtime are both installed. However, any other runtime version wouldn't be installed with the SDK and would require you to install it separately.

Choose how to install .NET

There are different ways to install .NET, and some products might manage their own version of .NET. If you install .NET through software that manages its own version of .NET, it might not be enabled system-wide. Make sure you understand the implications of installing .NET through other software.

If you're unsure which method you should choose after reviewing the lists in the following sections, you probably want to use the .NET Installer package.

Developers

• Visual Studio Code - C# Dev Kit

  Install the C# Dev Kit extension for Visual Studio Code to develop .NET apps. The extension can use an already installed SDK or install one for you.

Users and Developers

• .NET Installer

  Use the standalone installer to install .NET. This method is the typical way to install .NET on your developer or user machine.

• Install .NET with a script

  A bash script that can automate the install of the SDK or Runtime. You can choose which version of .NET to install.

• Install .NET manually

  Use this installation method when you need to install .NET to a specific folder, and run it apart from other copies of .NET.

Install .NET

Installer packages are available for macOS, an easy way of installing .NET.

1. Open a browser and navigate to https://dotnet.microsoft.com/download/dotnet.

2. Select the link to the .NET version you want to install, such as .NET 8.0.

   

   This link brings you to the page with links to download that version of .NET

   If you're going to install the SDK, choose the latest .NET version. The SDK supports building apps for previous versions of .NET.

   Tip

   If you're unsure which version to download, choose the version marked latest.

3. This page presents the download links for the SDK and the Runtime. Here you download the .NET SDK or .NET Runtime.

   

   There are two sections highlighted in the previous image. If you're downloading the SDK, refer to section 1. For the .NET Runtime, refer to section 2.

   • Section 1 (SDK)

     This section is the SDK download area. Under the Installers column for the macOS row, two architectures are listed: Arm64 and x64.

     • If you're running an Apple processor, such as an M1 or an M3 Pro, select Arm64.
     • If you're running an Intel processor, select x64.

   • Section 2 (Runtime)

     This section contains the runtime downloads. Notice that links for the Installers column in the macOS row are empty! This section is empty because the ASP.NET Core Runtime, is only provided in the SDK, or through binary installation.

     Scroll further down to find the standard .NET Runtime for download.

     

     • If you're running an Apple processor, such as an M1 or an M3 Pro, select Arm64.
     • If you're running an Intel processor, select x64.

4. Once the download completes, open it.

5. Follow the steps in the Installer.

   

Install .NET manually

As an alternative to the macOS installers, you can download and manually install the SDK and runtime. Manual installation is usually performed as part automation in a continuous integration scenario. Developers and users usually want to use the installer.

Tip

Use the install-dotnet.sh script to perform these steps automatically.

1. Open a browser and navigate to https://dotnet.microsoft.com/download/dotnet.

2. Select the link to the .NET version you want to install, such as .NET 8.0.

   This link brings you to the page with links to download that version of .NET

   If you're going to install the SDK, choose the latest .NET version. The SDK supports building apps for previous versions of .NET.

   Tip

   If you're unsure which version to download, choose the version marked latest.

   

3. Select the link to the SDK or Runtime you want to install. Look for the Binaries column in the macOS row.

   

   • If you're running an Apple processor, such as an M1 or an M3 Pro, select Arm64.
   • If you're running an Intel processor, select x64.

4. Open a terminal and navigate to where the .NET binary was downloaded.

5. Extract the tarball to where you want to .NET on your system. The following example uses the HOME directory ~/Applications/.dotnet.

   mkdir -p ~/Applications/.dotnet
   tar -xf "dotnet-sdk-9.0.100-rc.2.24474.11-osx-arm64.tar" -C ~/Applications/.dotnet/
   

Test that .NET is working by changing the directory to where .NET was installed, and run the dotnet --info command:

chdir ~/Applications/.dotnet/
./dotnet --info

Install .NET with a script

The dotnet-install scripts are used for automation and unelevated installs of the runtime. You can download the script from https://dot.net/v1/dotnet-install.sh.

The script defaults to installing the latest long term support (LTS) version, which is .NET 8. You can choose a specific release by specifying the channel switch. Include the runtime switch to install a runtime. Otherwise, the script installs the SDK.

Tip

These commands are provided a script snippet at the end of this procedure.

1. Open a terminal.

2. Navigate to a folder where you want to download the script, such as ~/Downloads.

3. If you don't have the wget command, install it with Brew

   brew install wget
   

4. Run the following command to download the script:

   wget https://dot.net/v1/dotnet-install.sh
   

5. Give the script execute permissions

   chmod +x dotnet-install.sh
   

6. Run the script to install .NET.

   The script defaults to installing the latest SDK to the ~/.dotnet directory.

   ./dotnet-install.sh
   

Here are all the commands as a single bash script:

chdir ~/Downloads
brew install wget
wget https://dot.net/v1/dotnet-install.sh
chmod +x dotnet-install.sh
./dotnet-install.sh

Test .NET by navigating to the ~/.dotnet folder and running the dotnet --info command:

chdir ~/.dotnet
./dotnet --info

Important

Some programs might use environment variables to find .NET on your system, and using the dotnet command might not work when opening a new terminal. For help resolving this issue, see Make .NET available system-wide section.

Install .NET for Visual Studio Code

Visual Studio Code is a powerful and lightweight source code editor that runs on your desktop. Visual Studio Code can use the SDK already installed on your system. Additionally, the C# Dev Kit extension will install .NET for you if it's not already installed.

For instructions on installing .NET through Visual Studio Code, see Getting Started with C# in VS Code.

Notarization

Software created for macOS that's distributed with a Developer ID must be notarized, including apps made with .NET.

If you run a non-notarized app, an error window similar to the following image is displayed:

For more information about how enforced-notarization affects .NET (and your .NET apps), see Working with macOS Catalina Notarization.

Validation

After downloading an installer or binary release, verify it to make sure that the file hasn't been changed or corrupted. You can verify the checksum on your computer and then compare it to what was reported on the download website.

When you download the file from an official download page, the checksum for the file is displayed in a text box. Select the Copy button to copy the checksum value to your clipboard.

Use the sha512sum command to print the checksum of the file you've downloaded. For example, the following command reports the checksum of the dotnet-sdk-8.0.100-linux-x64.tar.gz file:

$ sha512sum dotnet-sdk-8.0.100-linux-x64.tar.gz
13905ea20191e70baeba50b0e9bbe5f752a7c34587878ee104744f9fb453bfe439994d38969722bdae7f60ee047d75dda8636f3ab62659450e9cd4024f38b2a5  dotnet-sdk-8.0.100-linux-x64.tar.gz

Compare the checksum with the value provided by the download site.

Important

Even though a Linux file is shown in these examples, this information equally applies to macOS.

Use a checksum file to validate

The .NET release notes contain a link to a checksum file you can use to validate your downloaded file. The following steps describe how to download the checksum file and validate a .NET install binary:

1. The release notes page for .NET 8 on GitHub at https://github.com/dotnet/core/tree/main/release-notes/8.0#releases contains a section named Releases. The table in that section links to the downloads and checksum files for each .NET 8 release:

   

2. Select the link for the version of .NET that you downloaded.

   The previous section used .NET SDK 8.0.100, which is in the .NET 8.0.0 release.

3. In the release page, you can see the .NET Runtime and .NET SDK version, and a link to the checksum file:

   

4. Right-click on the Checksum link, and copy the link to your clipboard.

5. Open a terminal.

6. Use curl -O {link} to download the checksum file.

   Replace the link in the following command with the link you copied.

   curl -O https://dotnetcli.blob.core.windows.net/dotnet/checksums/8.0.0-sha.txt
   

7. With both the checksum file and the .NET release file downloaded to the same directory, use the sha512sum -c {file} --ignore-missing command to validate the downloaded file.

   When validation passes, you see the file printed with the OK status:

   $ sha512sum -c 8.0.0-sha.txt --ignore-missing
   dotnet-sdk-8.0.100-linux-x64.tar.gz: OK
   

   If you see the file marked as FAILED, the file you downloaded isn't valid and shouldn't be used.

   $ sha512sum -c 8.0.0-sha.txt --ignore-missing
   dotnet-sdk-8.0.100-linux-x64.tar.gz: FAILED
   sha512sum: WARNING: 1 computed checksum did NOT match
   sha512sum: 8.0.0-sha.txt: no file was verified
   

Troubleshooting

The following sections are available to help troubleshoot issues:

• Arm-based Macs
• System.Drawing.Common and libgdiplus
• Make .NET available system-wide

Make .NET available system-wide

Sometimes apps on your system, including the terminal, need to find where .NET is installed. The .NET macOS Installer package should automatically configure your system. However, if you used the manual installation method or the .NET install script, you must add the directory where .NET was installed to the PATH variable.

Some apps might look for the DOTNET_ROOT variable when trying to determine where .NET is installed.

There are many different shells available for macOS and each has a different profile. For example:

• Bash Shell: ~/.profile, /etc/profile
• Korn Shell: ~/.kshrc or .profile
• Z Shell: ~/.zshrc or .zprofile

Set the following two environment variables in your shell profile:

• DOTNET_ROOT

  This variable is set to the folder .NET was installed to, such as $HOME/.dotnet:

  export DOTNET_ROOT=$HOME/.dotnet
  

• PATH

  This variable should include both the DOTNET_ROOT folder and the DOTNET_ROOT/tools folder:

  export PATH=$PATH:$DOTNET_ROOT:$DOTNET_ROOT/tools
  

Arm-based Macs

The following sections describe things you should consider when installing .NET on an Arm-based Mac.

.NET Versions

The following table describes which versions of .NET are supported on an Arm-based Mac:

.NET Version	SDK	Runtime	Path conflict
8	Yes	Yes	No
8	Yes	Yes	No
6	Yes	Yes	No
6	Yes	Yes	No

The x64 and Arm64 versions of the .NET SDK exist independently from each other. If a new version is released, each install needs to be upgraded.

Path differences

On an Arm-based Mac, all Arm64 versions of .NET are installed to the normal /usr/local/share/dotnet/ folder. However, when you install the x64 version of .NET SDK, it's installed to the /usr/local/share/dotnet/x64/dotnet/ folder.

Path conflicts

The x64 .NET SDK installs to its own directory, as described in the previous section. This allows the Arm64 and x64 versions of the .NET SDK to exist on the same machine. However, any x64 SDK prior to .NET 6 isn't supported and installs to the same location as the Arm64 version, the /usr/local/share/dotnet/ folder. If you want to install an unsupported x64 SDK, you need to first uninstall the Arm64 version. The opposite is also true, you need to uninstall the unsupported x64 SDK to install the Arm64 version.

Path variables

Environment variables that add .NET to system path, such as the PATH variable, might need to be changed if you have both the x64 and Arm64 versions of the .NET 6 SDK installed. Additionally, some tools rely on the DOTNET_ROOT environment variable, which would also need to be updated to point to the appropriate .NET 6 SDK installation folder.

System.Drawing.Common and libgdiplus

.NET applications that use the System.Drawing.Common assembly require libgdiplus to be installed.

An easy way to obtain libgdiplus is by using the Homebrew ("brew") package manager for macOS. After installing brew, install libgdiplus by running the following commands in the terminal:

brew update
brew install mono-libgdiplus

Related content

• How to check if .NET is already installed.
• Working with macOS Catalina notarization.
• Tutorial: Create a new app with Visual Studio Code.
• Tutorial: Containerize a .NET app.