novelwriter.io

novelWriter runs on Linux, Windows, and MacOS, and it is Free and Open Source. The installation method differs by platform: Linux offers the most options (AppImage, Flatpak, package repositories, and a Cloudsmith repo), Windows uses a setup installer, and MacOS currently requires a Python environment with the novelwriter package from PyPi because DMG releases have been discontinued.

The current release is Version 2026.2 Patch 1, released on September 26, 2026. Release notes are published alongside the download.

Linux

Linux has the widest set of installation paths. Choose based on how you prefer to manage updates.

To add the Cloudsmith repository on Debian/Ubuntu-based systems:

curl -sLf \
  'https://dl.cloudsmith.io/public/saga-soft/stable/cfg/setup/bash.deb.sh' \
  | sudo bash
sudo apt update
sudo apt install novelwriter

The Ubuntu PPA can also be used on other Debian-based distributions, but since it is deprecated, the Cloudsmith repository is the better long-term choice. Ubuntu pre-releases are available through the Pre-Release PPA by adding ppa:vkbo/novelwriter-pre.

Windows

Download the setup installer and run it. Code signing on Windows is sponsored by SignPath.io, with the certificate provided by the SignPath Foundation; the Code Signing Policy is published on the site.

MacOS

MacOS DMGs have been discontinued as of release 2026.1, and the site notes that DMG releases are being worked on. Until they return, the only current method of running novelWriter on MacOS is to set up a Python environment and install the novelwriter package. The site points to its "Installing from PyPi" instructions for the details.

Other install options

• Python Package Index: pipx install novelwriter
• Pre-releases and checksum files: available on the Downloads page

What to check before you install

• Confirm you are on the latest release (2026.2 Patch 1) unless you specifically want a pre-release.
• On Linux, prefer the Cloudsmith repository over the deprecated Ubuntu PPA so you keep receiving updates.
• On Fedora, expect a delayed release cycle because the package is maintained by Fedora package managers.
• On MacOS, plan for a Python-based install rather than a DMG.

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

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.

Yes. novelWriter is stated on its own site as Free and Open Source, and it runs on Linux, Windows, and MacOS. The page content provided does not list any price, subscription, or paid tier, so there is nothing to suggest a cost for the software itself. That said, "free" here refers to the license status stated by the project — no pricing details are given, so don't read the absence of a price as a formal confirmation of every distribution channel's terms.

What "Free and Open Source" means here

The description comes directly from the project's homepage, which labels novelWriter as "Free and Open Source." In practice this means:

• No license fee is mentioned anywhere in the provided page content.
• The source is available, and the project distributes builds through multiple channels.
• Development is community- and sponsor-supported rather than sold as a product.

The page does note some sponsorship around distribution: Windows code signing is sponsored by SignPath.io with a certificate from the SignPath Foundation, and free package repository hosting is provided by Cloudsmith. These are infrastructure contributions, not pricing signals.

Platforms and how to install it

novelWriter runs on Linux, Windows, and MacOS. Installation differs by platform, and one important change affects Mac users.

Linux

Several options are listed:

Two caveats from the page:

• The Ubuntu PPA is deprecated and will soon stop receiving updates. The project asks users to migrate to the Cloudsmith repository. The PPA can still be used on other Debian-based distros.
• The Fedora package is maintained by Fedora package managers and follows a delayed release cycle compared to upstream.

Ubuntu pre-releases are available through a separate pre-release PPA (ppa:vkbo/novelwriter-pre).

Windows

Download the Setup Installer from the site and run it. Code signing for Windows builds is sponsored, which is relevant if you care about verifying the installer's publisher.

MacOS

This is the part to pay attention to: as of release 2026.1, MacOS DMGs have been discontinued. The page says the team is working to bring DMG releases back, but for now the only current method of running novelWriter on MacOS is to set up a Python environment and install the novelwriter package — for example via pipx install novelwriter. If you're on a Mac and expect a drag-and-drop app, plan for the Python route instead.

Current release

The latest release listed is Version 2026.2 Patch 1, released September 26, 2026. Release notes are linked from the site.

What this means for you

• If you want a no-cost, open-source writing tool for novels and larger multi-file projects, novelWriter fits that description as stated by the project.
• If you're on Linux, you have the widest choice of install methods; prefer the Cloudsmith repo over the deprecated Ubuntu PPA.
• If you're on Windows, the setup installer is the straightforward path.
• If you're on MacOS, budget extra time for the Python/PyPI installation, since DMGs are currently unavailable.

For anything beyond the license status — such as future pricing, commercial support, or paid hosting — the provided page content doesn't say, so check the project's own site and release notes directly.

novelWriter is a free, open-source plain-text editor built specifically for writing novels and other large projects that span many smaller documents. It stores everything as plain text files and adds a markdown-like syntax for comments, synopses, and cross-references between files, so you get the robustness of plain text with lightweight structure for long-form work. It runs on Linux, Windows, and MacOS. It is a good fit if you want to organize a book-length project into many small files without locking your manuscript into a proprietary format.

