Blazor Render Modes Jun 2026

At its simplest, a render mode determines the component is rendered (Server or Client) and how it is rendered (Static or Interactive).

<h1>Server-side Rendering Example</h1>

Or programmatically:

The component runs on the server, but maintains a real-time SignalR WebSocket connection to the browser. UI events (clicks, typing) are sent to the server, which re-renders the component and sends back the UI diffs. blazor render modes

| Requirement ↓ | Static SSR | Interactive Server | Interactive WASM | Auto | |---------------|------------|--------------------|------------------|------| | SEO-friendly | ✅ Best | ❌ No (requires JS) | ⚠️ Limited | ⚠️ Limited | | Fast initial load | ✅ Best | ✅ Good | ❌ Slow | ✅ Good | | Offline capable | ❌ No | ❌ No | ✅ Yes | ✅ Yes | | Real-time data | ❌ No | ✅ Best | ⚠️ Polling/WebSocket | ✅ Server then client | | Server cost | ✅ Low | ❌ High (per user) | ✅ Low | ⚠️ Medium | | Scalability | ✅ Excellent | ⚠️ Requires SignalR | ✅ Excellent | ⚠️ Requires SignalR | At its simplest, a render mode determines the

By matching the render mode to the component’s job, you can build Blazor apps that load fast, feel responsive, and scale efficiently. | Requirement ↓ | Static SSR | Interactive

In your .razor file: