Troubleshoot Hosting Pagefind
Pagefind outputs a static bundle directory to your built site, and no hosting configuration is required.
Compression
Pagefind handles compression of the files in the bundle directly, so no server gzip support is required.
Content Security Policy (CSP)
If you have a strict content security policy enabled on your site, you may encounter issues with the Pagefind WebAssembly — this isn’t specific to Pagefind but is an issue with CSP and WebAssembly.
The most widely-supported solution at the current moment is to ensure your Content Security Policy allows script-src 'wasm-unsafe-eval', which is supported in Chrome, Firefox, Edge, and Safari since 2022.
In the future, hopefully a
wasm-srcattribute / SRI hash validation will be supported in CSP, as proposed in chrome#961485, chrome#945121. Open an issue if this is now the case!
If you have any inline scripts initializing Pagefind you will also need unsafe-inline, but this could also be addressed by moving the Pagefind initialization into one of your existing JavaScript files.
Web Workers
Pagefind runs search in a Web Worker by default. If your Content Security Policy restricts workers, you may need to add worker-src 'self' blob: to your CSP headers. Alternatively, you can disable the Web Worker by passing noWorker: true to your search configuration — see Search API config for details.