NotepadNext: a Qt6 reimplementation of Notepad++ for Windows, Linux and macOS

What NotepadNext solves, and who it is actually for

Notepad++ is a Windows application. People who move to macOS or Linux and depend on its editing model, the tab-per-file workflow, the session that survives a restart, the find-and-replace across open documents, have historically had to choose between running it under Wine or switching to something else. NotepadNext is a reimplementation of that editor on Qt, built so the same application runs on Windows, Linux and macOS. The repository describes it as "A cross-platform, reimplementation of Notepad++".

The audience is narrow but real: developers and writers who treat a text editor as a tool rather than an IDE, who want Notepad++ behaviour without a Windows VM, and who are willing to run software the author himself flags as incomplete. The README is unusually direct about this. It says the application is "stable and usable" but "should not be considered safe for critically important work", and adds that there are "numerous bugs and half working implementations". That sentence should drive the adoption decision more than any feature list. If losing a buffer matters to you, this is not the editor to trust with it yet.

How the Qt6 rewrite is structured

The stack is C++ with Qt 6.5 as the supported Qt version, according to the README; older Qt releases are described as likely to work but untested, and fixes for them are accepted only if they stay simple. The build system is CMake, driven from the top-level CMakeLists.txt, and the README points at Qt Creator with the Microsoft Visual C++ compiler as the development setup the maintainer uses.

The repository layout reflects a desktop application rather than a library: src/ holds the application code, thirdparty/ holds bundled dependencies, i18n/ holds translation sources, deploy/ and installer/ hold packaging material, and updates.json sits at the top level for the update mechanism the Windows installer wires up. Translations are managed on Crowdin through crowdin.yml rather than as pull requests against the source tree, which keeps locale churn out of the code history. The practical consequence for anyone building from source is that you are compiling a Qt desktop application, not linking a library, so you need a full Qt 6.5 toolchain and a compiler before CMakeLists.txt is useful to you. The README notes that a detailed guide exists at doc/Building.md for people new to that workflow.

Installing NotepadNext on Windows, Linux and macOS

The README lists the supported distribution channels per platform and warns that other downloads are made by third parties and will likely not receive support. On Windows, packages come from the release page as an installer or a stand-alone zip, and the installer adds an auto-updater and Windows context menu integration. Winget is the shortest path:

winget install dail8859.NotepadNext

After it finishes, NotepadNext appears in the Start menu, and the context menu entries are installed alongside it.

On Linux there are two supported routes. The stand-alone AppImage is downloaded from the release page; the flatpak comes from Flathub:

flatpak install flathub com.github.dail8859.NotepadNext

The flatpak installs under the application ID com.github.dail8859.NotepadNext and can be launched from your desktop environment's application menu. Ubuntu users who prefer a deb package have a third-party PPA maintained by Quentin Lienhardt, supporting Ubuntu 22.04 and newer:

sudo add-apt-repository ppa:quentiumyt/notepadnext
sudo apt update
sudo apt install notepadnext

That PPA is not run by the project, so treat it as a separate supply chain.

On macOS, disk images come from the release page, or Homebrew can do the work:

brew tap dail8859/notepadnext
brew install notepadnext

If macOS reports the application as damaged, the README attributes this to Gatekeeper and gives the fix directly:

xattr -d com.apple.quarantine /Applications/NotepadNext.app

That command strips the quarantine attribute from the installed bundle. It works, but it is also the point where you are overriding an OS security check, so confirm the disk image came from the project's release page before running it. First real use is unremarkable by design: open the application, drag files into the tab bar or use the file menu, and edit. There is no project file, no workspace concept, and no configuration step before you can type.

The macOS font smoothing problem and other platform gaps

The README documents a macOS-specific divergence: the system enables font smoothing by default, which makes text render noticeably differently from the Windows build. The suggested remedy is a system-wide setting:

defaults -currentHost write -g AppleFontSmoothing -int 0

A restart is required for it to take effect. Notice what this means: matching the Windows appearance requires changing a global macOS preference that affects every application on the machine, not a setting inside NotepadNext. That is a real cost, and it is the kind of detail that separates a native cross-platform application from a port that happens to compile everywhere.

The broader limitation is stated by the project itself. "Numerous bugs and half working implementations" is not marketing hedging; it is a description of the current state, and the README invites pull requests on that basis. For an editor, the failure mode that matters is data loss during save or session restore, and the README explicitly declines to guarantee safety for critically important work. Treat any buffer you have not written to disk as at risk. This is also the wrong tool if your workflow depends on the Notepad++ plugin ecosystem. The README does not claim plugin compatibility, and a reimplementation on a different toolkit cannot load binaries built against Notepad++'s plugin API.

NotepadNext versus Notepadqq and other Linux editors

The closest comparison is Notepadqq, which also set out to bring a Notepad++-like editor to Linux, but it was built on Qt 5 and targeted Linux specifically. NotepadNext targets Qt 6.5 and ships packages for Windows, Linux and macOS, so the same application follows you across all three. If your reason for looking at either is that you moved off Windows, that difference decides it: Notepadqq does not give you a macOS build, and it does not give you a Windows build either.

Against a macOS-native editor such as CotEditor, the trade runs the other way. CotEditor is a macOS application, so it inherits native text rendering, native menus and native file handling without the font smoothing workaround quoted above. NotepadNext gives you the same interface on every platform, which is valuable if you switch machines daily and want muscle memory to carry over, and a liability if you only ever use macOS and want the editor to behave like the rest of the system. Against Sublime Text, the difference is packaging and licence rather than editing model: Sublime is a commercial cross-platform editor, while NotepadNext is GPL-3.0 and distributed through winget, flatpak, Homebrew and the release page. There is no feature parity claim to make here; the honest summary is that NotepadNext competes on being free, GPL-licensed, and identical across platforms, and it concedes on stability and plugin depth.

Maintenance, releases and what GPL-3.0 means for distribution

The last push to the default branch was on 2026-09-20, and the most recent tagged release is v0.14 from 2026-04-27, preceded by v0.13 in January 2026 and v0.12 in June 2025. The cadence is measured in months, not weeks, and the gap between v0.12 and v0.13 was roughly seven months. Plan upgrades around tagged releases rather than around the branch. Windows users get an auto-updater through the installer build, which is the only automatic update path the README describes; flatpak, Homebrew, PPA and AppImage users update through their own package manager or by downloading a new artifact. There is no documented rollback procedure, and the README does not describe a downgrade path, so keeping the previous installer or AppImage is the only practical insurance.

The licence is GPL-3.0. For individual use that changes nothing. For redistribution, the copyleft terms attach to the whole work, which matters if you intend to bundle the editor inside a proprietary product or ship a modified build internally without publishing sources. This is not legal advice; read the licence text and, if the answer affects revenue, ask a lawyer. Note also that the Ubuntu PPA is maintained by a third party, so the licence of the upstream code and the trustworthiness of that specific build are two separate questions.

Editorial conclusion

Adopt NotepadNext if you want a Notepad++-style editor on macOS or Linux and you can live with the README's own warning that it should not be considered safe for critically important work. Do not adopt it as the only editor holding unsaved work, and do not expect Notepad++ plugin compatibility. Before committing, check the release page for the current v0.14 assets for your platform, confirm your Qt version if you build from source, and read GPL-3.0 before shipping it inside a commercial product.

Frequently asked questions

Official sources

1. dail8859/NotepadNext on GitHub
2. Issues
3. License: GPL-3.0
4. README
5. Releases