Releases

What’s Fixed in IntelliJ IDEA 2025.3

Welcome to the overview of fixes and improvements in IntelliJ IDEA 2025.3.

In this release, we have resolved over 800 bug reports and usability issues throughout the IDE, with the highlights including improvements to the developer experience, Spring support, build tools, version control, the terminal, and more. Below are the most impactful changes that will help you work with greater confidence every day.

For the full list of updates, please refer to the release notes.

Unified distribution

Overall quality improvement 

Unifying IntelliJ IDEA Ultimate and Community Edition into a single distribution reduces the number of editions to work on, and having fewer editions means better quality. 

Maintaining separate Community Edition and Ultimate builds has always required parallel testing, validation, and packaging. By unifying the distribution, we can streamline development and focus our efforts more effectively, leading to faster iteration, fewer inconsistencies, and a better overall experience.

Smaller distribution

Despite the unification, we managed to make the distribution 30% smaller than IntelliJ IDEA Ultimate was on its own, meaning you don’t need to worry about this change slowing you down.

Fix for the uninstaller

While working on migration, we also resolved a long-standing issue causing the uninstaller not to work after IDE updates.

Developer experience

Better experience before indexes are ready

For several releases, it has been possible to begin working before all indexing is complete, as many features work without full indexes.

This release reflects this improved workflow. You’ll no longer see unnecessary warnings about incomplete indexes, as the IDE now reports only the information that’s relevant to your current task, reducing noise and helping you get back into your workflow faster. 

As part of this update, some processes have been renamed to better represent their purpose. For example, Analyzing project now appears instead of Indexing.

More details in Find Usages

The ability to search for and navigate to usages is one of the IDE’s main time-saving features. Previously, Find Usages showed only the file name, which was not always clear in complex codebases. Now you’ll be able to see relative paths where appropriate.

Accessibility

This release includes numerous accessibility improvements to make our IntelliJ IDEA easier to use. Most notably, the magnifier now works correctly in Windows, and many UI areas have been adjusted to work better with screen readers.

Islands theme

The new theme introduces several improvements. Perhaps the most noticeable is the new way tabs are displayed, as the active tab is more clearly visible and easier to spot at a glance.

Spring

Although support for Spring Framework 7 and Spring Boot 4 was the key focus of the release, we also kept an eye on other areas, ensuring inspections and code insight work reliably and correctly.

JPA support

When working with Spring Data, JPA entities do not get highlighted as errors if there is no connection to the database.

Spring debugger

In parallel, we are continuing to make Spring Debugger improvements based on your feedback.

Notably, we fixed issues that were affecting remote debugging, and we optimized context collection using the debugger API. It’s now ten times faster and does not affect startup time on projects with thousands of beans.

Many thanks to everyone who reported issues and shared sample projects!

Languages

Java

First-class support for the latest Java versions and features is the foundation of IntelliJ IDEA, which introduced day-one support for Java 25 in the 2025.2 release. 

This release focused on adding the finishing touches to that support, ensuring all bundled tools and libraries are compatible with Java 25 runtimes and fixing related inconveniences and inspections along the way.

We also started preparing support for features coming in future Java versions.

Kotlin

Spring Framework 7 and Spring Boot 4 support were two of the main points of focus for Kotlin support in this release. 

On top of that, we are finalizing our work on migrating to K2 mode, moving toward the deprecation of K1. 

Check out this post to learn more. 

Scala 

One of the major improvements for the Scala plugin is support for structural search and replace. You can now search for and replace code fragments by defining a pattern rather than relying on regular search and replace actions and manually sifting through irrelevant hits.

A significant part of the highlighting for Scala is based on the compiler output, but there is also an extra layer of built-in inspections that enhance highlighting logic beyond what the compiler provides. However, those can sometimes be slow. A new Disable built-in inspections option allows you to speed things up if they are holding you back.

Additionally, using actions like Show Type Info, Show Implicit Argument, Show Implicit Conversion, Copy Type, and others should no longer result in freezes.

To learn more about changes to the Scala support, refer to this blog post.

GitHub and GitLab integrations

As a developer, you interact with version control and code review tools multiple times a day, which means the several noticeable improvements in this release should be very helpful.

For a long time, the IDE automatically marked files as reviewed when you opened them. We have finally changed this behavior, and Mark as reviewed is now a manual action, so quickly reading through the changes does not make the request reviewed.

This release also brings proper UX support for multi-line comments, making the experience of working with them much clearer.

Terminal

The new terminal implementation is now enabled for PowerShell, bringing performance improvements, fixes, and visual enhancements for Windows users.

Build tools

For the Maven and Gradle integrations, building Micronaut projects or running Spring Applications using native IntelliJ IDEA build and run actions should no longer cause any issues.

The dependency analyzer popup also received several usability improvements. 

Web development

Better module resolution and monorepo support for JS

IntelliJ IDEA 2025.3 introduces significant improvements for working with large JavaScript and TypeScript monorepos. The IDE now understands customConditions in tsconfig.json and respects package exports with development conditions. As a result, auto‑imports, Go To Definition, and Find Usages now work reliably in Nx workspaces and similar setups, even when packages haven’t been built. 

TypeScript project references are correctly resolved across multiple packages and no longer require replacing .mts imports with .mjs.

Unified JavaScript Runtime settings page

Configuring similar settings in different places has long been a challenge. As of version 2025.3, Node.js, Bun, and Deno configurations have been merged into a single JavaScript Runtime settings page. This unified page consolidates interpreter configuration for all supported runtimes, making it clear which will be used.

Performance

UI responsiveness and overall speed remain top priorities. In this release, we continued eliminating freezes and optimizing performance in large projects. Notable improvements include optimizations to TypeScript highlighting as well as fixes for freezes related to the HTTP client and code navigation.

That’s it for this overview

Let us know what you think about the fixes and priorities in this release. Your feedback helps us steer the product so it works best for you.

Update to IntelliJ IDEA 2025.3 now and see how it has improved. Don’t forget to join us on X, Bluesky, or LinkedIn and share your favorite updates. 

Thank you for using IntelliJ IDEA!

image description