The next major Oracle Java licensing change is planned for after September 2026. It concerns future updates to Oracle JDK 21—not Java as a programming language, the entire Java ecosystem, or every OpenJDK distribution.
Organizations running Oracle JDK 21 in production will generally have four choices: accept the limits of Oracle’s OTN license, upgrade to Oracle JDK 25, buy Java SE Universal Subscription, or migrate to another OpenJDK distribution. The right decision depends on the exact binary, update, deployment, support requirement, and redistribution model.
As an Amazon Associate I earn from qualifying purchases.
The short answer
Oracle says Oracle JDK 21 updates are planned to remain under its No-Fee Terms and Conditions (NFTC) through September 2026. Later JDK 21 updates are planned to move to the more restrictive Oracle Technology Network License Agreement (OTN). Oracle recommends that users who want to remain under its free Oracle license move to Oracle JDK 25. See Oracle’s JDK 21 release notes.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →This does not mean that Java will stop working, that every Java user must pay Oracle, or that an existing JDK 21 installation will shut down. It means that the license attached to later Oracle JDK 21 updates may impose different restrictions on production, commercial, embedded, and redistribution use.
For finance, procurement, and IT teams, the first task is not buying a subscription. It is identifying which Java distribution and exact update are actually running.
Java, OpenJDK, Oracle OpenJDK, and Oracle JDK are different
“Java” is often used as a catch-all term, but the licensing question applies to a specific implementation and binary:
- Java is the programming language and platform ecosystem.
- OpenJDK is the open-source project and reference implementation.
- Oracle OpenJDK is Oracle’s GPLv2 build with the Classpath Exception.
- Oracle JDK is Oracle’s separately distributed binary, whose license depends on the release and update.
- Java SE Universal Subscription is Oracle’s paid licensing, support, and related-services offering.
Amazon Corretto, Eclipse Temurin, Azul Zulu, BellSoft Liberica, Microsoft Build of OpenJDK, and other distributions are not automatically governed by Oracle JDK licensing. Their own licenses, support terms, and update policies apply. Oracle distinguishes Oracle JDK from other distributions in its JDK License General FAQs.
The timeline: JDK 17, JDK 21, and JDK 25
| Date | Event | Why it matters |
|---|---|---|
| September 2021 | NFTC introduced with JDK 17 | Oracle offered broad no-fee rights for the applicable release period. |
| September 2023 | JDK 21 released as an LTS release | JDK 21 became the next long-term platform for many enterprise applications. |
| September 2024 | JDK 17 NFTC period ended | Later Oracle JDK 17 updates moved under OTN according to Oracle’s published position. |
| September 2025 | JDK 25 released as an LTS release | Oracle says JDK 25 updates are planned to remain under NFTC through September 2028. |
| After September 2026 | Planned JDK 21 license transition | Oracle says later JDK 21 updates are planned to use OTN. |
| September 2028 | Planned end of JDK 25 NFTC period | Oracle currently plans a similar transition after the next LTS cycle. |
These future dates are Oracle’s stated plans, not guarantees that replace the license shipped with a particular binary. Oracle’s FAQ says the actual license terms control if they conflict with explanatory material.
Which Oracle JDK versions are affected?
| Release | Oracle’s published position | Practical question |
|---|---|---|
| JDK 8 | Current updates use OTN, with limited no-cost uses. | Is the deployment within an OTN-permitted category, or is paid coverage required? |
| JDK 11 | Updates use OTN. | Are production use and support rights covered? |
| JDK 17 | NFTC applied only through September 2024; later updates use OTN. | Which exact update is installed? For example, Oracle identifies different treatment around the 17.0.12 and 17.0.13 update boundary. |
| JDK 21 | NFTC is planned through September 2026; later updates are planned to use OTN. | Can the application move to JDK 25 before the transition? |
| JDK 25 | NFTC is planned through September 2028. | Can the organization use the extra time to establish a regular upgrade process? |
| Non-LTS releases | NFTC for their planned six-month support life. | Does the short support window fit the application’s release process? |
| Oracle OpenJDK | GPLv2 with the Classpath Exception. | Can the organization manage patching, validation, and support under this model? |
The exact update number matters. Do not classify an installation from “Java 17” or “Java 21” alone. Record the complete version string and preserve the license text associated with that binary.
What NFTC permits
Oracle describes NFTC as permitting free use by all users, including commercial and production use, subject to its conditions. Oracle also says hosted use is generally treated as internal business operations and permits redistribution when it is not for a fee.
“Free” does not mean unconditional. Separate review may be needed for:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #2
- commercial features or components downloaded separately;
- Java Management Service;
- Enterprise Performance Pack;
- Oracle Jipher and other separately licensed components;
- embedding Java in a commercial product;
- redistributing Java for a fee; and
- software-as-a-service or other hosted arrangements with unusual distribution or customer-access models.
The license shipped with the precise Oracle binary takes precedence over a summary or FAQ. For an embedded product, reseller arrangement, or redistribution model, obtain a contract-specific review rather than relying on assumptions about ordinary internal server use.
What OTN permits
OTN permits specified uses at no cost, including personal use, development, testing, prototyping, and demonstrating. That is narrower than NFTC’s broad commercial and production permission.
It is inaccurate to summarize OTN as “all commercial use is forbidden.” Oracle products and particular use cases can have specific treatment. Oracle publishes an approved product-use list covering examples such as Oracle SQL Developer, Oracle Forms, E-Business Suite, WebLogic client applications, and JD Edwards.
That list is not a universal exemption for every Oracle-related deployment. Production use for internal business operations, Java bundled into a commercial product, redistribution, and SaaS scenarios require careful analysis. Oracle says organizations outside permitted categories may need to move to another technology or obtain Java SE Universal Subscription.
Who is most exposed?
The highest-risk organizations are those that:
- run Oracle JDK 21 in production;
- need Oracle’s security and performance updates after September 2026;
- cannot yet certify JDK 25;
- depend on legacy APIs, removed modules, old application servers, native integrations, or outdated libraries;
- need Oracle support or Oracle-only commercial features;
- embed or redistribute Java in a commercial product;
- have many employees, contractors, consultants, or outsourced teams relevant to an Oracle subscription calculation; or
- have contracts, regulatory controls, or procurement policies that specifically require Oracle JDK.
Exposure may be lower when an organization runs Oracle JDK 25, Oracle OpenJDK, or another OpenJDK distribution; uses Oracle JDK only for development and testing under permitted terms; or receives a runtime from an application or cloud vendor and has confirmed that vendor’s licensing responsibility.
The useful question is not “Do we use Java?” It is: Which vendor’s binary, which exact update, in which environment, under which license?
Four practical choices
1. Buy Oracle Java SE Universal Subscription
This is the most direct route for an organization that cannot move off Oracle JDK 21 and needs Oracle support, long-lived versions, or commercial features. Oracle describes the subscription as including licensing, support access, Java Management Service, and other listed benefits. Details depend on the agreement.
Oracle says the subscription uses an employee-based metric. Container count, server count, cloud architecture, or application design does not by itself change that underlying metric. Therefore, do not estimate the bill from the number of JVMs alone. Ask procurement and legal teams how employees, contractors, outsourcers, consultants, and other covered personnel are counted.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Oracle’s available price-list materials contain historical examples but are not sufficient to present as an August 2026 quote. Obtain a current written quote based on the organization’s population, geography, entitlements, support term, and products.
Best fit: Oracle support or commercial features are essential, the application cannot yet move, or formal vendor accountability outweighs recurring cost.
Trade-off: a subscription does not eliminate modernization work, and an employee metric can produce a materially different cost from a server-based assumption.
2. Upgrade to Oracle JDK 25
Oracle says JDK 25 updates are planned to remain under NFTC through September 2028. Moving from JDK 21 to JDK 25 may therefore solve the immediate licensing deadline while retaining Oracle’s distribution.
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 minuteIt is not automatically a drop-in replacement. Test removed APIs, changed defaults, module access, security behavior, JVM flags, application servers, native libraries, database drivers, agents, and performance characteristics. Oracle currently indicates that the next LTS, JDK 29, is planned for September 2027 and that JDK 25 would follow a similar later transition pattern. Treat that as a forward-looking plan, not a permanent solution.
Best fit: the application is compatible with JDK 25 and the organization wants Oracle binaries without immediately purchasing a subscription.
Rank #4
Trade-off: the team must perform a real LTS upgrade and establish a recurring lifecycle instead of waiting for the next licensing deadline.
3. Use Oracle OpenJDK
Oracle OpenJDK builds are licensed under GPLv2 with the Classpath Exception. This can be attractive when the organization wants Oracle-produced OpenJDK builds and can operate without Oracle’s subscription model.
Oracle distinguishes its OpenJDK cadence and support model from subscription benefits. Oracle describes OpenJDK releases as being on a six-month cadence and targeted at developers, while its subscription provides longer-term access to older versions and direct support.
Best fit: GPLv2 with the Classpath Exception is acceptable and the organization can own binary intake, patch validation, lifecycle management, and incident response.
Trade-off: the organization must define how production binaries are selected, verified, archived, patched, and supported. Oracle OpenJDK does not automatically include every Oracle commercial feature.
4. Move to another OpenJDK distribution
Other distributions can provide a legitimate alternative to Oracle JDK licensing. Examples include Amazon Corretto, Eclipse Temurin, Azul Zulu, and BellSoft Liberica JDK.
Recommended Free Tools
AWS describes Corretto as a no-cost, production-ready, multi-platform OpenJDK distribution and announced Corretto 26 general availability in March 2026. “No-cost” describes the binary distribution, not every possible support, migration, compliance, or operational expense.
Best Value
Compare distributions on supported versions, security patch timing, paid support, escalation, container images, hardware optimizations, certifications, JavaFX or supplemental components, debugging tools, and maintenance duration. A distribution with free downloads may still require paid support for an enterprise risk profile.
Best fit: the organization wants a non-Oracle support model, a cloud-provider runtime, community binaries, or a commercially supported OpenJDK alternative.
Trade-off: switching vendors requires qualification. “OpenJDK” does not mean that every vendor build has identical patches, support, tools, or lifecycle commitments.
Inventory the estate before making a decision
Build an inventory across production, staging, development, test, desktop, build, container, Kubernetes, VM, and cloud environments. Capture:
- vendor, distribution, complete version and update number;
- license displayed by the package, installer, archive, or image;
- operating system, architecture, and package source;
- application owner, business criticality, and environment;
- application server, framework, database driver, messaging client, and native-library versions;
- JavaFX, Web Start replacements, commercial features, or separately downloaded components;
- number of servers, containers, desktops, and build agents;
- whether a cloud or software vendor supplies the runtime;
- whether Java is embedded in a product or redistributed to customers;
- Oracle contracts, product entitlements, and support requirements;
- required security-update window; and
- upgrade and rollback procedures.
Useful discovery commands
On Linux or macOS:
java -version
javac -version
which java
readlink -f "$(which java)"On Windows PowerShell:
java -version
Get-Command java
where.exe javaFor a container:
docker inspect <container>
docker exec <container> java -versionThese commands identify the runtime being invoked. They do not prove the governing license. Preserve the archive or package, checksum, image digest, package metadata, download source, installer records, and license files. Also inspect build agents and bundled runtimes: the Java used to compile an application may differ from the Java used to run it.
Test before changing JDKs
Treat an Oracle JDK-to-JDK 25 or OpenJDK migration as a deployment-readiness project:
- Build: compile the application and all native or generated components with the target runtime.
- Functional testing: run unit, integration, end-to-end, batch, scheduled-job, and file-processing tests.
- Security: test TLS, certificates, keystores, authentication, cryptographic providers, security policies, and scanners.
- Connectivity: validate JDBC drivers, connection pools, messaging clients, database procedures, and service integrations.
- Compatibility: exercise reflection, serialization, dynamic proxies, module access, removed APIs, and restricted internal APIs.
- Operations: validate startup flags, garbage collection, heap sizing, container limits, health checks, logging, and time-zone behavior.
- Observability: qualify APM agents, profilers, tracing libraries, monitoring exporters, and incident tools.
- Performance: compare throughput, latency, startup time, memory consumption, garbage-collection behavior, and error rates against the current runtime.
- Licensing: verify that the runtime image contains only components permitted by the selected license and that the exact archive and license text are recorded.
- Rollback: perform a rollback test using the previously validated runtime, not merely a theoretical deployment plan.
Java maintains strong compatibility across releases, but that does not guarantee that every application, framework, agent, native library, or vendor certification will work unchanged.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallQuestions for procurement and legal teams
- What exact Oracle binaries and update numbers are in scope?
- Which environments constitute production or internal business operations?
- Are contractors, consultants, outsourcers, and other personnel included in the subscription metric?
- Does an Oracle product entitlement cover this particular Java use case?
- Is Java embedded in a product, redistributed for a fee, or exposed through a hosted service?
- Which security updates are required, and for how many years?
- Is Oracle support contractually required by a customer, regulator, or internal policy?
- Would a different OpenJDK distribution satisfy application, security, certification, and support requirements?
- What is the cost of migration engineering, testing, vendor qualification, and ongoing patch management?
A sensible action plan before September 2026
- Inventory: identify every JDK vendor, update, environment, owner, and distribution path.
- Classify: separate Oracle JDK, Oracle OpenJDK, third-party OpenJDK, and vendor-bundled runtimes.
- Preserve evidence: archive binaries, checksums, package metadata, and the applicable license text.
- Identify exceptions: review commercial features, Oracle products, embedded software, redistribution, and SaaS deployments.
- Choose a target: compare JDK 25, Oracle subscription coverage, Oracle OpenJDK, and alternative vendors.
- Test early: qualify the target JDK with application, security, database, performance, and rollback testing.
- Budget accurately: include subscription or support costs plus migration, certification, operations, and compliance work.
- Document ownership: assign responsibility for future Java updates so the next LTS transition is routine rather than urgent.
The most important distinction is between license rights, access to updates, Oracle support, and commercial features. They are related but not identical. A company may be legally able to keep running an existing JDK while lacking the rights, support, or update path it needs for the future.
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.
