Java applet replacement: your options after JDK 25

Somewhere in your company an applet still does real work. Maybe it's the order entry screen a branch office opens in an old browser profile, or a planning tool that lives inside a locked-down virtual desktop because nothing else will start it. It kept running because nobody touched it. That grace period is over, and finding a Java applet replacement is no longer a job you can push to next year.
JDK 25 is the last Java release that ships the Applet API. JDK 26 removed it. This post sets out the dates, what the removal breaks, and the options you can stand behind: keep the applet reachable in a browser through Webswing while you plan, or rebuild its screens as a webforJ app in Java, with the Java team you already have.
Moving a desktop Java app to the web?
Send us a screenshot of one screen and we'll reply with how it moves to webforJ.
Applets removed from the JDK: the dates
The removal came in steps, spread over almost a decade:
| Release | What changed |
|---|---|
| JDK 9 (2017) | Applet API and the appletviewer tool deprecated (JEP 289) |
| JDK 11 (2018) | appletviewer removed, and the browser deployment stack for applets and Web Start removed |
| JDK 17 (2021) | Applet API deprecated for removal (JEP 398) |
| JDK 24 (2025) | Security Manager, which sandboxed applet code, permanently disabled (JEP 486) |
| JDK 25 (GA September 16, 2025) | The last release that still contains the Applet API |
| JDK 26 (GA March 17, 2026) | Applet API removed (JEP 504) |
JDK Enhancement Proposal (JEP) 504 states the reason plainly: neither recent JDK releases nor current web browsers support applets. Since appletviewer left in JDK 11, there has been no way to run an applet with the JDK itself. The removal shipped in JDK 26, so every JDK from 26 on is applet-free.
Java Web Start, the usual sibling of the applet, left earlier. The JDK 11 release notes say the deployment stack required for applets and Web Start applications "has been removed in JDK 11."
What the removal breaks
JEP 504 deletes the whole java.applet package: Applet, AppletContext, AppletStub and AudioClip. It also removes javax.swing.JApplet and java.beans.AppletInitializer, along with the methods and fields that reference them in java.beans.Beans and javax.swing.RepaintManager.
For a business app that means:
- A class that extends
AppletorJAppletno longer compiles against JDK 26 or later. - Code that casts the result of
URL.getContent()toAudioClipno longer compiles or runs, as the JEP spells out. - A shared library that still references these classes ties every app that uses it to JDK 25 or older.
The JEP is blunt about the choice left to you. Applications that still use the Applet API "will either stay on older releases or will migrate to some other API." If your applet also blocks the move off an old runtime for the rest of the estate, the cost of waiting is already on the table, as the post on Java Swing technical debt lays out for desktop Java in general.
What replaces Java applets
There are four answers you can defend in front of an architect and a budget holder. Two of them buy time. Two of them move the app forward.
Stay on JDK 25 or older
This is the answer the JEP names first, and for a few months it can be the right one. It doesn't make the applet work in a modern browser, though. Browser plug-ins are long gone, and the JDK has had no applet runner since JDK 11. Staying put keeps the code compiling. It does nothing for the users who need to reach the screens, and every year on an old release makes the eventual move larger.
Turn the applet into a desktop app
JEP 504 points out that where the Applet class only serves as a user interface container, the AWT API offers alternatives. In practice, the content of a JApplet can move into a JFrame and compile on a current JDK. The price is that you are back to delivering and updating a desktop app on every machine, and Java Web Start, the tool that used to do that from a link, has been out of the JDK since Java 11. For an internal tool used by a handful of people, that can be fine. For an app your customers or field staff open from a browser, it's a step backwards.
Run the applet in the browser with Webswing
Webswing documents applets as a supported launcher type. In the Webswing applet configuration, you set up the applet much like a Swing app, choose Applet as the launcher type, and name the applet class that extends java.applet.Applet, plus any applet parameters. The same page lists embedding into your web page and a Java to JavaScript interface. Webswing runs the app on the server and shows its interface in the browser, so users get a URL instead of a plug-in.
Two facts keep this option honest. The applet class still extends java.applet.Applet, so the Java runtime that runs it on the server has to be one that still ships the Applet API, which means JDK 25 or older. The Webswing documentation lists Java 8, 11, 17, 21 and 25 as supported, so the versions it runs on still include that API. And Webswing is a separate commercial product: its licensing page states that using it in production requires a commercial license. It buys time without touching the applet's source. It doesn't remove the dependency on the Applet API.
Webswing and webforJ are partners. Webswing keeps the old app reachable today, and webforJ carries it forward.