If your job is receiving Word files and returning Word files, use LibreOffice Writer. If your document is yours alone, you want it fast, or you want an AI agent to operate a word processor, WordCraft is the more interesting tool — and it is honest enough to tell you when it will break.
Side by side
| WordCraft | LibreOffice Writer | |
|---|---|---|
| Written in | Rust, rendered with egui | C++, mature codebase |
| Licence | MIT or Apache-2.0 | MPL-2.0 |
| Maturity | alpha — self-rated ~60% | Released for decades; the default free office suite |
| Native .docx | Read and write, with known round-trip gaps for charts and SmartArt | Read and write, with extensive real-world testing |
| Agent automation | MCP server, 422 commands, CLI, JSON control channel | Headless conversion and the UNO API; no MCP |
| Browser build | Yes, via WebAssembly | No |
| Other formats | .doc, .odt, .rtf, .html, .md, .tex, .txt, PDF export | Very broad, including long-tail legacy formats |
| Interface languages | 20+ | 100+, including community translations |
| Printing | Not yet native — listed as a beta prerequisite | Mature |
| Size | A single native binary | A full office suite |
Where WordCraft wins
Startup speed and feel. A Rust binary drawing with the GPU opens in the time a suite needs to resolve its components. If you write all day, that is not a small thing.
Agent operability. WordCraft exposes documents as objects an agent can inspect and mutate — list commands, execute batches, type, select, render a page, save. LibreOffice's UNO API can do much of this, but nobody designed UNO for a language model to discover. This is the clearest real advantage, and the one most likely to matter in two years.
Legibility of the codebase. A small team can read the whole thing. That matters if you want to fix rather than file a bug.
Where LibreOffice wins
Other people's files. This is decisive for most office work. WordCraft's roadmap lists "keeping charts and SmartArt through a round trip" as a beta prerequisite — meaning it is not done. LibreOffice has absorbed years of exactly those bug reports.
Printing, and the unglamorous parts. WordCraft does not yet print natively. If your document ends on paper, that is the whole decision.
Everything else in the suite. Spreadsheet, presentations, drawings, database, formulas — Writer is one sixth of a package you install once.
What neither replaces
If a document has to survive a round trip through your client's Microsoft Word — with track changes, comments and a chart someone will later edit — neither of these is Word. The realistic choice in that situation is Word, or a copy as PDF plus a conversation about who owns the master file.
How to decide in one minute
- Does a document you handle get opened in Microsoft Word afterwards? → LibreOffice Writer, or Word itself.
- Do you need it on paper? → LibreOffice Writer.
- Is the document yours from first word to final export, and do you want it fast? → WordCraft.
- Do you want an AI agent writing into the document? → WordCraft, and nothing else on this list is close.
Frequently asked
Is WordCraft better than LibreOffice Writer?
Not for compatibility. WordCraft is a faster, more modern application with a genuinely novel automation surface, but it is an alpha that grades itself at roughly 60%. For opening and re-saving Word files, LibreOffice is the safer tool.
Can WordCraft replace Microsoft Word?
Not yet. By the project's own estimate it is about 60% of the way there, with charts, SmartArt, pagination fidelity, printing and stability still ahead of beta.
Is WordCraft free?
Yes — dual-licensed MIT or Apache-2.0, with signed installers and a browser build.
Sources: WordCraft repository (README, ROADMAP.md); LibreOffice project documentation. Read 18 October 2026.