- Updated: March 17, 2026
- 6 min read
Java 26 Released: New Features and Improvements
Java 26 brings a focused set of new JEPs, performance‑tuned garbage‑collector enhancements, and strategic deprecations that together lay the groundwork for Project Valhalla while delivering immediate productivity gains for Java developers.
Why Java 26 matters for you
The official announcement of Java 26 was published on Hanno’s blog. For Java developers, software engineers, and tech enthusiasts, this release is not just another incremental update—it is a strategic pivot toward the next generation of language features, especially those that will enable Project Valhalla (value types and specialized generics). In this article we break down every headline feature, explain the performance impact, and show how you can start experimenting today.
Overview of Java 26 JEPs
Java 26 ships with ten JEPs, ranging from core‑library extensions to HotSpot performance tweaks. The table below groups them by project area and indicates whether they are new features, previews, or deprecations.
| JEP | Project | Feature Type | Status |
|---|---|---|---|
| JEP 516 | HotSpot | Performance | New feature |
| JEP 522 | HotSpot | Performance | New feature |
| JEP 517 | Core Libs | Extension | New feature |
| JEP 524 | Security Libs | Security | Second preview |
| JEP 525 | Loom | Concurrency | Sixth preview |
| JEP 526 | Core Libs | New API | Second preview |
| JEP 529 | Panama | New API | Eleventh incubator |
| JEP 530 | Amber | Language | Fourth preview |
| JEP 500 | Core Libs | Deprecation | Prepare to make final mean final |
| JEP 504 | Client Libs | Deprecation | Remove the Applet API |
The most “eye‑catching” additions for most developers are the Ahead‑of‑Time Object Caching (JEP 516) and the G1 GC throughput boost (JEP 522). Both target latency‑sensitive workloads such as micro‑services and real‑time data pipelines. Meanwhile, the HTTP/3 client (JEP 517) brings the next‑generation transport protocol to the standard Java HTTP client, making it easier to take advantage of QUIC‑based networks without third‑party libraries.
For teams already experimenting with AI marketing agents or building custom integrations on the UBOS platform, the new OpenAI ChatGPT integration and ChatGPT and Telegram integration provide ready‑made building blocks that can be combined with Java 26’s lazy constants (JEP 526) for ultra‑fast startup in serverless environments.
Performance improvements
1. Ahead‑of‑Time Object Caching (JEP 516)
JEP 516 expands the AOT cache to a GC‑agnostic format. Previously the cache was tied to the specific garbage collector used during the training run (e.g., ZGC vs. G1). By storing objects as logical indices rather than raw memory addresses, the cache can be reused across any GC, eliminating the “cold‑start” penalty when switching from ZGC in dev to G1 in production. Real‑world benchmarks from the OpenJDK team show up to a 30 % reduction in warm‑up time for Spring‑Boot micro‑services.
2. G1 GC Synchronization Reduction (JEP 522)
The new dual‑card‑table design decouples application write‑barriers from the optimizer threads that maintain the card table. This reduces lock contention and yields 5‑15 % higher throughput on workloads with heavy object allocation (e.g., high‑frequency trading simulators). The memory overhead is modest—about 0.2 % of the heap—making it a safe default for most production clusters.
3. HTTP/3 Support (JEP 517)
By adding HttpClient.Version.HTTP_3, developers can opt‑in to QUIC‑based transport with a single line of code. The API automatically falls back to HTTP/2 or HTTP/1.1 if the server does not support HTTP/3, preserving compatibility while still gaining the latency benefits of reduced handshake round‑trips. Early adopters report up to 20 % lower tail latency on CDN‑backed services.
Deprecations and removals
- JEP 500 – Prepare to Make Final Mean Final: Deep‑reflection mutability of final fields now emits warnings and will become a hard error in a future release. This encourages developers to rely on immutable data structures and improves JIT optimizations.
- JEP 504 – Remove the Applet API: The entire
java.appletpackage is gone, reflecting the fact that browsers no longer support Java applets. Projects still using the API must migrate to AWT/Swing or modern web‑native alternatives.
The deprecations are deliberately aggressive to clean up legacy code paths that hinder performance and security. If you maintain a large codebase, start by scanning for java.applet imports and for reflective writes to final fields. The Java tutorials on UBOS provide scripts to automate this audit.
Key takeaways for Java developers
- Start‑up speed matters. Use the new GC‑agnostic AOT cache (JEP 516) together with lazy constants (JEP 526) to shave seconds off cold starts.
- Throughput gains are now “free”. Enable G1 GC’s dual‑card‑table mode (JEP 522) without extra configuration; the JVM detects the optimal switch automatically.
- Network‑level latency is lower. Adopt HTTP/3 via the standard
HttpClientAPI (JEP 517) for services that communicate over the public internet. - Security and maintainability improve. The removal of the Applet API and stricter final‑field rules reduce attack surface and enable better compiler optimizations.
- Future‑proofing. The previewed features (structured concurrency, primitive pattern matching, and the Vector API) are stepping stones toward Project Valhalla. Early experimentation now will pay off when those features graduate.
What’s next? Put Java 26 to work today
Java 26 is a “foundation release” that prepares the ecosystem for the big changes coming later this year. If you’re looking for a low‑friction way to experiment, consider building a small micro‑service on the Web app editor on UBOS. The editor ships with pre‑configured Maven wrappers, so you can drop in the new --enable-preview flags and start testing lazy constants or the new HTTP/3 client in minutes.
Need a ready‑made template? The UBOS templates for quick start include a “Java 26 starter” that already enables the AOT cache and configures G1 GC for optimal throughput. Pair it with the AI SEO Analyzer to ensure your service’s endpoints are search‑engine friendly from day one.
For enterprises, the Enterprise AI platform by UBOS offers managed runtimes that automatically apply the latest JDK patches, including Java 26. Smaller teams can explore the UBOS for startups program, which provides free credits for the first 90 days.
Finally, if you want to see Java 26 in action within an AI‑centric workflow, try the AI Video Generator template. It combines the new HTTP/3 client with ElevenLabs AI voice integration to stream video assets over QUIC, delivering smoother playback on low‑bandwidth connections.