Java Applets Deprecation Reasons Fact Checked
“Melania Tsyhan CS 3250 17 April 2026 The Deprecation of Java Applets Java Applets were once a central part of early web interactivity, offering capabilities that standard HTML could not provide in the mid 1990s. However, the technology has been deprecated since Java 9 and ultimately removed in later Java releases due to a combination of declining browser support, significant security concerns, and the evolution of modern web standards. The primary reason for deprecation was the disappearance of the browser plugin model that applets depended on. Applets required NPAPI (Netscape Plugin Application Programming Interface) to run, but major browsers began phasing out NPAPI between 2013 and 2017. Chrome removed NPAPI support in 2015, Firefox followed in 2017, and Microsoft Edge never supported it at all. Without NPAPI, applets could no longer run in modern browsers, effectively rendering the technology obsolete. Security vulnerabilities further accelerated the decline of applets. Although applets were originally sandboxed to protect users, the plugin model became a frequent target for exploits. By 2014, unsigned applets were blocked by default, and even signed applets required users to make trust decisions that were often misunderstood, creating opportunities for malicious code to spread. These persistent vulnerabilities made applets increasingly incompatible with modern security expectations. Browser vendors’ shift away from plugins also aligned with the rise of more capable and secure web technologies. HTML5, CSS3, and JavaScript matured into powerful standards that could deliver interactive content without requiring external plugins. As a result, applets saw a steep decline in usage, and Oracle formally deprecated the Java browser plugin in JDK 9, noting that developers should migrate to plugin free technologies such as Java Web Start or modern web frameworks. The removal of the Applet API in later Java versions reflects the broader evolution of the web. Applets were designed for a web ecosystem that no longer exists. Modern browsers prioritize security, performance, and native web standards, leaving little room for legacy plugin based technologies. Even Oracle acknowledged that applets had become a “mostly non functional” part of the platform once browser support disappeared. Personal Opinion The reasoning behind the deprecation of Java Applets is justified. The web has moved toward safer, standardized, and more efficient technologies, and maintaining a plugin based system would introduce unnecessary security risks. While applets were innovative in their time, continuing to support them would conflict with modern browser architecture and security practices. The deprecation reflects a natural and necessary progression in web development. References (APA Style) CodingTechRoom. (n.d.). Why were applets deprecated in JDK 9? Retrieved from CodingTechRoom. Inside.java. (2025). So long and thanks for all the applets. Retrieved from Inside.java. Stack Overflow. (2017). Why were applets deprecated in JDK 9? Retrieved from StackOverflow.com. Bswen. (2026). Why Java 26 removes the Applet API: End of an era. Retrieved from Bswen.com.”
Summary
Java applets were indeed deprecated in Java 9 (via JEP 289) and later removed in Java 26, following the loss of NPAPI support in browsers such as Chrome (2015) and Firefox (2017). Security vulnerabilities and the shift to HTML5, CSS3, and JavaScript accelerated their obsolescence, and Oracle officially phased out the Applet API as described.
Sources 58 searched
- Modern browsers are closing the door on Java exploits, but some threats remain | Microsoft Security Blog
Internet Explorer 11 provides a mechanism to validate that a webpage is safe before allowing embedded Java applets. Further updates to Internet Explorer released in 2014 hardened the browser against Java exploitation by reducing use-after-free exploits and blocking out-of-date ActiveX controls. The fact that new browsers are flexing muscles in the security space is good news, but the bad news is that some threats still persist.
- JEP 398: Deprecate the Applet API for Removal
The Applet API was previously deprecated, though not for removal, by JEP 289 in Java 9.
- JEP 504: Remove the Applet API
The Applet API and the appletviewer tool were deprecated in JDK 9 via JEP 289 (2017), when web-browser vendors were already removing support for applets.
- [JDK-8256145] JEP 398: Deprecate the Applet API for Removal
The Applet API was previously deprecated, though not for removal, by JEP 289 in Java 9.
- Java applet - Wikipedia
Beginning in 2013, major web browsers ... becoming completely unable to be run by 2015–2017. Java applets were deprecated by Java 9 in 2017, deprecated for removal by Java 17 in 2021, and removed by Java 26 in 2026....
- The Rise and Fall of Java Applets: A Web Revolution Derailed | oome
timeline title The Decline of the ... interactivity emerges 2007 : Apple iPhone launches without plugin support : The mobile web's future is defined ~2013-2016 : Browsers start blocking NPAPI plugins : Chrome, Firefox, and Edge cite security & performance 2017 : Applet API is ...
- NPAPI deprecation: developer guide
In January 2015 all plugins will be blocked by default. Even though users will be able to let NPAPI plug-ins run by default in January, we encourage developers to migrate of off NPAPI as soon as possible. Support for NPAPI will be completely removed from Chrome by September 2015.
- Applets Are Officially Going, But Java In the Browser Is Better Than Ever - Slashdot
But long-time Slashdot reader AirHog links to this blog post reminding us that "Applets Are Officially Gone, But Java In The Browser Is Better Than Ever." This brings to an official end the era of applets, which began in 1996.
- So Long and Thanks for All the Applets – Inside.java
Because deployment models have changed and browsers stopped supporting the plugin model, applets are no longer possible on modern web browsers.
This fact check is free and donation-based. $1 powers ~30 fact-checks.
