Open-source .docx editor library for building document apps
Details
- External ID
- 48228411
- Source
- HN
- Company
- —
- Product
- Open-source .docx editor library for building document apps
- Website domain
- github.com
- Launched
- May 21, 2026
- Cohort
- —
- Upvotes
- 107
- Upvotes percentile
- 0.9168012924071083
- Tags
- —
- Fetched at
- Sept. 7, 2026, 9:26 p.m.
- Updated at
- Sept. 7, 2026, 9:26 p.m.
Description
We are working on an open-source .docx editor library for apps that need to edit Word documents in the browser. We just shipped 1.0.A lot of existing approaches convert .docx into HTML and lose document semantics along the way. Our editor parses OOXML directly and uses its own rendering+layout engine to produce paged documents with html/css. Edits round-trip back to .docx, so you’re always editing the document, not its representation.The core rendering engine is framework agnostic, with React and Vue ui adapters on top.It’s Apache 2.0. Happy to answer questions.
Enrichment
- Theme
- document and PDF utility tools
- Vertical
- Horizontal
- Function
- Dev tools
- Audience
- Developer
- AI stance
- Not AI
- Project type
- Hobby / open-source project
- Normalized one-liner
- docx editor library for developers
- Manually corrected
- False
Could you build this?
No Directly parsing the complex OOXML specification and writing a custom layout and rendering engine from scratch for browser-based .docx editing requires deep systems and graphics/layout engineering. LLMs struggle significantly with massive legacy file specifications and custom rendering engines without relying on existing DOM/canvas rendering abstractions.
What it would actually take: Building an in-browser OOXML editor requires deep understanding of ECMA-376 specifications, a custom page layout engine (handling line breaking, hyphenation, tables, multi-column layouts, and pagination), and a performant canvas or SVG renderer with bidirectional editing state management. The stack typically uses WebAssembly/Rust or TypeScript with optimized spatial indexing for text carets and selections. This demands veteran text-engine and document-standards engineering expertise.
Discussion
17 comments analyzed.
Competitors mentioned: Claude/OpenAI web search for docx libraries, Pandoc for MD extraction, PDF editors (similar product for PDFs)
Concerns raised: Performance degrades significantly with larger documents (~40 pages), Mobile UI elements overlap and unusable on small screens, Word rendering fidelity gaps due to undocumented OOXML quirks
Feature requests: Better support for documents over 50 pages, Improved mobile/small screen experience, Extract Word doc content in agentic workflows with comment preservation
Competitors
Other products that read as similar to this one — 260 launches clear the similarity bar, closest 8 shown.
Attention rank: #22 of 261 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).
Launched 192 days after the earliest competitor.
- Word in Web · hn · 2026-07-21 · 37 upvotes · similarity 0.69
- JavaScript-first, open-source WYSIWYG DOCX editor · hn · 2026-02-09 · 130 upvotes · similarity 0.61
- Extend UI · hn · 2026-06-10 · 252 upvotes · similarity 0.55
- DOM-docx · hn · 2026-07-13 · 158 upvotes · similarity 0.55
- Docx-to-Markdown · hn · 2026-09-16 · 5 upvotes · similarity 0.54
- TinyDOCX · hn · 2025-12-22 · 6 upvotes · similarity 0.52
- Opal Editor, free Obsidian alternative for markdown and site publishing · hn · 2026-01-18 · 36 upvotes · similarity 0.50
- PDF to MD · ph · 2026-09-10 · 1 upvotes · similarity 0.47
Other launches for this product
- No other launches for this product.
Same idea, different domain
Nobody's really built a dev tools tool for Sales yet.