Inside JitWord: How One Open-Sourced .doc Converter Proves Enterprise Online Word Is a Hard, Real Problem
The open-sourcing of doc2docx makes the hardest part of legacy .doc migration inspectable and reusable, which matters to anyone handling decades of Word archives. JitWord's 公文 engine and OFD support also demonstrate that document collaboration must accommodate regional regulations, not just generic editing.
JitWord targets the gap between Notion-style editors and desktop Word by reimplementing Word's formatting system in the browser: multi-level numbering, complex tables, section breaks, embedded OLE objects, native flowcharts, and comment/revision round-tripping all survive import and export. A CRDT-based sync layer allows multiple users to edit without losing text, and an optional per-section page setting handles formal documents. The project also ships a 公文 (official document) engine, OFD support, a template system with fillable variables, and a batch generation API that turns a JSON payload into hundreds of documents.
The company open-sources its hardest part: doc2docx, a Node.js library (BSD) that converts legacy binary .doc files, so enterprises can audit and extend it. Deployment is private and containerized, with source-level delivery, API/SDK integration, and a unified AI layer supporting DeepSeek, Kimi, Qwen, GLM, Doubao, MiniMax, and custom private models. Pricing sits at roughly ¥30k for a permanent enterprise co-build license, compared to per-seat annual SaaS costs. Trade-offs are limited brand reach, a steeper learning curve, and rendering pressure on extremely large documents, but JitWord is a rare attempt to combine Word fidelity, collaboration, and data control in one product.
Open-sourcing doc2docx is a trust play: enterprises that deploy privately want to verify the parser handling their legacy .doc files, and the BSD license lowers the barrier for adoption and auditing.
The 公文 engine is a moat that Western document tools ignore; by modeling Chinese official document standards, JitWord addresses a regulatory niche that requires local domain knowledge to replicate.
Selling source code and SDK alongside SaaS pushes the business ceiling above a typical subscription model, but it also shifts the burden to support and customization for each buyer.
The emphasis on format fidelity over feature breadth suggests the real cost in enterprise document migration is not collaboration but faithful conversion, which most web editors underinvest in.