---
title: ASP.NET integration
description: pagefind-net works well with ASP.NET applications. Build the index at startup (or as a background task) and serve the pagefind/ directory as static files...
url: https://docs-v3-preview.elastic.dev/pagefind-net/getting-started/asp-net
---
# ASP.NET integration
pagefind-net works well with ASP.NET applications. Build the index at startup (or as a background task) and serve the `pagefind/` directory as static files.
## Complete example
```csharp
using Microsoft.AspNetCore.StaticFiles;
using Pagefind.Net;
var builder = WebApplication.CreateBuilder(args);
var app = builder.Build();
// Build the search index into wwwroot/pagefind/
var wwwroot = Path.Combine(app.Environment.ContentRootPath, "wwwroot");
var index = new PagefindIndex(new PagefindIndexOptions { Language = "en" });
foreach (var doc in LoadDocuments())
index.AddRecord(doc);
await index.WriteAsync(wwwroot);
// Register custom MIME types for Pagefind file extensions
var contentTypeProvider = new FileExtensionContentTypeProvider();
contentTypeProvider.Mappings[".pf_meta"] = "application/octet-stream";
contentTypeProvider.Mappings[".pf_index"] = "application/octet-stream";
contentTypeProvider.Mappings[".pf_fragment"] = "application/octet-stream";
contentTypeProvider.Mappings[".pagefind"] = "application/wasm";
app.UseStaticFiles(new StaticFileOptions { ContentTypeProvider = contentTypeProvider });
app.MapFallbackToFile("index.html");
app.Run();
```
## Custom MIME types
ASP.NET's static file middleware does not recognize Pagefind's file extensions by default. Without registering them, the browser receives 404 responses when `pagefind.js` tries to load index chunks.
The required mappings:
| Extension | Content type |
|----------------|----------------------------|
| `.pf_meta` | `application/octet-stream` |
| `.pf_index` | `application/octet-stream` |
| `.pf_fragment` | `application/octet-stream` |
| `.pagefind` | `application/wasm` |
## Frontend runtime
With `Pagefind.Net.Frontend` installed, the MSBuild target automatically copies `pagefind.js` and `wasm.en.pagefind` into `wwwroot/pagefind/` on every build. The project file just needs a package reference:
```xml
```
The `.targets` file shipped in the `build/` and `buildTransitive/` folders of the NuGet package is imported automatically by MSBuild. No manual `` element is needed.
To customise the output directory, set the `PagefindFrontendOutputPath` property:
```xml
wwwroot/pagefind
```
```xml
true
```
## HTML search page
Include a minimal search UI in your `wwwroot/index.html`.
`pagefind.js` is an ES module and must be loaded with `import()`.
```html
Search