WordCraft Web

WordCraft Web is a community-maintained Docker image that serves WordCraft, a browser-based word processor written in Rust.

  • Productivity
WordCraft Web is a community-maintained Docker image that serves WordCraft, a browser-based word processor written in Rust. The upstream application works with document formats including DOCX, ODT, RTF, HTML, Markdown, LaTeX, and TXT, and can export PDF. Documents are handled through the browser application and browser file operations; the container only serves the static WebAssembly frontend and does not provide centralized document storage or server-side document processing.

Platform availability

Available on 4 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac
  • Windows
  • Linux
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

79/100 Good

Maintained
82last commit 16 days ago
Popular
8517,387 GitHub stars
Easy to install
654 install platforms, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

GitHub stars
17,387
Open issues
2639
Last commit
2026-11-05
Latest release
v0.15.2
License
Apache-2.0
Activity
rising

Checked 16 days ago - source: GitHub (storytold/wordcraft)

Resources & Compatibility

Requirements not published yet.

Checked 16 days ago - source: Docker Hub image tags and published docs

First-install notes

  • No server-side document storage The container serves only the static WebAssembly frontend: documents are opened, edited and saved in the browser. The container itself provides no document storage and performs no server-side processing. source

Fetched yesterday - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Do web settings such as dark mode persist after reload in the self-hosted build?

No. In the self-hosted web build 0.7.0, settings such as dark mode reset on every reload.

Does the self-hosted container provide centralized document storage or server-side processing?

No. It only serves the static WebAssembly frontend, so documents are handled through the browser application and browser file operations.

Is a native desktop or mobile client required?

No. The editor is served as a browser-based WebAssembly frontend and uses browser file operations.

How is the Web View expected to render?

A reported issue says it may remain formatted like a document, not span the full work area, and render blurry.

Answers sourced from github.com, github.com, github.com

Community

Collected 16 days ago - public community threads