Deploy a Blazor site
Creating a new Blazor WASM project
There are two types of Blazor projects: Blazor Server applications, which run on the server, and Blazor WASM (WebAssembly), which run in the browser. Since Blazor Server is not static, this guide will use Blazor WASM. Create a new Blazor WASM application by running the following command in your terminal:
$ dotnet new blazorwasm my-blazor-project
Creating the build script
To deploy, Cloudflare Pages will need a way to build the Blazor project. In the project’s directory root, create a
build.sh file. Populate the file with this:
#!/bin/sh curl -sSL https://dot.net/v1/dotnet-install.sh > dotnet-install.sh chmod +x dotnet-install.sh ./dotnet-install.sh -c 6.0 -InstallDir ./dotnet6 ./dotnet6/dotnet --version ./dotnet6/dotnet publish -c Release -o output
Before you continue
Creating a GitHub repository
$ dotnet new gitignore$ git init$ git add -A$ git commit -m "Initial commit"$ git remote add origin https://github.com/yourgithubusername/githubrepo.git$ git branch -M main$ git push -u origin main
Deploying with Cloudflare Pages
Deploy your site to Pages by logging in to the > Account Home > Pages dashboard and selecting Create a project. Select the new GitHub repository that you created and, in the Set up builds and deployments section, provide the following information:
After configuring your site, you can begin your first deploy. You should see Cloudflare Pages installing
dotnet, your project dependencies, and building your site, before deploying it.
After deploying your site, you will receive a unique subdomain for your project on
Every time you commit new code to your Blazor site, Cloudflare Pages will automatically rebuild your project and deploy it. You will also get access to on new pull requests, so you can preview how changes look to your site before deploying them to production.
A file is over the 25 MiB limit
If you receive the error message
Error: Asset "/opt/buildhome/repo/output/wwwroot/_framework/dotnet.wasm" is over the 25MiB limit, you have two options:
- Remove the
*.wasmfiles from the output (
rm output/wwwroot/_framework/*.wasm) and modify your Blazor application to instead.