When browser-side Office preview stops being good enough #126
wybaby168
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
The open-source File Viewer is great for broad, browser-side preview. But some business files are brutal: old DOC/XLS/PPT files, contracts with complicated layouts, huge spreadsheets, and slides that must keep their pagination. Pretending one renderer is perfect for both cases would be dishonest.
So we are shipping Flyfish Office Preview, a separate commercial Office engine for teams that need stronger Word, Excel, and PowerPoint fidelity, private deployment, source licensing, and integration support.
It can replace the Office rendering path inside a File Viewer integration. The rest of the viewer can stay the same.
Try the live demo with a real, sanitized business file.
The open-source edition stays Apache-2.0 and keeps moving. This is not a paywall around it. It is an honest answer for teams whose release depends on difficult Office files and a clear support path.
I would love blunt feedback: what breaks first in your production documents - layout, fonts, pagination, legacy formats, or file size?
All reactions