Razor Components hosting models

By Daniel Roth

Razor Components is a web framework designed to run client-side in the browser on a WebAssembly-based .NET runtime (Blazor) or server-side in ASP.NET Core (ASP.NET Core Razor Components). Regardless of the hosting model, the app and component models remain the same. This article discusses the available hosting models.

Client-side hosting model


Blazor is an unsupported, experimental web framework that shouldn't be used for production workloads at this time.

The principal hosting model for Blazor is running client-side in the browser. In this model, the Blazor app, its dependencies, and the .NET runtime are downloaded to the browser. The app is executed directly on the browser UI thread. All UI updates and event handling happens within the same process. The app assets can be deployed as static files using whatever web server is preferred (see Host and deploy).

Blazor client-side: The Blazor app runs on a UI thread inside the browser.

To create a Blazor app using the client-side hosting model, use the Blazor or Blazor (ASP.NET Core Hosted) project templates (blazor or blazorhosted template when using the dotnet new command at a command prompt). The included blazor.webassembly.js script handles:

  • Downloading the .NET runtime, the app, and its dependencies.
  • Initialization of the runtime to run the app.

The client-side hosting model offers several benefits. Client-side Blazor:

  • Has no .NET server-side dependency.
  • Has a rich interactive UI.
  • Fully leverages client resources and capabilities.
  • Offloads work from the server to the client.
  • Supports offline scenarios.

There are downsides to client-side hosting. Client-side Blazor:

  • Restricts the app to the capabilities of the browser.
  • Requires capable client hardware and software (for example, WebAssembly support).
  • Has a larger download size and longer app load time.
  • Has less mature .NET runtime and tooling support (for example, limitations in .NET Standard support and debugging).

Visual Studio includes the Blazor (ASP.NET Core hosted) project template for creating a Blazor app that runs on WebAssembly and is hosted on an ASP.NET Core server. The ASP.NET Core app serves the Blazor app to clients but is otherwise a separate process. The client-side Blazor app can interact with the server over the network using Web API calls or SignalR connections.


If a client-side Blazor app is served by an ASP.NET Core app hosted as an IIS sub-app, disable the inherited ASP.NET Core Module handler. Set the app base path in the Blazor app's index.html file to the IIS alias used when configuring the sub-app in IIS.

For more information, see App base path.

Server-side hosting model

In the ASP.NET Core Razor Components server-side hosting model, the app is executed on the server from within an ASP.NET Core app. UI updates, event handling, and JavaScript calls are handled over a SignalR connection.

ASP.NET Core Razor Components server-side: The browser interacts with the app (hosted inside of an ASP.NET Core app) on the server over a SignalR connection.

To create a Razor Components app using the server-side hosting model, use the Blazor (Server-side in ASP.NET Core) template (blazorserver when using dotnet new at a command prompt). An ASP.NET Core app hosts the Razor Components server-side app and sets up the SignalR endpoint where clients connect. The ASP.NET Core app references the app's Startup class to add:

  • Server-side Razor Components services.
  • The app to the request handling pipeline.
public class Startup
    public void ConfigureServices(IServiceCollection services)

        services.AddResponseCompression(options =>
            options.MimeTypes = ResponseCompressionDefaults.MimeTypes.Concat(new[]

    public void Configure(IApplicationBuilder app, IHostingEnvironment env)

        if (env.IsDevelopment())

        // Use component registrations and static files from the app project.

The blazor.server.js script† establishes the client connection. It's the app's responsibility to persist and restore app state as required (for example, in the event of a lost network connection).

The server-side hosting model offers several benefits:

  • Allows you to write your entire app with .NET and C# using the component model.
  • Provides a rich interactive feel and avoids unnecessary page refreshes.
  • Has a significantly smaller app size than a client-side Blazor app and loads much faster.
  • Component logic can take full advantage of server capabilities, including using any .NET Core compatible APIs.
  • Runs on .NET Core on the server, so existing .NET tooling, such as debugging, works as expected.
  • Works with thin clients (for example, browsers that don't support WebAssembly and resource constrained devices).

There are downsides to server-side hosting:

  • Has higher latency: Every user interaction involves a network hop.
  • Offers no offline support: If the client connection fails, the app stops working.
  • Has reduced scalability: The server must manage multiple client connections and handle client state.
  • Requires an ASP.NET Core server to serve the app. Deployment without a server (for example, from a CDN) isn't possible.

†The blazor.server.js script is published to the following path: bin/{Debug|Release}/{TARGET FRAMEWORK}/publish/{APPLICATION NAME}.App/dist/_framework.