Ofline
Recently, I came across a very interesting JavaScript DOCX editor while searching for alternatives to replace OnlyOffice in one of our projects.
Previously, our company was using OnlyOffice for document editing, but due to licensing and implementation considerations, we needed to move to a different solution.
Our initial direction was to use Meta’s Lexical editor since it is lightweight, open source, and great for rich text editing. However, one major challenge quickly became clear: Lexical is not a true 1:1 representation of the DOCX format.
For simple text editing, Lexical works well. But once you deal with real Word documents containing tables, paragraph spacing, text highlighting, font configurations, bullet points, and more complex formatting, maintaining DOCX fidelity becomes much harder.
That led me to continue searching for alternatives, and I stumbled upon this:
What caught my attention immediately was how well it renders DOCX files directly in the browser while preserving formatting properly. It supports paragraph spacing, text highlighting, font settings, bullet lists, and even table rendering quite well. The documentation is also surprisingly solid, which makes evaluation much easier.
What made it even more interesting is the story behind it.
Apparently, this started as a vibe-coding project using Claude Code with Ralph Loop: Ralph-looping Claude to build a DOCX editor in js from scratch https://j.blaszyk.me/tech-blog/ralph-looping-claude-to-build-docx-editor-in-js/
That was honestly unexpected. Seeing something this technically challenging start from an AI-assisted experimental workflow is fascinating.
Still exploring it, but it is definitely one of the most promising open source DOCX editor projects I have seen recently for web applications that need better DOCX fidelity without relying on heavyweight proprietary solutions.
Previously, our company was using OnlyOffice for document editing, but due to licensing and implementation considerations, we needed to move to a different solution.
Our initial direction was to use Meta’s Lexical editor since it is lightweight, open source, and great for rich text editing. However, one major challenge quickly became clear: Lexical is not a true 1:1 representation of the DOCX format.
For simple text editing, Lexical works well. But once you deal with real Word documents containing tables, paragraph spacing, text highlighting, font configurations, bullet points, and more complex formatting, maintaining DOCX fidelity becomes much harder.
That led me to continue searching for alternatives, and I stumbled upon this:
What caught my attention immediately was how well it renders DOCX files directly in the browser while preserving formatting properly. It supports paragraph spacing, text highlighting, font settings, bullet lists, and even table rendering quite well. The documentation is also surprisingly solid, which makes evaluation much easier.
What made it even more interesting is the story behind it.
Apparently, this started as a vibe-coding project using Claude Code with Ralph Loop: Ralph-looping Claude to build a DOCX editor in js from scratch https://j.blaszyk.me/tech-blog/ralph-looping-claude-to-build-docx-editor-in-js/
That was honestly unexpected. Seeing something this technically challenging start from an AI-assisted experimental workflow is fascinating.
Still exploring it, but it is definitely one of the most promising open source DOCX editor projects I have seen recently for web applications that need better DOCX fidelity without relying on heavyweight proprietary solutions.