EOL.Wiki EOL.Wiki
← ← Back to all products

Notepad++

Active
Applications Latest Version: 8.9.1 Latest Release: Jan 26, 2026

Notepad++ is a free source code editor and text editor for Windows supporting multiple programming languages.

Versions

10

Latest Version

8.9.1

Active Support

1

EOL

9

Lifecycle Timeline

Today
8.9
8.9
8.8
8.8
8.7
8.7
8.6
8.6
8.5
8.5
8.4
8.4
8.3
8.3
8.2
8.2
8.1
8.1
7.9
7.9
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
8.9Dec 27, 2025-No8.9.1No
Active
8.8Apr 28, 2025-Dec 27, 20258.8.9No
EOL
8.7Sep 17, 2024-Apr 28, 20258.7.9No
EOL
8.6Nov 23, 2023-Sep 17, 20248.6.9No
EOL
8.5Mar 6, 2023-Nov 23, 20238.5.8No
EOL
8.4Apr 26, 2022-Mar 6, 20238.4.9No
EOL
8.3Feb 3, 2022-Apr 26, 20228.3.3No
EOL
8.2Jan 1, 2022-Feb 3, 20228.2.1No
EOL
8.1Jun 17, 2021-Jan 1, 20228.1.9.3No
EOL
7.9Sep 28, 2020-Jun 17, 20217.9.5No
EOL

Frequently Asked Questions

Which versions of Notepad++ have reached end of life?
The following Notepad++ versions have reached end of life and no longer receive security updates: 8.8, 8.7, 8.6, 8.5, 8.4, 8.3, 8.2, 8.1 (and 1 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Notepad++ 8.8?
Notepad++ 8.8 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Notepad++?
The latest version of Notepad++ is 8.9.1, released in the 8.9 release cycle.
How many versions of Notepad++ are currently supported?
Notepad++ currently has 1 actively supported version(s): 8.9.
When does Notepad++ 8.9 reach end of life?
Notepad++ 8.9 does not have a specific end-of-life date announced yet.
What should I do when Notepad++ reaches end of life?
When a Notepad++ version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.