If your organisation still relies on JNLP files to launch Java applications, you’ve probably discovered that Java Web Start is no longer included with modern Java distributions.
While many organisations continue to rely on Java Web Start for business-critical applications, there are now several ways to run JNLP applications, each with different trade-offs.
This guide explains what changed, the most common alternatives and why many organisations are moving to the CheerpJ JNLP Runner for browser-based deployment.
What Is a JNLP File?
A JNLP (Java Network Launch Protocol) file is an XML document used to launch Java Web Start applications.
Rather than containing the application itself, a JNLP file tells Java where to download the application, which Java version to use, and how to launch it.
Many enterprise applications, including internal business systems, Oracle Forms deployments and engineering software, still use JNLP files today.
Why Java Web Start Was Discontinued
Oracle deprecated Java Web Start with Java 9 and removed it from later Java releases.
As a result:
- Modern Java distributions no longer include Java Web Start.
- Most OpenJDK distributions require a separate JNLP implementation.
- Organisations have had to find alternative ways to launch existing applications.
For many teams, the application itself continues to work perfectly. The challenge is simply how users launch it.
Common Java Web Start Alternatives
Most organisations have taken one of four approaches.
OpenWebStart
OpenWebStart replaces the original Java Web Start launcher while preserving existing JNLP files.
Advantages
- Minimal application changes
- Familiar user experience
- Fast migration
Considerations
- Requires a local Java installation.
- Desktop deployment and updates must still be managed.
- Ongoing endpoint support.
Virtual Desktop Infrastructure (VDI)
Some organisations centralise Java applications using VDI or Remote Desktop Services.
Advantages
- Centralised runtime management
- Existing applications continue to work
Considerations
- Infrastructure costs
- Session latency
- Printing and file redirection issues
- Poor experience for remote and mobile users
Rewrite the Application
Some organisations choose to replace their Java client entirely.
Advantages
- Modern user interface
- Opportunity to redesign workflows
Considerations
- High cost
- Long delivery times
- Significant project risk
- Existing business logic must be recreated
CheerpJ JNLP Runner
The CheerpJ JNLP Runner allows existing JNLP applications to run directly in Chrome and Microsoft Edge.
Instead of installing Java Desktop on every endpoint, users launch applications through a browser using the CheerpJ runtime.
This approach allows organisations to continue using their existing Java applications while simplifying deployment and reducing desktop management.
Comparing Your Options
| Approach | Local Java | Browser Access | Time to Deploy | Ongoing Management |
|---|---|---|---|---|
| OpenWebStart | Required | No | Fast | Medium |
| VDI / RDP | Centralised | Remote session | Medium | High |
| Application rewrite | No | Native web | Slow | High |
| CheerpJ JNLP Runner | Not required | Native browser | Fast | Low |
When Should You Consider Moving?
Many organisations begin evaluating alternatives when they experience:
- Increasing support requests for Java installations.
- Browser compatibility issues.
- Growing VDI infrastructure costs.
- Delays to application rewrite projects.
- Security or compliance concerns around desktop Java.
If any of these sound familiar, it may be time to evaluate a browser-based approach.
Frequently Asked Questions
Can I still open a JNLP file?
Yes. Although Java Web Start is no longer included with modern Java distributions, JNLP files can still be used with compatible launchers such as OpenWebStart or the CheerpJ JNLP Runner.
Does Chrome support JNLP files?
Chrome does not include native support for Java Web Start. The CheerpJ JNLP Runner enables JNLP applications to launch directly from Chrome.
Do users need Java installed?
With the CheerpJ JNLP Runner, no local Java installation is required.
Can I keep my existing application?
Yes. The CheerpJ JNLP Runner is designed to work with existing Java Web Start applications without requiring a full application rewrite.
Which Approach Is Right for You?
If your priority is simply maintaining the current desktop deployment model, OpenWebStart may be a suitable short-term solution.
If you’re already planning a complete application redesign, a rewrite may make sense despite the longer timeline.
However, if your goal is to continue running existing JNLP applications while reducing desktop management and enabling browser-based access, the CheerpJ JNLP Runner offers a practical migration path without changing the application itself.
Learn more about the CheerpJ JNLP Runner and see how existing Java Web Start applications can run directly in Chrome and Microsoft Edge.