What makes it different from a general text editor

Most editors treat a novel as one long document. novelWriter assumes the opposite: a project is a collection of many small plain-text documents plus notes, and the editor is designed around organizing and navigating that collection.

• Plain text as the storage format. Your writing lives in ordinary text files, which keeps the project readable and portable.
• Markdown-like syntax. Formatting is written as text rather than applied through hidden rich-text state.
• Metadata for structure. A dedicated syntax handles comments, synopsis, and cross-referencing between files, so notes and links stay inside the project rather than in a separate app.
• Built for many small documents. The design goal is easy organization of text files and notes rather than one monolithic file.

Who it suits

novelWriter fits writers who are comfortable working in plain text and want their manuscript organized as a set of linked files. If you prefer a word-processor view where the whole book is one scrolling document, or you need heavy layout and print design, a general word processor will likely serve you better. If you value portability, version-control friendliness, and keeping notes and manuscript together, this is the kind of tool built for that.

Platforms and how to get it

novelWriter runs on Linux, Windows, and MacOS. The latest release listed is Version 2026.2 Patch 1, released on September 26, 2026.

Note that as of release 2026.1, MacOS DMGs have been discontinued, and the only current method of running novelWriter on MacOS is to set up a Python environment and install the novelwriter package. The project notes it is working to bring back DMG releases.

Install commands from the project

Add the Linux repo provided by Cloudsmith:

curl -sLf \
  'https://dl.cloudsmith.io/public/saga-soft/stable/cfg/setup/bash.deb.sh' \
  | sudo bash
sudo apt update
sudo apt install novelwriter

Install from the Python Package Index:

pipx install novelwriter

Install on Fedora 41+:

sudo dnf install novelwriter

The Ubuntu PPA is deprecated and will soon stop receiving updates; the project recommends migrating to the Cloudsmith repository. The Fedora package is maintained by Fedora package managers and follows a delayed release cycle. For more download options, including pre-releases and checksum files, see the project's Downloads page.

Licensing

novelWriter is Free and Open Source.

novelWriter uses a markdown-like meta data syntax embedded directly in your plain text files. Comments, synopsis, and cross-references are written as special lines that the editor recognises and indexes, while the underlying files stay readable plain text. This means your notes and structure live alongside the manuscript rather than in a separate database, so the project remains portable and robust.

The meta data syntax

Meta data is written on lines that begin with a % character followed by a keyword. Because these lines are just text, they survive copying, syncing, and version control without corruption. The editor parses them to build an internal index of your project.

A typical meta line looks like this:

%Synopsis: The protagonist discovers the letter.

The keyword after % tells novelWriter what kind of information the line carries. Everything after the colon is the content.

Comments

Comments are notes to yourself that should not appear in the rendered manuscript. They use the % prefix so the editor can distinguish them from prose.

% A quick note about why this scene changed.

You can also use a keyword form for structured comments:

%Comment: Check the timeline here.

Because comments are ordinary text lines, they remain visible if you open the file in any other editor — nothing is hidden in a binary format.

Synopsis

Synopsis lines summarise what a document or scene contains. They are useful for outlining and for navigating a large project of many small files.

%Synopsis: Mara confronts her brother about the inheritance.

The synopsis is stored in the same file as the text it describes. novelWriter can collect these across the project so you can review your structure without opening every document. This is the main mechanism that makes a project of many small plain text documents manageable.

Cross-referencing between files

Cross-references let one document point to another by a tag or identifier rather than by file path. You assign a reference tag to a document, then cite it from elsewhere.

%Tag: mara-letter

Elsewhere, you reference it:

%See: mara-letter

The editor resolves these links through its index, so you can jump between related files. Because the link is stored as text, the reference remains meaningful even outside novelWriter — though only novelWriter will resolve it automatically.

Why plain text matters here

The trade-off is that you must follow the syntax conventions for the editor to recognise your meta data. A mistyped keyword is simply treated as ordinary text, so nothing breaks — but the feature won't activate for that line either.

Practical workflow

1. Write your manuscript as plain text documents, one per scene or chapter.
2. Add a %Synopsis: line at the top of each document to describe its content.
3. Add a %Tag: line to give the document a stable identifier.
4. Use %See: or similar reference lines to link documents together.
5. Use % comment lines for reminders that shouldn't appear in the output.

The expected result is a project where structure, notes, and links are all stored in the same plain text files as the prose, and novelWriter's index lets you navigate that structure without leaving the editor.

Common pitfalls

• Forgetting the % prefix. Without it, the line is treated as manuscript text and will appear in your output.
• Reusing tags. Reference tags should be unique, or cross-references become ambiguous.
• Assuming other tools resolve links. The cross-references are meaningful to novelWriter's index; another editor will show them as plain text.
• Editing meta lines in a word processor. Formatting tools may alter the characters and break parsing — keep meta data in plain text.

novelWriter is Free and Open Source and runs on Linux, Windows and MacOS, so the same plain text project can be opened across platforms.