What is the Oracle NFTC license?
The Oracle NFTC license, short for No Fee Terms and Conditions, is the license Oracle applied to recent Oracle JDK releases starting with Java 17, allowing free use including in production and for commercial purposes. It replaced the more restrictive terms that had applied to Oracle Java in the preceding years and was, on its face, a return to free production use for the latest releases. Under the NFTC you can download, run, and redistribute the covered Oracle JDK without a paid subscription, which is why many estates quietly adopted it.
The important word is recent. The NFTC covers the specified newer versions, not the whole history of Oracle Java. Older releases remain under their original terms, which for several versions means a paid subscription is required for updates or commercial use. So the presence of NFTC in your estate tells you only part of the story. The rest depends on which other versions are installed, and under which terms each of them runs. For the broader version map, read which Java versions require a license.
Where do the limits of the NFTC license bite?
The NFTC limit that bites hardest is time, because the free updates for a covered version continue only until one year after the next long term support release ships, after which Oracle moves that version to paid terms. Oracle issues a long term support, or LTS, release on a regular cadence. When the following LTS arrives, the older NFTC version keeps receiving free updates for one more year, and then it does not. To stay current on security updates beyond that point you either move to the newer NFTC version or take a paid subscription for the older one. An estate that adopted an NFTC release and then stood still can therefore drift out of the free window without anyone changing a line of code.
Two further limits matter. First, the NFTC applies to the Oracle JDK builds Oracle designates, so mixing in older Oracle Java, or Oracle Java embedded in third party applications, can reintroduce paid terms you did not intend. Second, the NFTC does not change the per employee model where a paid version is in use, so a single estate can hold both free NFTC versions and paid liability at the same time. The risk is not that NFTC is a trap. The risk is that NFTC covers a narrower slice of your estate than a quick look suggests, and the paid slice still prices against headcount.
NFTC is a timed, version specific allowance. It removes cost for covered versions inside the window. It does not remove the older versions in your estate, the embedded copies in third party software, or the per employee pricing on anything that needs a paid subscription.
A worked example of the NFTC window
Consider an estate that standardised on an NFTC covered Oracle JDK shortly after it shipped and assumed Java was now free. Two years on, a newer LTS release has come and gone, and the one year window after it has closed for the older version. The estate is still on the older build, still pulling Oracle updates.
| Stage | License position |
|---|---|
| Adopt NFTC covered Oracle JDK | Free, including production |
| Next long term support release ships | Still free for one more year |
| One year after that release | Updates move to paid terms |
| Continue on Oracle updates anyway | Paid subscription required, priced per employee |
Nobody made a licensing decision. The estate simply aged past the free window while continuing to take Oracle updates, and a soft audit email can now frame that as a paid subscription liability across the whole workforce. The fix is to know the window for every version you run, and to plan the move to the next NFTC release or to a maintained alternative before the window closes. For the comparison with the older paid licenses, read legacy Java licenses versus the subscription.
Our Java exposure assessment kit helps you map every Java version in your estate, identify which sit inside an NFTC window, and size the paid exposure on the rest. We reduce your Oracle exposure or we reimburse our service fee, on a Fixed Fee or Gainshare basis with no risk to you.
What is the buyer move?
The buyer move is to inventory every Java version in your estate, mark which sit inside a live NFTC window and which do not, and plan upgrades or migrations before any window closes. Treat NFTC as a calendar item, not a settled state, because the free period expires on a schedule tied to Oracle's release cadence. For versions that have fallen out of the window, weigh a paid subscription against moving to a maintained build of OpenJDK or another vendor's distribution. Where the terms for a specific version or an embedded copy are unclear, treat the answer as contract dependent and confirm it. Then work up to the Oracle Java licensing guide for the full method.
FAQ
What is the NFTC license? The No Fee Terms and Conditions, applied to recent Oracle JDK releases from Java 17, allowing free use including production until one year after the next long term support release.
Where do the limits bite? Mainly on time. The free updates end one year after the next LTS release, and the NFTC covers only the designated recent versions, not older Oracle Java.
Does NFTC remove audit risk? Not by itself. Older versions and embedded copies run under other terms, and the per employee model still applies where a paid version is in use.