Install Telerik UI for WPF from NuGet Packages
Use Telerik UI for WPF NuGet packages to install, update, and manage Telerik assemblies in your project. This article explains how to configure the Telerik NuGet feed, authenticate correctly, and install the packages that your project needs.
When Visual Studio prompts for Telerik NuGet credentials, enter
api-keyas the user name and your Telerik NuGet API key as the password. This is the recommended authentication method for the Telerik NuGet server.
Before You Start
Before you configure the feed, confirm the following prerequisites:
- You can create and run a standard WPF application in Visual Studio.
- Your Telerik account has an active trial or commercial license for Telerik UI for WPF.
- If you want to use the Telerik NuGet server, you have a Telerik NuGet API key from the API Keys page.
The Telerik packages are available in two main ways:
- From the online Telerik NuGet server.
- As downloaded
.nupkgfiles in a local package source.
This article focuses on the Telerik NuGet server. For broader feed setup guidance, see Use the Telerik NuGet server.
Starting with Q3 2026, Telerik UI for WPF NuGet packages are also available on NuGet.org. If you install packages from NuGet.org, you do not need to authenticate against the Telerik NuGet server.
Step 1: Add the Telerik NuGet Package Source
-
Navigate to the Package Manager Settings menu in Visual Studio.

-
Add a new source in the Package Sources section.

-
In the Source field, enter
https://nuget.telerik.com/v3/index.json, and then select OK.
-
Confirm that the Telerik source appears in the package sources list.
Step 2: Authenticate to the Telerik NuGet Server
When you select the Telerik feed for the first time, Visual Studio prompts you for credentials.
Use the following values:
- User name:
api-key - Password: Your Telerik NuGet API key
Generate the key from the API Keys page in your Telerik account.
If single sign-on (SSO) is enabled for your Telerik account, do not enter your Telerik account email and password in this prompt. Even if you use SSO to sign in to telerik.com, Visual Studio still requires
api-keyas the user name and a Telerik NuGet API key as the password for Telerik NuGet feed access. The account must also have an active trial or commercial license.
Step 3: Install NuGet Packages
The following steps show how to search for and install Telerik packages from the configured source.
-
Select your solution or project and click on the "Manage NuGet Packages" menu.

-
Set the Telerik server as the current package source.
-
Search for the Telerik package that contains the control you want to use.
-
Select the required version and install the package.
Some packages depend on other Telerik assemblies, so NuGet installs those dependencies automatically when needed.

For example, if your project uses RadTabControl, install Telerik.Windows.Controls.Navigation or Telerik.Windows.Controls.Navigation.Xaml, depending on whether the project uses NoXaml or Xaml packages.
Read more about the package list in Available NuGet Packages and the package type differences in Xaml vs. NoXaml.
If You Created an Account but Still Cannot Log In
If you created a Telerik account and Visual Studio still cannot access the feed, check the following:
- Make sure that you are using
api-keyas the user name instead of your Telerik account email. - Make sure that you are using a Telerik NuGet API key as the password instead of your Telerik account password.
- Verify that the Telerik account has an active trial or commercial license for Telerik UI for WPF.
- Generate a new API key from the API Keys page and try again.
- Confirm that the package source URL is exactly
https://nuget.telerik.com/v3/index.json.
If authentication still fails, download the .nupkg files and install them through a local package source.
Verify the Installation
After you install the package:
- Confirm that the Telerik assemblies appear under Dependencies or References.
- Add a Telerik control in XAML.
- Build and run the project.
If the project builds and the Telerik control renders correctly, the NuGet installation is complete.