Free tools Windows power users keep installed
One-click scans. No signup required.
There is no single best LTS JDK for every production application. Choose a specific vendor build by matching its support commitment, licensing terms, platform coverage, and compatibility with your stack; then validate it under your own workload before rollout. As of October 7, 2026, Java 25 is the newest LTS release named on Oracle’s roadmap, but an LTS label alone does not guarantee the same support period or terms across vendors.
Start with the support commitment you need
“LTS” is not a universal support contract. The vendor and distribution determine which builds receive updates, how often updates arrive, when support is scheduled to end, and whether you qualify for commercial assistance. Compare the commitment for the exact JDK you plan to deploy—not just the Java major version.
As an Amazon Associate I earn from qualifying purchases.
| Distribution and version | Published support information | What to verify |
|---|---|---|
| Oracle JDK 17 | Oracle’s April 2, 2026 roadmap lists Premier Support through September 2026 and Extended Support through September 2029. | Oracle describes these dates as examples and directs customers to its Lifetime Support Policy for current information. Entitlement and product-specific exceptions apply. Oracle Java SE Support Roadmap |
| Oracle JDK 21 | Oracle’s roadmap lists Premier Support through September 2028 and Extended Support through September 2031. | Confirm current policy dates and your entitlement with Oracle. Oracle Java SE Support Roadmap |
| Oracle JDK 25 | Oracle’s roadmap lists Premier Support through September 2030 and Extended Support through September 2033. | Confirm current policy dates and your entitlement with Oracle. Oracle Java SE Support Roadmap |
| Microsoft Build of OpenJDK 11 and 17 | Microsoft lists September 2027 as the earliest end-of-support target for each. | These are initial targets Microsoft may extend. Commercial support requires qualifying Azure customers and specified services; the system must use the latest update. Microsoft Build of OpenJDK overview and roadmap |
| Microsoft Build of OpenJDK 21 | Microsoft lists September 2028 as the earliest end-of-support target. | Target may be extended. Quarterly updates are provided, and commercial support eligibility and currency requirements apply. Microsoft Build of OpenJDK overview and roadmap |
| Microsoft Build of OpenJDK 25 | Microsoft lists September 2030 as the earliest end-of-support target. | Target may be extended. Quarterly updates are provided, and commercial support eligibility and currency requirements apply. Microsoft Build of OpenJDK overview and roadmap |
The dates above are vendor-specific statements, not directly interchangeable guarantees. Oracle’s roadmap names Java 8, 11, 17, 21, and 25 as LTS releases and plans a two-year LTS cadence, with Java 29 planned for September 2027. That is Oracle’s roadmap; it does not establish that every vendor uses the same designations or schedule. Oracle Java SE Support Roadmap
For Microsoft Build of OpenJDK, the vendor says updates arrive quarterly and commercial support requires remaining on the latest update. Its commercial support is limited to qualifying Azure customers with active support plans for specified Azure services; users outside that scope can use community issue and discussion channels. Microsoft Build of OpenJDK overview
Check the license for the exact distribution and update
Do not assume that a license follows from the words “Java” or “OpenJDK.” Oracle’s terms vary by JDK version and update period, and those terms apply to Oracle’s distribution rather than every vendor build.
- Oracle JDK 21 and later: Oracle states these releases are under its No-Fee Terms and Conditions (NFTC), which permits commercial and production use subject to the license conditions. Oracle says JDK 21 updates beginning with the October 2026 Critical Patch Update are planned to move to the Oracle Technology Network (OTN) license. Check the actual update’s terms when adopting it. Oracle JDK FAQ and Oracle Java SE Support Roadmap
- Oracle JDK 25: Oracle says updates after September 2028 are planned to move to the OTN license. Confirm the terms that apply to the specific update you deploy. Oracle Java SE Support Roadmap
- Oracle JDK 8, 11, and 17: Oracle lists updates under the OTN license, which is free only for specified users and uses, including personal and development use. Other uses may require an applicable entitlement. Oracle JDK FAQ and Oracle Java SE Support Roadmap
Before standardizing, review the current license for the precise build and update, along with any rights or terms supplied by your cloud provider or software vendor.
Rank #2
Confirm your application stack supports the target major
Compatibility is broader than whether the application compiles. Inventory the framework, libraries, application server, build plugins, native components, and operational agents that will run or participate in building and observing the application. Oracle’s JDK 25 Migration Guide advises checking third-party libraries and tools for versions designed for the target JDK, and specifically calls out Maven, Gradle, and IDE support. It also recommends the javac --release option in relevant compiler workflows. Oracle JDK 25 Migration Guide
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteReview support statements from each important dependency’s maintainer. A runtime may be supported by the JDK vendor while a framework, bytecode tool, application server, security agent, or native library has a different compatibility boundary.
Verify operating system, architecture, and container coverage
Match the vendor’s build matrix to the actual production environment: operating-system version, CPU architecture, container base image, and libc variant. These details can narrow the viable JDK choices even when two distributions target the same Java major.
For example, Microsoft’s published support matrix shows Alpine/musl support differs by major version. Check the current matrix for your chosen Build of OpenJDK release and deployment image rather than extrapolating support from another major. Microsoft Build of OpenJDK overview
Rank #4
Validate the candidate before changing production
Oracle warns in its JDK 25 Migration Guide that an application appearing to run successfully is not a substitute for completing the migration checks and reviewing listed issues. Use a staged evaluation suited to your system; the checks below are a practical checklist, not a claim that a particular application has been tested. Oracle JDK 25 Migration Guide
- Build on the candidate JDK. Update the compiler and build plugins as needed, and use
javac --releasewhere appropriate to make the intended Java API target explicit. - Run automated and integration tests. Include startup and shutdown paths, not only unit tests or a successful compilation.
- Exercise production-relevant behavior. Where applicable, test TLS and cryptography, locale and date formatting, reflection, instrumentation, agents, native libraries, and packaging.
- Test representative operating conditions. Compare behavior, performance, and memory use on representative normal and peak workloads. Results for one workload do not establish performance for another.
- Rehearse deployment and rollback. Verify that the JDK image or installation is reproducible, updates can be applied through your normal process, and the previous runtime can be restored if the rollout fails.
Make the decision against your operating model
Once several candidates meet application and platform requirements, use a decision record that answers these questions:
Best Value
- Which vendor will publish security fixes and builds for this deployment, and what end date or extension terms does it state?
- How frequently are updates released, and can the team stay current with the vendor’s required maintenance level?
- What support channel is actually available under your cloud account, contract, and workload?
- What license and deployment or redistribution conditions apply to the exact build and update?
- Are every production OS, architecture, container base, and libc combination covered?
- Do application dependencies, build tools, agents, and operations tooling support the target major?
- Does the application behave acceptably on the candidate under your representative workload?
Choose the newest LTS that your stack can support and your organization can maintain only if it also meets these checks. If it does not, a currently supported earlier major may be the more defensible short-term baseline, provided its vendor support and licensing fit your deployment. The sources do not establish a universal performance winner or compatibility answer for an individual application.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
