---
title: "Discussion on \"Self-Hosting a Browser File Viewer Under a Strict CSP: Workers, WASM, and Assets Without Public CDNs\" | Hashnode"
description: "Discussion on \"Self-Hosting a Browser File Viewer Under a Strict CSP: Workers, WASM, and Assets Without Public CDNs\". A practical deployment model for keeping document files, lazy renderer bundles, Web Workers, WASM modules, and fonts inside your own infrastructure."
url: "https://hashnode.com/posts/self-hosting-a-browser-file-viewer-under-a-strict-csp-workers-wasm-and-assets-without-public-cdns/6a54eaef76cac690b0b428df"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Self-Hosting a Browser File Viewer Under a Strict CSP: Workers, WASM, and Assets Without Public CDNs](https://file-viewer.hashnode.dev/self-hosting-a-browser-file-viewer-under-a-strict-csp-workers-wasm-and-assets-without-public-cdns?utm_source=hashnode&utm_medium=feed)

A practical deployment model for keeping document files, lazy renderer bundles, Web Workers, WASM modules, and fonts inside your own infrastructure.

Jul 13 · 10 min read · file-viewer.hashnode.dev  
Updated Jul 20  
Read the article

-   [#web-development](https://hashnode.com/tag/web-development)
-   [#security](https://hashnode.com/tag/security)
-   [#wasm](https://hashnode.com/tag/wasm)
-   [#self-hosting](https://hashnode.com/tag/self-hosting)
-   [#javascript](https://hashnode.com/tag/javascript)

## Written by

[Yu Wang](https://hashnode.com/@wybaby168)

@wybaby168 · Osaka, Japan

  
[View profile](https://hashnode.com/@wybaby168)

CTO at Flyfish. Building File Viewer in the browser.

I build File Viewer: 206 file extensions, 24 browser-side pipelines, no upload. I write about Workers, WASM, CSP, and the bugs that waste whole days.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
