Blazor WASM apps compile to static files — HTML, CSS, JS, and WebAssembly binaries. This makes deployment simple: host on any static file server, CDN, or pair with an ASP.NET Core backend.

Publishing the App

dotnet publish -c Release -o ./publish

Output is in publish/wwwroot — these are the static files to deploy.

Deployment Targets

• Azure Static Web Apps — free tier, built-in CI/CD from GitHub
• Azure App Service — for hosted (server + client) solutions
• IIS — add a web.config to handle client-side routing fallback
• Nginx — configure try_files to serve index.html for all routes
• GitHub Pages / Netlify / Vercel — static hosting with routing workaround

Critical: Routing Fallback

All servers must return index.html for any unknown path. Without this, refreshing on a deep-linked URL returns 404:

# Nginx:
location / {
    try_files $uri $uri/ /index.html;
}

Reduce Download Size

• Enable IL trimming: <PublishTrimmed>true</PublishTrimmed>
• Enable Brotli/Gzip compression on the server

Reference:

Wikipedia: WebAssembly

https://en.wikipedia.org/wiki/WebAssembly