File Viewer developer documentation
Preview private files. Keep every byte in the browser.
Start with a native component, choose renderers, presets, or a Full package, and self-host every runtime asset on your own origin.
Recommended delivery pathBrowser-native
- 01ComponentWeb · Vue · React · Svelte
- 02CapabilityRenderer · Preset · Full
- 03Runtime assetsWorker · WASM · Fonts
Files parse and render locallySame-origin · offline-first · self-hosted
- 266
- registered extensions (224 stable / 42 experimental)
- 45
- preview pipelines
- 100%
- self-hostable runtime
Clear entry points
Choose the path closest to your goal
Recommended path
Integrate in five clear steps
Run the smallest path first, then add only the capabilities your product needs.
- 01Pick the native componentStart with Web Component, or use your framework-native package.
- 02Choose the capability layerUse Full for the complete matrix, or compose presets on demand.
- 03Publish offline assetsKeep Workers, WASM, and fonts on local same-origin paths.
- 04Pass the file and optionsUse a URL or File with one shared options contract.
- 05Verify real formatsTest your PDF, Office, CAD, and archive samples before shipping.
pnpm add @file-viewer/web-full<script type="module">
import '@file-viewer/web-full'
</script>
<flyfish-file-viewer
src="/files/report.pdf"
style="height: 720px"
/>Open the complete integration guideEngineering guarantees
Everything is verifiable before release
No conversion serverAuditable format matrixModular and Full pathsStatic HTML and raw Markdown