Participate in the Kotlin Early Access Preview
You can participate in the Kotlin Early Access Preview (EAP) to try out the latest Kotlin features before they are released.
Before every language (2.x.0) and tooling (2.x.20) release, we ship Early Access Preview (EAP) builds for you to test in real projects and share early feedback. Kotlin EAP builds typically include the following stages:
EAP build | Description |
|---|---|
Beta1 | Introduces the first set of upcoming features, improvements, and other significant changes. Gives you an early opportunity to evaluate new functionality and share feedback. |
Beta2 | Usually adds more features and refinements based on the feedback we've received. Is feature-complete and continues the preview of the upcoming release, further maturing previously introduced features. |
RC | The first release candidate. Focuses on stabilizing the changes delivered in Beta1 and Beta2, as well as fixing regressions found during testing. |
RC2 | Includes important fixes to finalize the release and confirm readiness. |
We'd appreciate it if you report any bugs you find to our issue tracker, YouTrack. In most cases, we can fix them before the final release, so you won't need to wait for the next Kotlin release to see your issues resolved.
By participating in the Early Access Preview and reporting bugs, you contribute to Kotlin and help us make it better for everyone in the growing Kotlin community.
If you have any questions or want to join the discussion, you're welcome to join the #eap channel in Kotlin Slack. In this channel, you can also get notifications about new EAP builds.
Configure your project for the Kotlin EAP version
How the EAP can help you be more productive with Kotlin
Prepare for the Stable release. If you work on a complex multimodule project, participating in the EAP may streamline your experience when you adopt the Stable release version. The sooner you update to the Stable version, the sooner you can take advantage of its performance improvements and new language features.
The migration of huge and complex projects might take a while, not only because of their size, but also because some specific use cases may not have been covered by the Kotlin team yet. By participating in the EAP and continuously testing new versions of Kotlin, you can provide us with early feedback about your specific use cases. This will help us address as many issues as possible and ensure you can safely update to the Stable version when it's released. Check out how Slack benefits from testing Android, Kotlin, and Gradle pre-release versions.
Keep your library up-to-date. If you're a library author, updating to the new Kotlin version is extremely important. Using older versions could block your users from updating Kotlin in their projects. Working with EAP versions allows you to support the latest Kotlin versions in your library almost immediately with the Stable release, which makes your users happier and your library more popular.
Share the experience. If you're a Kotlin enthusiast and enjoy contributing to the Kotlin ecosystem by creating educational content, trying new features in the Kotlin EAP allows you to be among the first to share the experience of using the new cool features with the community.
Build details
Build info | Build highlights |
|---|---|
2.4.0-Beta2 Released: April 22, 2026 | A language release with major changes in the language and tooling updates. For more details, refer to the changelog or What's new in Kotlin 2.4.0-Beta2. |