The IDE that empowers PHP developers
You may have never heard of PhpStorm Light, or you may be using it and wondering if this Early Access build is ever going to make its way into a major release.
In this post, we explain what PhpStorm Light is, what we’ve learned from this experiment, and what’s happening next.
What is PhpStorm Light?
PhpStorm Light has been available since June under the Early Access Program (EAP) as an experimental, trimmed-down version of PhpStorm. Its goal was to test quickly and boldly which optimizations could improve startup time, reduce memory consumption, and eliminate whatever slows PHP developers down – without disrupting the workflows they rely on.
Like every JetBrains IDE, PhpStorm is built on the IntelliJ Platform and benefits from many of the improvements introduced there. For example, version 2026.3 added an agent-first development workspace, a projectless Welcome screen, and separate worktrees for PR/MR reviews.
PhpStorm Light, on the other hand, focuses on tools, project structures, and workflows that are specific to PHP development. We experimented with:
- Faster startup: Smarter project scanning and indexing order, less unnecessary work during startup, and clearer indexing progress.
- Smoother editing: A lighter inspection profile by default, a smart mode toggler, and other optimizations.
- Lighter footprint: Not loading tools (e.g. for databases) until you actually need them, and making rarely used features and plugins opt-in.
Why a separate build?
We wanted to explore what would happen if we rethought some of PhpStorm’s long-standing defaults. But it’s hard to test this in a regular release that development teams rely on every day. Changing what loads at startup, which inspections run by default, and which plugins come bundled affects everyone at once.
A separate build gave us the freedom to experiment with these changes and gather feedback from PHP developers who had opted in and understood what they were testing.
That is also why it’s distributed separately: PhpStorm Light is an experiment, not a product.
What we’ve learned
- Much of the overhead is work you haven’t asked for yet. PhpStorm does a lot in the background as soon as a project opens: checking for updates, scanning for places to make suggestions, and preparing information you may never look at. In PhpStorm Light, this work is deferred until you actually need it. This means less work during startup and while you’re typing.
- Faster doesn’t have to mean fewer features. PhpStorm Light changes what’s enabled by default, not what is available. Features and plugins that aren’t enabled out of the box are still there, and you can enable them whenever you need them.
- Not every change is right for everyone. Some of the new defaults will not suit every developer or workflow. We’re still evaluating them, and we are open to your feedback.
So, here’s the plan: We’re bringing some of PhpStorm Light’s improvements right into PhpStorm, making sure that every change to a long-standing default comes with a simple way to restore the previous behavior.
What’s next?
If you’re using the standard PhpStorm build, several PhpStorm Light improvements will arrive through regular updates. We’ll explain each change when it ships. There is no need to install a separate build.
If you’re using PhpStorm Light, nothing changes for now. However, PhpStorm Light builds will eventually be discontinued once the changes are merged into the mainstream PhpStorm build.
Thank you to everyone who tried this experimental build and took the time to tell us what worked and what didn’t.
Is there anything else we should take into account? Let us know in the comments to this blog post or provide your feedback on YouTrack. Your input is helping shape the future of PhpStorm.












