# CheerpJ 5.0 Launches with Java 21/25 and WasmGC Support The new release brings full OpenJDK compatibility and improved performance to browser-based Java applications. - **Source:** [programming](https://brifing.si/source/21f413d8-a401-41ca-83b1-904b87bb8257) - **Published:** 2026-11-02 - **Topic:** [Software & Engineering](https://brifing.si/c/engineering) - **Original article:** - **On Brifing:** https://brifing.si/s/089737a2-6cdd-4733-82cc-06cff7dbfc68 ## CheerpJ 5.0 Architecture Update The latest version of CheerpJ introduces full support for Java 21 and Java 25 within the browser environment. By integrating a complete OpenJDK implementation, the platform ensures that complex enterprise applications can run natively without requiring local installations. This release marks a significant shift in how legacy Java codebases interact with modern web standards. ## WasmGC Engine Integration A primary technical advancement in this release is the implementation of a new WasmGC engine. This engine leverages WebAssembly Garbage Collection to optimize memory management and execution speed for Java applications running in the browser. By offloading garbage collection to the browser engine, developers achieve better performance parity with native desktop Java environments. ## Full OpenJDK Compatibility CheerpJ 5.0 provides comprehensive support for the full OpenJDK stack, enabling developers to utilize standard Java libraries directly in web applications. This eliminates the need for custom shims or restricted subsets of the language. Teams can now migrate existing backend-heavy logic to the client-side while maintaining full compatibility with standard Java development workflows. ## Performance and Execution Gains The transition to WasmGC significantly reduces the overhead typically associated with running Java in a sandboxed web environment. By utilizing native browser-level primitives, the runtime minimizes latency during object allocation and collection cycles. These improvements allow for smoother execution of high-performance Java applications that were previously considered too resource-intensive for browser deployment. ## Modernizing Legacy Enterprise Systems This release specifically targets the modernization of legacy enterprise software that relies on older Java versions. Organizations can now expose complex desktop-based tools to web users without rewriting the entire codebase. By maintaining Java 21 and 25 support, CheerpJ ensures that businesses can leverage modern language features while extending the lifecycle of their existing software. ## Browser-Based Deployment Strategy Deploying Java applications via CheerpJ 5.0 removes the dependency on local Java Runtime Environments for end users. This simplifies the distribution process for internal business tools and public-facing applications alike. Developers can manage updates centrally on the server, ensuring that all users access the latest version of the application without manual client-side patching. ## Technical Implications for Developers The shift toward WasmGC requires developers to understand the interaction between Java bytecode and WebAssembly memory models. While the tool automates much of the conversion, optimizing performance involves aligning Java object structures with the capabilities of the underlying WasmGC engine. This provides a more predictable execution path for complex, multi-threaded Java applications in browsers. ## Future of Web-Based Java CheerpJ 5.0 represents a milestone in bridging the gap between traditional enterprise Java and the modern web ecosystem. By prioritizing OpenJDK parity and WasmGC performance, the platform sets a new standard for browser-based execution. This evolution suggests a future where complex Java applications operate seamlessly across all modern web browsers without performance compromises. ## Sources covering this story - https://www.reddit.com/r/programming/comments/1xlutld/cheerpj_50_java_2125_in_the_browser_full_openjdk/ — --- _Summary written by Brifing from the original reporting. Copyright in the original article belongs to its publisher; read the full piece at the link above._