The creator of Notepad++, Don Ho, has publicly disavowed a macOS port of the iconic Windows text editor, accusing its developers of borrowing the name, logo, and visual identity without permission. The dispute, which erupted on May 4, 2026, highlights a long-simmering tension in open source: the freedom to fork code versus the obligation to respect trademarks.

The macOS application, which purported to be a native version of Notepad++, allegedly replicated the editor’s distinctive branding—right down to the green lizard mascot and the familiar document icon. Ho’s denunciation centered not on the code itself, which is licensed under the GNU General Public License (GPL) and thus freely forkable, but on the presentation that he says intentionally confused unsuspecting Mac users into believing they were installing an official version of his software.

Open source licensing can be a double-edged sword. The GPL grants anyone the right to modify and redistribute the source code, but it does not grant any rights to a project’s trademarks. The Notepad++ name and logo are registered trademarks owned by Ho. By using them without authorization, the macOS port walked into a legal grey area that open source projects have long wrestled with: code freedom does not equal brand freedom.

A Beloved Tool Without an Official macOS Equivalent

Notepad++ has been a mainstay of Windows power users since its debut in 2003. Lightweight, fast, and extensible via plugins, it supports dozens of programming languages with syntax highlighting and code folding. Over two decades, it has built a loyal following that often installs it as the very first third-party application on a fresh Windows machine.

Yet for all its popularity, Notepad++ has never officially ventured beyond Windows. Its architecture is deeply tied to the Win32 API and the Scintilla editing component, making porting a non-trivial effort. Third parties have attempted in the past to bring Notepad++-like experiences to other platforms—sometimes by forking the source, sometimes by using web technologies—but none achieved the status of an accepted official port.

The macOS port at the center of the May 4 dispute appeared to fill that void. By adopting the Notepad++ name and visual hallmarks, it immediately signaled trust and familiarity to the many developers who switch between Windows and macOS on a daily basis. But Ho’s swift condemnation suggests the port’s creators crossed a line that even permissive open source licenses cannot erase.

The Trademark Trap in Open Source

The situation mirrors other high-profile clashes in the open source world. The VLC media player, for instance, has multiple ports for iOS and Android, but the VideoLAN organization holds strict control over the VLC trademark to prevent malicious clones from masquerading as the real thing. Similarly, the Debian project selectively allows the use of its name only for distributions that pass its quality guidelines.

Why does this matter? When a project relies on its reputation to drive adoption, any software that uses its name can effectively siphon trust. Users who download the unauthorized macOS port expecting the familiar Notepad++ experience might encounter bugs, missing features, or even security vulnerabilities that they wrongly attribute to the official project. In an era where software supply chain attacks are increasingly common, the brand name acts as a first line of defense.

The Notepad++ GPL license explicitly separates code rights from trademark rights. The GPL version 3—which Notepad++ has used since 2007—states that “no covered work shall be deemed part of an effective technological measure” and that rights to the work are distinct from rights to marks used in connection with the work. Even the earlier GPL version 2, while less explicit, does not grant trademark rights.

The Community’s Divided Reaction

As news of Ho’s denunciation spread across developer forums and social media, reactions splintered along predictable lines. Some users applauded the move, arguing that project founders must be able to protect their brand from what they called “parasitic forks.” Others countered that the spirit of open source should allow anyone to build on existing work, and that the macOS port was simply providing a service to users left behind by Notepad++’s Windows-only philosophy.

A common refrain from the pro-fork camp: the GPL guarantees the freedom to run, study, share, and modify the software for any purpose, and that includes creating derivatives that work on different platforms. They point to the success of projects like Audacity, Clementine, and Firefox, where community forks flourished without trademark disputes because the original authors embraced the adaptations.

Yet the Notepad++ case is unique in one crucial respect. The macOS port did not merely borrow the code; it borrowed the entire public-facing identity. The distinction is critical. A fork that renames itself “SuperPad++” and uses a different logo would likely have faced no legal challenges, even if it were a direct port of the Notepad++ codebase. The controversy stems entirely from the decision to trade on an established name and visual brand.

Ho has not yet indicated whether he will pursue legal action, but trademark law generally requires owners to actively defend their marks to avoid dilution. If Ho allows an unauthorized use to go unchallenged, he could weaken his ability to stop future, more malicious copies. On the other hand, litigation is expensive and time-consuming, and the open source community often frowns on heavy-handed legal tactics.

For the macOS port’s developers, the path forward is clear: rebrand. By replacing the Notepad++ name, logo, and any other trademarked elements, they can continue distributing their fork in full compliance with the GPL. Many popular ports have taken this route. The Qt-based “Notepadqq” editor, for example, carries a similar name but a distinct brand and has never been challenged by Notepad++.

The saga also serves as a cautionary tale for end users. Just because software carries a familiar name does not guarantee it comes from the original developer. Checking the website’s domain, verifying the source on official platforms like GitHub, and looking for a clear statement of endorsement from the project creator are all essential habits in 2026’s fractured software distribution landscape.

The Bigger Picture: FOSS Governance in a Multiplatform World

The Notepad++ trademark row is a symptom of a broader evolution in free and open source software (FOSS) governance. As more projects originate on one platform but see demand on others, the gap between license-granted freedoms and brand-protected identities widens. Projects that neglect to register trademarks early often find themselves scrambling to reclaim their name when a fork gains traction.

Some communities have turned to explicit trademark policies to avoid these situations. The Apache Foundation, the Linux Foundation, and the Eclipse Foundation all maintain clear guidelines on how their projects’ names may be used. Notepad++ does not appear to have published a formal trademark policy, which may have contributed to the misunderstanding.

This incident could prompt Ho to consider releasing such a policy, clarifying what constitutes acceptable use of the Notepad++ mark. It might also encourage the creation of an official community process for vetting ports—similar to how the Signal app endorses third-party clients after security audits.

What Comes Next for Notepad++ Users?

For the millions of Notepad++ users, the immediate takeaway is unchanged: if you are on Windows, download the editor only from notepad-plus-plus.org. If you are on macOS, as of May 2026 there is no official Notepad++ client, and any app claiming that title should be viewed with skepticism.

The silver lining is that the GPL ensures the underlying code remains open for anyone to study, improve, and legally port—provided they respect the brand. So a legitimate macOS Notepad++ derivative could still emerge, perhaps under a name like “NppMac” or “MonoPad.” But as of now, that derivative does not carry the creator’s blessing, and the confused messaging has left a stain on a project that otherwise stands as a paragon of open source success.

Ultimately, the May 4 denunciation is not an attack on forking but a defense of identity. In a digital ecosystem where trust is both fragile and valuable, the line between borrowing code and borrowing a reputation must remain bright.