Long-form writing
Draft and revise structured documents in a focused word-processing workspace.
In development · MIT or Apache-2.0 · v0.7.0
WordCraft is an open-source word-processing project in the Craft Apps family. It is a useful page to read when you are looking for a free Word alternative, but it is not an automatic Microsoft Word replacement: the project is still in development, the browser build is a local WebAssembly editor, and DOCX compatibility needs to be checked with the documents you actually use. This guide explains what the project is, how the browser and release paths differ, what to test before a Windows install, and where the honest limits are.
Try the browser editor Try WordCraft in your browser Read the source
| Platform | Architectures | Build formats | Where work runs |
|---|---|---|---|
| Browser (WebAssembly) | modern browser | wordcraft-web-0.7.0.zip | Browser build; confirm the current hosting and file boundary upstream |
Draft and revise structured documents in a focused word-processing workspace.
Use a representative document to test headings, tables, images, fonts and export behavior before relying on a browser round trip.
The browser build is an editor running on the visitor device, not a hosted document store operated by OpenCraftTools.
The repository and release history stay available so a team can inspect the project and pin the build it tested.
This is an upstream preview of WordCraft. It helps you recognise the workflow, but it is not a promise that every panel, model or file format is unchanged in v0.7.0. Use the release and source links above for the version-specific truth.
Browser experience
Target workflow: writing, text editing and DOCX checks. The editor opens in the upstream application; This portal does not upload, proxy or retain your files.
WordCraft is the document-writing member of a wider open-source Craft lineup that also includes spreadsheet, presentation, image, vector and audio projects. Its natural job is structured writing: headings, paragraphs, lists, tables, images and the ordinary revisions that make a document useful after the first draft. The project has its own source repository and release trail, so you can inspect the implementation and pin a version instead of treating a marketing page as the product.
The phrase “Word alternative” needs a boundary. Microsoft Word includes years of compatibility work, add-ins, collaboration paths, accessibility tooling, mail merge, review features and a large ecosystem. WordCraft does not claim to reproduce that surface. It is better understood as a free open-source project worth testing when you value inspectable source, a focused writing workflow or a browser-first canary and can keep a mature office application available for files that matter.
The online page is an explicit browser entry, not a cloud account provided by OpenCraftTools. The official WebAssembly package runs in the browser session, and this portal does not receive, upload or recover your document. That makes it convenient for an early test, but it also makes the browser the boundary: memory, fonts, clipboard permissions, local persistence and export behavior depend on the device and browser. Save or export before closing the tab, and do not assume a refresh is a recovery strategy.
A desktop release can have a different file path, keyboard integration and operating-system behavior from the browser build. If you are evaluating WordCraft for a Windows workflow, start with the upstream release page and a disposable document. Compare the browser export and desktop export rather than assuming that a shared project name means identical support. The test is small by design: one document, one export, one reopen, and one comparison against the original.
A file opening is not the same as a file surviving a round trip. Use a copy containing a heading hierarchy, a table with wrapped text, an image with a caption, a page break, a list and at least one font that is installed on the target computer. Open it, inspect the layout, make one harmless edit, export or save, reopen the result in the office software your team normally uses, and compare the pages. If a comment, field, embedded object or tracked change matters, make that a separate acceptance test rather than inferring support from a simple paragraph.
| Area | Use in the sample | What to check |
|---|---|---|
| Structure | Headings, lists and a page break | Outline order, numbering and page flow remain understandable |
| Layout | A table, image and caption | Wrapping, anchors, spacing and export placement |
| Typography | One available and one missing font | Substitution, line breaks and text overflow |
| Delivery | Export, close and reopen | The receiving application shows the same content and usable layout |
Use the upstream GitHub repository and release page for the exact WordCraft asset. OpenCraftTools links the source and release but does not mirror or repackage installers. Before running a download, confirm the repository, release tag, architecture and any published checksum information. A checksum can show that the file matches what the publisher released; it cannot show that an early-stage editor supports every document your organisation owns. Keep the release tag with your sample file so a later comparison is reproducible.
Do not make a client contract or the only copy of a manuscript your first test. Use a representative sample with the structures you need.
Open WordCraft online, check fonts and editing behavior, then save or export before closing the tab.
If you need Windows installation, use the upstream release and record the exact tag, asset and operating system.
Compare the result in the office software used for delivery and record any layout or feature gap before switching.
The useful privacy claim here is narrow: the OpenCraftTools browser page does not provide an account, upload endpoint or server-side document store. That does not make every browser environment safe for confidential work; the browser, device, extensions and upstream editor remain part of the risk boundary. For sensitive documents, use a redacted copy until you have reviewed the exact build and local file behavior. Download only from the official project repository or release path linked on this page, and be cautious with third-party packages that add an unrelated installer or wrapper.
WordCraft is a sensible canary for people who want to follow an emerging open-source office family, prototype a writing flow, or test whether a lightweight editor is enough for a particular document. It is not the right moment to remove the only mature office application from a production workflow. Keep a known-good fallback for documents with complex fields, macros, tracked changes, embedded objects, accessibility requirements or a delivery deadline. The strongest result is not a feature checklist; it is a saved test file that another person can reopen and inspect.
WordCraft is an open-source word-processing project in the Craft Apps family. It is in development, so use it as a testable alternative rather than a blanket replacement for Microsoft Word.
It is presented here as a free, open-source project, with its licence and release links shown from upstream. “Alternative” does not mean feature or file compatibility parity; test your real documents first.
Use a copy of a representative DOCX and verify headings, tables, images, fonts and export in the current build. A simple file opening does not prove that every DOCX feature round-trips.
Download from the official repository or release page, verify the exact asset and any published checksum, and keep a mature fallback until the early-stage build passes your own document test.
No account, upload or server-side recovery service is provided by this portal. The browser editor runs in your session; save or export before closing and still use caution with confidential files.