Wiki.js 3.0 rewrites the wiki platform from scratch and adds multi-site and live collaboration
On November 1, 2026, Wiki.js published version 3.0, a complete rewrite of the backend and frontend that brings multi-site, live collaboration and dynamic content blocks. Migrating from 2.x is not a version bump: it goes through a .wkbackup export and a reinstall, with markdown syntax changes to plan for.
November 1, 2026. Wiki.js ships the stable 3.0 release, a complete rewrite of the backend and frontend. 2.5.317. That is the last release of the 2.x branch, which stayed in place for years while the community grew restless — publicly asking whether “Wiki.js 3 is dead?”. November 1, 2026. Multi-site, live collaboration and content blocks become real. Why it matters: the most-awaited open-source wiki in the self-hosting ecosystem rebuilds on fresh foundations, but migrating from 2.x is a real project, not a Docker tag change.
A rewrite to settle 2.x’s debts
Project lead Nicolas Giard is blunt: 3.0 is “a complete rewrite of both the backend and frontend, to address foundational issues in 2.x.” Those issues were not cosmetic. The 2.x architecture, designed in the monolithic Node.js era, was holding back three features users had demanded for years — multi-site, high availability and real-time collaboration.
As a result, Wiki.js had fallen behind on the very ground where it once excelled: an elegant, self-hosted wiki that is trivial to deploy in Docker. While 2.x stagnated, alternatives such as Outline and BookStack advanced on collaboration and multi-team organization. 3.0 is the answer: rather than patching what existed, the team rebuilt everything.
What changes for editing
The Markdown editor — and its AsciiDoc alternative — now runs on the Monaco engine, the one behind Visual Studio Code. Users gain the syntax highlighting, completion and navigation that 2.x lacked. A brand-new visual editor stores content as markdown behind the scenes, for those who never want to see the markup.
3.0 also introduces new page types: Drawing (shapes and arrows via Excalidraw), Feedback Boards (users submit, upvote and comment on ideas), Blog (posts inside the wiki itself) and Live Notes. All editors, except the boards and the blog, support live collaboration: you see other contributors’ cursors and their edits arrive in real time.
Multi-site: one instance, several wikis
This is the most structural feature. A single Wiki.js instance can now serve multiple wikis, each with its own hostname, theme, storage, login and editors. Everything is scoped per site, except users and groups, which are shared at the instance level.
For a team that previously maintained one instance per service — one for internal docs, one for the client, one for the public knowledge base — this is a major consolidation. Permission management becomes centralized: a group can define rights for one or several sites at once, without multiplying deployments.
Content blocks, the real break
Pages can now embed dynamic content through content blocks: list every page in a folder, show a diagram, an interactive map, an image gallery, an infobox, a PDF viewer, a spoiler box, or include the contents of another page. Wiki.js ships more than 25 built-in blocks, usable across all three editors, and lets you write your own custom blocks.
On top of that come a file manager with a built-in image editor (crop, resize, rotate, redact), the return of Visualize Pages for all users, and a recycle bin that restores deleted pages. On the governance side, approval rules let one group review another group’s edits, and lifecycle rules automatically show a “stale” banner on a page not updated for three months, notifying its owners.
Migration is not an upgrade
This is the point not to underestimate. There is no in-place upgrade from 2.x. Migration is an explicit three-step process:
- Create a
.wkbackuppackage: first upgrade the 2.x install to the latest 2.5.317, then use the “Export for Wiki.js 3.x” tool in the admin area to generate the archive. - Install a fresh 3.x, then run the “Import from Wiki.js 2.x” utility.
- Import the archive and review site and system settings.
The import is idempotent and can be replayed safely, existing items being skipped unless the overwrite option is checked. But some settings are deliberately not imported: module settings (storage, authentication, comments), security settings, the site logo and the hostname — the latter to avoid locking you out by pointing at the old installation.
The markdown syntax also changes on a few specific points, to plan for before the import:
- Admonitions: the 2.x CSS-class syntax is still supported, but you should now use the GitHub syntax (
> [!WARNING]); - Diagrams (katex, kroki, mermaid, plantuml): to be wrapped in their respective content blocks;
- Draw.io: diagrams must be exported to XML from 2.x and reinserted via the dedicated block;
- Inline KaTeX/MathJax: the expression must be wrapped in dollar signs and backticks (
$…$); - Relative links: they now point to the parent folder, matching GitHub;
- Tabs: declared via the tabs block, the old syntax displaying as plain text.
Verdict
Wiki.js 3.0 delivers on a long-deferred promise, and delivers: the rewrite settles the three debts of 2.x — multi-site, collaboration, high availability — and adds a block system that brings the wiki closer to a real documentation platform.
If your Wiki.js 2.x has run unchanged for years for a small group and you do not need multi-site or collaborative editing, there is no rush — 2.5.317 remains maintained and functional, and migration is a real project. If you maintain multiple instances, or you miss collaboration and approval governance, plan the migration now: export the .wkbackup, test the import on a staging 3.x, and rework your legacy-syntax pages before the cutover. The trap is not 3.0 itself — it is treating it as a version bump when it demands a deliberate migration.