Java Web Start was deprecated in JDK 9 and removed from JDK 11. Java 8 support follows a separate timeline. Here is how to assess the impact on your application and choose your next step.
The removal of Java Web Start from JDK 11 changed how desktop Java applications can be deployed. It did not remove Swing or make every existing JNLP application stop working. Your next step depends on the launcher, runtime and support arrangement you actually use.
What changed in the JDK
Oracle's JDK 11 migration guide and release notes identify two separate milestones.
Release | Change |
JDK 9 | Java deployment technologies, including Java Web Start, were deprecated. |
JDK 11 | The deployment stack, including Java Web Start and the javaws tool, was removed. |
Installing a newer JDK therefore does not provide the old Web Start launcher. The application's Java compatibility and its deployment method need separate checks.
Java 8 has a separate support timeline
Oracle's support roadmap currently extends Java Web Start support on Java 8 through December 2030 for entitled Oracle Customers. Confirm the support and licensing conditions for your deployment.
Support information checked in October 2026. Consult the linked roadmap when planning a change.
A JNLP file is a launch description
Java Web Start downloads and starts a Java application on the user's computer. Opening its link in a browser does not make the application a native web application.
Before changing the deployment, identify the JNLP file, downloaded JARs, Java version and services the application relies on. Include native libraries, local files, printers and any offline requirements. Test the workflows people use, not only whether the first window opens.
Choose your next deployment model
Keep desktop execution. Evaluate a JNLP launcher such as OpenWebStart, or package the application with a suitable runtime. Check compatibility, updates and who will support the installation on each device.
Provide browser access. Evaluate Webswing when users should open the application through a URL while it runs on a server. Plan the server environment and test the integrations affected by moving execution away from the desktop.
Modernise selected workflows. If the interface or architecture needs broader changes, define a manageable first part to replace. Our Modernisation Framework describes approaches that can be combined as the application evolves.
Make the next step a focused pilot
Choose one representative application and write down acceptance criteria for login, daily tasks, files, printing and performance. Use the findings to decide whether to retain desktop delivery, introduce browser access or begin a larger modernisation project.
For the deployment comparison and pilot checklist, read Webswing as a Java Web Start alternative. If you are ready to test browser access, follow our Java desktop application guide or discuss your application with us.
arrow_back_ios
