File Viewer
file-viewer.app
- Free plan
- Web
- Self-hosted
What File Viewer is
File Viewer is a free, open-source browser component ecosystem for previewing business files without a conversion server. Files are parsed and rendered in the browser, and runtime assets can be served from a customer’s own origin for offline or private deployments. The project lists 274 registered extensions across 47 preview pipelines, including 224 stable and 50 experimental extensions. Viewer options include in-file search, zoom, print, download, HTML export, watermarks, lifecycle hooks, and operation guards. Integration packages are documented for Vanilla JavaScript and Web Components, Vue 2 and 3, React, Svelte, and jQuery. Teams can install individual renderers or choose Lite, Office, Engineering, or Full presets. A browser-reachable file URL needs suitable CORS headers for cross-origin files, while a File object can also be supplied. File Viewer is read-only rather than an editor. Fonts, vendor-specific features, encrypted files, and very large inputs can affect fidelity, memory use, or performance. Its own source and packages use Apache-2.0; optional dependencies keep their own licenses.
Who it suits
File Viewer suits developers building browser-based file previews in web applications. It is useful for self-hosted, private, offline, or framework-specific deployments that need configurable rendering.
Good to know, and what to watch
- Runs parsing and rendering in the browser
- Lists 274 extensions across 47 pipelines
- Supports Vue, React, Svelte, jQuery, and vanilla web
- Offers search, zoom, print, and HTML export
- Runtime assets can stay on the customer’s origin
- It is a viewer, not a professional editor
- Large files can increase memory use and affect performance
- Complex files may not match native-app fidelity
- Cross-origin URLs need appropriate CORS headers
The verdict
File Viewer offers broad, browser-local preview coverage with framework integrations and modular presets. Its read-only design and file-complexity constraints should be considered when native editing or exact fidelity is required.
What the maker publishes
- Commercial offering
- A separate commercial Office engine focuses on Word, Excel, and PowerPoint fidelity, large-file performance, private delivery, and enterprise support. source
- Distribution
- The project is distributed through npm packages, public GitHub repositories, release downloads, and self-hostable runtime assets. source
- Features
- Viewer options include search, zoom, print, download, HTML export, watermarks, lifecycle hooks, and operation guards. source
- Format coverage
- The product site reports 274 registered extensions and 47 preview pipelines, with 224 stable and 50 experimental. source
- Formats
- The maker lists 274 registered file extensions across 47 preview pipelines, with 224 stable and 50 experimental extensions. source
- Frameworks
- Integration packages are listed for Vanilla JS/Web Components, Vue 2 and 3, React, Svelte, and jQuery. source
- Input requirements
- A file URL must be reachable by the browser, and cross-origin files need appropriate CORS headers; a File object can also be supplied. source
- Integrations
- The maker documents integrations for Vanilla JavaScript and Web Components, Vue, React, Svelte, and jQuery. source
- Known constraints
- The project says fonts, vendor-specific features, encrypted files, and very large inputs can affect fidelity or memory use. source
- Large files
- The maker advises validating extreme large files with real samples because file size can affect performance and memory use. source
- License
- The maker says File Viewer-owned source and packages use the Apache-2.0 license; optional external dependencies retain their own licenses. source
- License
- The source is licensed Apache-2.0, while the DWG/DWF/DWFX runtime packages named by the project are AGPL-3.0-only. source
- Limit
- File Viewer is a preview component rather than a professional editor and does not promise native-app fidelity for every complex file. source
- Modular packages
- Teams can install individual renderers or choose Lite, Office, Engineering, or Full presets. source
- Offline deployment
- The documentation says runtime assets can be served from the application's own origin for offline or private deployments. source
- Presets
- Preset bundles cover lightweight text and media, Office documents, engineering formats, or the full published matrix. source
- Product
- File Viewer is a browser-based component ecosystem for previewing business files, with no conversion server. source
- Product
- File Viewer is a read-only, browser-based file preview component for Office, PDF/OFD, CAD, archives, email, and other formats. source
- Read-only
- The project describes File Viewer as a viewer rather than an editor. source
- Rendering
- Files are parsed and rendered in the browser, and runtime assets can be hosted on the customer's own origin for offline deployments. source
- Rendering
- Built-in renderers do not require a conversion server; Workers, WASM, and fonts can be self-hosted. source
- Security and privacy
- The maker describes the product as browser-local and self-hostable, allowing files and runtime assets to stay within the deployment environment. source
- Support
- Community issues and maintenance support do not include delivery commitments; the maker lists priority support and private delivery for commercial customers. source
- Support
- The repository directs users to GitHub Sponsors for maintenance support and enterprise support for private deployments or response commitments. source
Checked against the maker's pages on 2 Oct 2026.