Who is novelWriter designed for?
Updated
novelWriter is designed for novelists and writers who manage a large project as many small plain text documents, and who want a simple editor with built-in organisation rather than a rich word processor. It is a good fit if you write in Markdown-like plain text, want comments, synopsis and cross-references between files, and value the robustness of plain text files. It is not positioned as a rich word processor, so if you expect WYSIWYG formatting and layout, it is likely the wrong tool.
The core audience
The project describes itself as "a markdown-like text editor designed for writing novels and larger projects of many smaller plain text documents." That single sentence defines the audience fairly precisely:
- Novelists working on book-length manuscripts.
- Writers of larger projects that are naturally split into many smaller documents — chapters, scenes, notes.
- People who prefer plain text over a proprietary document format.
If your project is a single short document, the multi-file organisation model adds overhead without much benefit.
What kind of writer gets the most out of it
You think in scenes and chapters, not one long file
Because novelWriter is built around "many smaller plain text documents," it suits writers who like to keep each scene or chapter as its own file and navigate between them. The editor is "designed to be a simple text editor that allows for easy organisation of text files and notes."
You want metadata attached to your text
The editor includes "a meta data syntax for comments, synopsis, and cross-referencing between files." This matters if you want to keep planning notes, summaries and links between documents inside the same plain text workflow instead of in a separate app.
You care about file robustness and portability
novelWriter is "built on plain text files for robustness." If you want your manuscript to remain readable and recoverable without depending on one application, that is a direct argument in its favour.
You want free and open source, cross-platform
novelWriter is "Free and Open Source, and runs on Linux, Windows and MacOS." If licence cost or platform lock-in is a deciding factor, it meets those conditions.
Who it is not for
- Writers who want a rich word processor. The description explicitly frames it as "a simple text editor," not a formatting-heavy writing environment. If your process depends on visual layout, styles and print-ready formatting as you write, look elsewhere.
- Writers who want everything in one file. The design assumes many small documents; a single-file workflow fights the model.
- Writers unwilling to work in plain text or Markdown-like syntax. The metadata syntax for comments, synopsis and cross-referencing is part of the value, and it requires learning that syntax.
A quick fit check
| Your working style | novelWriter fit |
|---|---|
| Novel or long project split into many scene/chapter files | Strong |
| Want comments, synopsis and cross-references between files | Strong |
| Prefer plain text for robustness and portability | Strong |
| Need free, open source, Linux/Windows/MacOS | Strong |
| Want a rich word processor with visual formatting | Poor |
| Prefer one single document for the whole manuscript | Poor |
| Don't want to learn a Markdown-like syntax | Poor |
Practical note before you commit
Availability differs by platform. Linux users have several options, including an AppImage, Flatpak, package repositories, and a Cloudsmith-hosted repository. Windows users have a setup installer. On MacOS, DMGs "have been discontinued" as of release 2026.1, and the page states the only current method of running novelWriter on MacOS is to set up a Python environment and install the novelwriter package. If you are on a Mac and want a simple download-and-run install, that is a real friction point to weigh before adopting it.
The current release listed is Version 2026.2 Patch 1, released on September 26, 2026.