New to Telerik UI for Blazor? Download free 30-day trial

UI for Blazor in Hybrid Apps

The WebView feature available since .NET 6.0 allows you to embed Blazor components in native MAUI, WPF and WinForms apps.

This article provides details on how to setup the apps to use the Telerik UI for Blazor components.

Explore the Hybrid Blazor Sample Apps - Blazor Web Apps running in WinForms, WPF, and MAUI.

In this article:


Prior to adding the Telerik components, ensure the corresponding technology stack is setup and the basic Hybrid Blazor WebView runs as expected in it.

  1. Install the latest version of .NET 6.0. It requires Visual Studio 2022 Preview for Windows or for Mac.

  2. Install WebView.

  3. Make sure you have the necessary bits to work with WinForms/WPF/MAUI apps. For MAUI installation, follow the instructions in the official documentation.

Add the UI for Blazor components

The process for adding Telerik UI for Blazor in the WinForms/WPF/MAUI app is similar to including the components in a native Blazor app.

1. Get the Telerik UI for Blazor package

To use the UI for Blazor components you need to install the Telerik.UI.for.Blazor package and include its reference in the .csproj file of the app. Read more on where to get the Telerik.UI.for.Blazor package...

2. Add the Telerik client assets

To have the Telerik Blazor components look and behave as expected, you need the Telerik CSS and JavaScript assets. Include the assets inside the <head> of the wwwroot/index.html file.

You may add the Telerik resources as static assets or reference them from a cloud CDN.

3. Include @using statements

You can set the project to recognize all Telerik components without explicit @usingstatements on every .razor file. To achieve this, add the following to your ~/_Imports.razorfile. You can register one or both icon namespaces, depending on the icon type you will be using.


@using Telerik.Blazor
@using Telerik.Blazor.Components
@using Telerik.FontIcons
@using Telerik.SvgIcons

4. Add the TelerikRootComponent

You must add a TelerikRootComponent component as a top-level component in the app to make sure it wraps all the content. At the time of writing, custom layouts are not supported, so you can add it to the:

  • Shared/MainLayout.razor for MAUI apps
  • Main.razor for WPF and WinForms apps

Make sure that the TelerikRootComponent matches the webview viewport. Remove the default margin of the <body> HTML element.

Once custom layouts are supported, you will be able to configure a Telerik layout in the same way as with regular Blazor web apps (check Common Configuration).

5. Register the Telerik Services

The final step is to register the Telerik services. Add the Telerik services in accordance to the practice your native app requires.

For example, in MAUI app, you register services in the MauiProgram.cs:

namespace MyBlazorMauiAppName
    public static class MauiProgram
        public static MauiApp CreateMauiApp()
            var builder = MauiApp.CreateBuilder();
                .ConfigureFonts(fonts =>
                    fonts.AddFont("OpenSans-Regular.ttf", "OpenSansRegular");


            // register the Telerik services



            return builder.Build();

5. Add the UI for Blazor components

Add your desired Telerik Blazor components in the app as in a native Blazor app. Explore the available UI for Blazor components and their features in our live demos.

Run the apps

You can now run the hybrid application. Refer to the following resources for each technology stack:


  • The hybrid MAUI Blazor apps allow using browser developer tools. Learn how to enable and use them...
  • The Blazor web app code cannot make calls to native APIs. This feature is yet to be exposed by the framework. At the moment, you have to write your own calls to services and native app code that you need to explicitly expose.
  • The WebView is not on the list of officially supported browsers by Telerik UI for Blazor. It has its specifics and differences from a standalone browser. The hybrid Blazor app integration should be considered a proof-of-concept for the time being. We will monitor the framework maturity and consider adding the webview to the list of supported environments.

Known issues

In this article