Dev & EngARTICLE

JetBrains Will Fold PhpStorm Light Into Standard PhpStorm Instead of Keeping a Separate Build

JetBrains Will Fold PhpStorm Light Into Standard PhpStorm Instead of Keeping a Separate Build
Image: Bisneto Braga
Article · Dev & Eng
Reading
4 min
In short

Since June 2026, JetBrains had been testing a lean version of PhpStorm as an experimental build. Now it has decided to end that experiment and bring the optimizations to the standard version, gradually.

JetBrains confirmed, in a post on the official PhpStorm blog, that PhpStorm Light will not become a separate product. The improvements tested in that lean build will be incorporated, gradually, into standard PhpStorm, through regular updates. Anyone using the Light build today doesn't need to do anything now, but it will be discontinued once the merge is complete.

For anyone developing PHP on weaker hardware, running the IDE in a VM with little RAM, or who has simply gotten tired of waiting for the indexer to finish before opening the first file, this is the news that matters: the performance gain won't require switching installations or migrating configuration.

What PhpStorm Light Actually Was

PhpStorm Light has been available since June 2026 as an experimental build within JetBrains' Early Access Program (EAP). The proposal was simple: quickly test, without fear of breaking anything in production, which optimizations reduced startup time and memory consumption without removing functionality from the path of those who already use the IDE day to day.

The experiment touched on three specific fronts of PHP development (not the generic layers of the IntelliJ platform, which PhpStorm inherits regardless):

  • Faster startup: smarter order of project scanning and indexing, less unnecessary work when opening, and a clearer indexing progress indicator.
  • Lighter editing: a reduced inspection profile by default, a "smart mode" toggle, and other editor responsiveness tweaks.
  • Smaller footprint: tools that only load when the dev actually uses them (databases, for example), and rarely used plugins becoming opt-in instead of shipping enabled by default.

Why This Didn't Just Become a Flag in the Regular Version

JetBrains explains, in the post itself, the reason for creating an entire separate build instead of simply testing these changes directly in the stable version. Changing what loads at startup, which inspections run by default, and which plugins come bundled affects everyone who opens the IDE at the same time, and that's risky to test in a release that entire teams depend on every day.

The separate build gave the team freedom to experiment with these changes and gather feedback from those who agreed to join the program, knowing they were testing something unstable. It's the same feature-flag logic that many back-end teams apply in production, just applied to the development tool itself.

What JetBrains Learned From the Experiment

The central lesson, according to the post, is that much of the perceived slowness comes from work the dev never asked for. As soon as a project opens, standard PhpStorm already starts checking for updates, scanning places to suggest things, and preparing information the dev may never look at. In PhpStorm Light, that work is deferred until the moment it's actually needed.

Another point the team highlights is that faster doesn't mean less resource available. PhpStorm Light changes what comes enabled by default, not what's available: every plugin and feature that left the default set still exists and can be enabled manually at any time. It's the difference between removing capability and deferring its loading.

Not every change is right for everyone. Some of the new defaults will not suit every developer or workflow.

Hanna Yakush, PhpStorm Blog

This excerpt sums up why JetBrains promises that every change to a long-standing default will come with a simple way to restore the previous behavior. A dev who relies on the full inspection profile from the first second, for example, might prefer to keep the old behavior turned on.

What Changes for Those Who Already Use PhpStorm

Those on the standard PhpStorm build will receive several of PhpStorm Light's improvements through normal updates, with JetBrains explaining each change as it arrives. There's no parallel installation or configuration migration to do: the path is simply to keep updating the IDE that's already installed.

Those on the Light build today lose nothing for now, but should prepare for that build's discontinuation once the changes are fully incorporated into the main flow. It's worth following each PhpStorm version's changelogs from now on, since that's where the specific optimizations (startup, indexing, lazy loading of database tools) will appear, one by one, instead of all at once.

When This Actually Solves a Problem

The practical gain is greater for those running the IDE on limited hardware, in a development container with low reserved resources, or on a PHP project large enough that initial indexing becomes a visible bottleneck. For those who already run PhpStorm on a robust machine and never felt startup as a problem, the impact tends to be less noticeable day to day, although the lighter default inspection profile still subtly changes what the IDE flags while code is being typed.

It's worth remembering that these optimizations are specific to PhpStorm and the PHP flow; anyone using another JetBrains IDE (IntelliJ IDEA, WebStorm, PyCharm) isn't directly affected by this merge, although the shared IntelliJ platform has separately been receiving features like the agentic development workspace and the project-less Welcome screen introduced in version 2026.3. The underlying message, for anyone following development tools, is that separate experimental builds remain the way JetBrains tests reversible default changes, without forcing those who depend on the tool every day to become guinea pigs without a choice.

Translated from the Brazilian Portuguese original · Read the original

Read also
↳

Threads