QOwnNotes: A Qt Notepad That Keeps Notes as Files You Already Own
QOwnNotes is a plain-text file notepad and todo-list manager with Markdown support and Nextcloud / ownCloud integration.
At a glance
- What is it?
- QOwnNotes is a GPL-2.0 C++ desktop notepad that edits plain Markdown files on disk and syncs them through Nextcloud, ownCloud or any other file sync. The judgement: it is a good fit if your notes already live as files and you want a native editor over them, and a poor fit if you want the app to own your data or to be a collaborative web service.
- Who is it for?
- Adopt QOwnNotes if your notes are already plain Markdown files and you want a native Qt editor that syncs them through Nextcloud, ownCloud, Syncthing or Dropbox without importing anything. Skip it if you need real-time collaborative editing, a browser-first workspace, or a mobile client from the same project, since the README points to third-party Android and iOS apps for that.
- Can I use it commercially?
- Yes, with conditions. GPL-2.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository last received commits 1 day ago.
- What is it written in?
- Mainly C++, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 15, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
The problem QOwnNotes solves is ownership of the note file, not note-taking
Most note applications store your writing in a database with a proprietary schema and expose it through an export function. QOwnNotes inverts that. The README states the notes are stored as plain text markdown files and are synced with Nextcloud's or ownCloud's file sync functionality, and that Syncthing or Dropbox can be used as well. The application is therefore a view and an editor over a directory tree, not a storage engine. That distinction decides who the tool is for. If you already keep notes as .md files and have a sync client running, QOwnNotes can open that folder without an import step; the README says you can use your existing text or markdown files and that there is no need for an import most of the time. If you have no such folder and no sync service, you are adopting a sync stack alongside an editor, and the tool's value proposition is weaker. The intended audience is the person who already runs Nextcloud or ownCloud for other reasons and wants a desktop client that speaks to the same file store, plus anyone who wants local Markdown files and is willing to bring their own transport. It is a desktop application for GNU/Linux, macOS and Windows; the mobile side is explicitly delegated to other projects.
How the file-first model actually works, and where the server app fits
The core loop is simple and visible in the repository description: a Qt/C++ desktop application reads and writes Markdown files in one or more note folders, and a separate sync process (Nextcloud desktop client, ownCloud client, Syncthing, Dropbox) moves those files to a server or between machines. The README lists multiple note folders as a feature, so the mapping is not one directory per installation. QOwnNotes also watches for external changes: the README says external changes of note files are watched and that notes or the note list are reloaded, and that differences between the current note and an externally changed note are shown in a dialog. That matters because a sync client writing into the same folder is a second writer, and the diff dialog is the conflict surface. Two features sit outside the plain-file path. Note versioning and trash restore on the server require the QOwnNotesAPI app, a separate Nextcloud or ownCloud server application linked from the README. Todo lists managed on the web and on mobile require the Tasks backend for Nextcloud or ownCloud. So the architecture has three tiers: the desktop editor, the file sync layer, and optional server-side apps that add capabilities the file protocol alone cannot express. If you skip QOwnNotesAPI, you lose server-side version history and server-side trash; the README notes there are also local trash and system trash modes, which is a partial substitute.
Getting it running: install the desktop app, then decide which server pieces you need
Installation is documented at the project's installation page rather than in the README, which only links to it, so the exact package command depends on your distribution and is not reproduced in the supplied material. What the README does establish is the order of operations. First, install the desktop client on Linux, macOS or Windows. Second, point it at note folders; the README's feature list confirms multiple note folders are supported, and that existing text or markdown files can be used without an import. Third, if you want server-side versioning and trash, install QOwnNotesAPI on your Nextcloud or ownCloud instance from the linked app store entries. Fourth, if you want todo lists that are visible on the web and on mobile, install the Tasks backend from the Nextcloud app store or the ownCloud marketplace. The README does not list configuration keys or file paths for the note folder setting, so treat the in-application settings dialog as the place to look rather than a config file you edit by hand. Optional integrations are installed from inside the application: the README describes a scripting support feature with an online script repository where you can install scripts inside the application. That is the extension mechanism for anything not built in, including the AI features, which the README describes as built-in AI support with script integration for providers like OpenAI and Groq.
The scripting layer is the real extension surface, and the MCP server is the newest part of it
QOwnNotes ships a script repository, and the README says scripts can be installed inside the application. This is how the project avoids putting every integration in the compiled binary. Two items in the feature list depend on it. The AI support for OpenAI and Groq is described as built-in AI support with script integration, which reads as a hook plus scripts rather than a hard-coded provider client. The MCP server is described as built-in and as letting external AI agents search and fetch notes securely. That is an unusual position for a desktop notepad: the application becomes a data source for other tools rather than only a destination for your typing. The practical consequence is that the trust boundary moves. Once an external agent can search and fetch notes, the security question is what that agent is allowed to reach, and the README's phrase about searching and fetching securely is the only claim supplied here; the material does not describe the permission model, the transport, or how the server is enabled. Anyone evaluating this for a work machine should read the MCP documentation before enabling it, because the README alone is not enough to judge the exposure. The same caution applies to the AI provider integrations: sending note content to OpenAI or Groq is a data-egress decision that the local-first framing of the project does not cover.
Where QOwnNotes is the wrong tool
The most obvious limitation is concurrency. QOwnNotes edits files on disk and a separate sync client moves them. Conflict handling is a diff dialog, which is a manual resolution path, not a merge. If two machines edit the same note before sync completes, someone decides which version survives. For a single user with a laptop and a phone this is usually fine. For a shared folder with several writers it is not, and the README offers no collaborative editing feature to compensate. The second limitation is platform scope. The README lists GNU/Linux, macOS and Windows for the desktop application and then points to third-party clients for mobile: Nextcloud Notes for Android, MyOwnNotes for Android with ownCloud, CloudNotes for iOS, and mentions Markor and Notebooks as alternatives. There is no first-party mobile application in the supplied material. If you expect the same project to cover your phone, it does not. The third is the server dependency for the features people most often want. Version history and trash restore are gated behind QOwnNotesAPI, and web and mobile todo management is gated behind the Tasks backend. A user who installs only the desktop client gets a capable Markdown editor over a folder, and nothing more. Finally, the editor is a Qt desktop application; the README frames low resource consumption as a contrast with Electron apps, which is a positioning claim rather than a measured result, and the supplied material contains no benchmark to check it against.
The alternative that shares the most ground, and the one that differs most
The closest comparison is the Nextcloud Notes web application, which the README treats as a companion rather than a rival: the same note files are readable and editable from the Nextcloud web interface and from the Android and iOS clients listed. The difference is the editing surface. Nextcloud Notes runs in a browser or a mobile app and depends on the server being reachable; QOwnNotes runs on the desktop against the local copy of the files and works while offline, with the sync client reconciling later. If your work is mostly at a desk with a local folder, QOwnNotes is the more capable editor, with heading folding, inline image previews, wiki-style links and LanguageTool or Harper checking. If your work is mostly in a browser tab or on a phone, the web application is the shorter path, and installing QOwnNotes adds a second client to keep in step. A second comparison is with a self-contained Markdown editor that has no sync story at all. That kind of tool owns nothing and syncs nothing, so you supply the transport yourself. QOwnNotes differs by shipping the Nextcloud and ownCloud integrations, including the optional server app, as first-class parts of the project. The trade is that the integration is opinionated toward those two servers, even though the README confirms Syncthing and Dropbox work as plain file sync.
Maintenance, releases and the licence you are accepting
The release cadence is fast. The supplied release list shows v26.9.1 on 2026-09-04, v26.9.2 on 2026-09-07, and a continuous build on 2026-09-08, with the last push to the repository on 2026-09-09. A version scheme that moves in year.month.patch steps and produces point releases days apart means frequent small updates. For a desktop application that is mostly a benefit, since fixes arrive quickly, but it also means the version you install will be superseded within days and that any packaging you do yourself needs a repeatable update path. The repository is not archived, so the continuous build is the artifact to watch if you want the newest fixes before a tagged release. The licence is GPL-2.0. That is a copyleft licence, and it governs the application you install and any modified version you distribute; it does not extend to the Markdown files you write with it, which remain yours under whatever terms you choose. If you intend to bundle QOwnNotes inside a product, or to ship a modified build, the GPL-2.0 obligations apply to that distribution and you should read the licence text rather than rely on this summary. Note also that the scripting layer and the optional server apps are separate pieces of software with their own terms, and the README links to them rather than restating their licences.
Editorial conclusion
Adopt QOwnNotes if your notes are already plain Markdown files and you want a native Qt editor that syncs them through Nextcloud, ownCloud, Syncthing or Dropbox without importing anything. Skip it if you need real-time collaborative editing, a browser-first workspace, or a mobile client from the same project, since the README points to third-party Android and iOS apps for that. Before committing, verify three things: that your server has the QOwnNotesAPI app installed if you want note versioning and trash restore, that your Nextcloud or ownCloud Tasks backend is present if you intend to manage todo lists on the web and on mobile, and that the current release line (v26.9.2 as of the supplied release list) behaves correctly against your own sync client.
Community notes