The official WordCraft downloads are signed and checkable. The Windows files are signed by Learning Machines Inc, and the Mac app by Learning Machines LLC and notarized by Apple. The source code is public. The bigger risk today is to your documents rather than your computer: WordCraft is alpha software, so keep copies of anything important.
This page lists what you can verify yourself, what we checked, and what nobody can promise yet.
Download it only from the official release
WordCraft’s official downloads are on its GitHub releases page, and ArtCraft’s own WordCraft page links there too. Every download link on GetWordCraft goes straight to that page; we don’t host or change any files.
Other websites, this one included, are not run by the WordCraft team. If a site offers its own copy of the installer, get it from the GitHub release instead. The same goes for online versions: WordCraft does publish a web build, but a copy hosted by someone else runs whatever code that site serves.
The signatures we checked
On 16 October 2026 we downloaded the 0.7.0 release and checked these files:
| File | Signed by | Result |
|---|---|---|
| Windows x64 installer (.msi) | Learning Machines Inc, through Azure Trusted Signing, Microsoft’s code-signing service | Signature valid, timestamped 14 October 2026 |
| Mac disk image and the app inside | Apple Developer ID: Learning Machines LLC (team DJ6XS33FX8) |
Notarized by Apple; macOS accepts it |
| Mac command-line tool | Same Developer ID | Notarized; macOS accepts it |
| All three | — | SHA-256 matches SHA256SUMS.txt in the release |
The Windows installer and the Linux packages also list Learning Machines as their publisher. The Linux, FreeBSD and web builds aren’t signed; for those, the checksum is your check. The project’s release notes for maintainers (docs/releasing.md) describe the same arrangement.
To check a file yourself:
- Windows: right-click the .msi, choose Properties → Digital Signatures, and look for Learning Machines Inc.
- Mac: after installing, run
spctl -a -vv /Applications/WordCraft.appin Terminal. It should sayacceptedandsource=Notarized Developer ID. - Any system: compare the file’s SHA-256 with the one in the release. The download page shows the command for each system.
What it does with your files and the network
These points come from WordCraft’s README, its documentation and its packaging files.
- It works offline. The README says spelling, grammar and everything else work offline.
- It doesn’t run Word macros. Macro-enabled documents (.docm) keep their macros when you save, but WordCraft has no VBA, so the macros never run. Its own macro feature only records and replays WordCraft commands.
- The log never contains your text. The log file records errors and the choices the app makes, but not the text of your documents.
- Remote control is off unless you turn it on. Scripts and AI agents can drive the app only if you start it with
--control. Even then it listens only on your own computer (127.0.0.1), and every request needs a random 256-bit key that the app keeps in your settings folder. The separate MCP server for AI agents is a command you start yourself, and it can be limited to the folders you choose (docs/mcp.md). - The Flatpak build is sandboxed. It can read your Documents and Pictures folders and the files you open through the file chooser, and it has no network access.
- The Mac app is not sandboxed. Like most desktop word processors, it opens files by path, from the command line and by drag and drop. It uses Apple’s hardened runtime and requests no exceptions to it.
The documentation doesn’t describe telemetry or update checks either way, so this page doesn’t make claims about them.
How it’s built
WordCraft is written in Rust and developed in the open on GitHub under the MIT or Apache-2.0 licence. Much of the work is done with AI coding agents: of the 100 most recent changes on 16 October 2026, 69 list Claude as a co-author. The repository also contains the rules those agents follow (AGENTS.md). Among them:
- no unsafe Rust code, and no code that can deliberately crash outside tests;
- every crash fix lands with a test that reproduces it;
- data from files and commands is treated as hostile, with checked sizes and limits.
According to the README, the project’s CI checks run about 800 tests. None of this makes the code bug-free, but it is all public, so anyone can review it.
What alpha means for your documents
The developers are open about the gaps (docs/gaps.md). As of 0.7.0:
- They haven’t yet tested .docx support against a collection of real-world files from Word, Google Docs, LibreOffice and Pages. They rank this as the biggest gap.
- Crashes and freezes reported by users are third on the same list.
- Pagination can differ from Word’s, so page counts and line breaks may change.
- They estimate WordCraft is about 60% of the way to replacing Word for real work.
In practice: work on a copy of important documents, keep backups, and check the result in Word or another app before you send a file to someone who uses Word. If WordCraft crashes, report it on GitHub Issues with the log file attached. The log locations are on the Windows, Mac and Linux pages.
Who wrote this page
GetWordCraft is an independent guide to WordCraft, written by the GetWordCraft editors. We aren’t affiliated with ArtCraft or Microsoft. About GetWordCraft explains where our information comes from and how to report a mistake.