PhpStorm 2018.1 is now released!

Posted on by Maxim Kolmakov

PhpStorm 2018.1, the first major update for PhpStorm in 2018, is now available! You can download it here or via JetBrains Toolbox App.

Our website has all the details of this release, and here’s a roundup of the notable highlights.


PHP Language

  • Inline function/method refactoring
  • Refactor your code to functional style
  • Configurable unchecked exceptions
  • Goto Symbol navigation improvements
  • Hierarchy checks for class aliases


  • Creating class from test
  • Codeception: code coverage
  • Better @covers support
  • Gutter icons for running tests

HTTP Client

  • Assertions support
  • Simplified first start

Please see our issue tracker for the full list of fixed PHP-related issues, and release notes from all previous EAP builds.

PhpStorm 2018.1 also brings major improvements in its support for web technologies, such as reformat with Prettier, create new Vue project, TypeScript 2.7 support, debugging React Native apps and much more.

IntelliJ Platform has provided this release with lots of new features as well as bug-fixes. Specifically, Git partial commits, new Documentation UI, better HiDPI support on multiple displays for Windows, reworked focus subsystem, ability to open Terminal in a specific folder, and even more.

Database tools have been improved with Data editor SQL log, external schemas in Redshift and virtual schemas in Exasol, ability to choose how to switch schemas and more.

For more details please see What’s New in PhpStorm 2018.1 and download a free 30-day PhpStorm trial for your operating system.

PhpStorm 2018.1 is available as a free update for everyone who has an active subscription for PhpStorm or All Products!

JetBrains PhpStorm Team
The Drive to Develop

Comments below can no longer be edited.

33 Responses to PhpStorm 2018.1 is now released!

  1. Thomas Schulz says:

    March 29, 2018

    R.I.P classic “Windows” theme …

  2. Rafael Corrêa Gomes ♛ says:

    March 29, 2018

    Great! 😀

  3. Micha Hobert says:

    March 30, 2018

    I can not delete or return anymore – all keymappings look fine and I changed them again with pressing the button after the update. Still nothing. Am I overseeing something?

    I am using a Lenovo T470 with Ubuntu 17.04

    EDIT: I had to reboot my system to make it work. Restarting Phpstorm did not do the trick.

    • Dmitry Tronin says:

      March 30, 2018

      Try to reset your Keymap scheme (gear icon > Restore Defaults)

  4. Michael says:

    March 30, 2018


    Database manager is very slow. In previous version it could display very large tables. And these version gets a problem with less than 500 rows.
    Tools, that are undocked to a window mode, could not be brought back to the panel.
    I mean, if this IDE takes more than 1,5 GB of RAM, than I’m expecting MEGA speed for all sections of this IDE.

    To compare with Sequel Pro for example: it takes round about 120 MB memory for reading much more complex and bigger tables with more data than only 500 rows.

    PhpStorm is going to become slower and slower. It’s cool, that there are some tools and stuff, but the core of this tool is to get code written. So writing of code should be fast, without any time to get color scheme calculated and viewed or some short brakes. Don’t loose the focus. We need fast software and in my case I’m working on latest and powerful macbook pro.

    If it continues like this with the needed RAM and the (un)speed of PhpStorm, I suppose more and more people would be ready on day to give up all the GUI-Tools you built in and go back to editors like Visual Studio Code and use terminal for running all the tools (git, composer, gulp, compilers and so on) like in old times, BUT FAST.

    Hope PhpStorm get fast (again) one day.

    • Anton Kozlov says:

      March 30, 2018

      Same problem, 2018.1 is a WAY slower than 2017.3

      • Dmitry Tronin says:

        March 30, 2018

        In general or database-wise?

        • Anton Kozlov says:

          March 30, 2018

          Looks like related with database part, switch between IDE tabs lags with opened database table

    • Dmitry Tronin says:

      March 30, 2018

      It would be great if you could describe this in details at
      That would really help if you can provide some data our developers could look into.

    • shon says:

      April 2, 2018

      Also noticed that same thing and was hoping for better speed. Prior to this version my queries were really slow, sometimes having to force quit it was taking so long. Sequel Pro no problem…

  5. Josh Miller says:

    March 30, 2018

    I love phpstorm! <3 And the toolbox app updated me yesterday and no issues were had, it just worked. Jetbrains, you guys are the best! So grateful to have such a strong development tool that caters to my niche: PHP development for Drupal.

  6. mkz says:

    March 30, 2018


    The “search” and “search-and-replace” box, in the context of the editor (not the Project view) FREEZES for quite a few seconds and any keyboard input is ignored! This also freezes any keyboard input in the editor anywhere.

    If I click the “x” button in the search box it seems to temporarily solve the problem, but it appears again upon another search!
    UPDATE: Sorry, I was wrong, clicking the “x” button does not solve the issue. I’d have to wait for about ~10 seconds for keyboard input to be taken, after attempting a search or search-and-replace. The close button on the right side (for closing the search bar) works for its purpose (closing the bar), but the freeze persists for the ~10 seconds!

    My productivity plummeted. I did not consider filing a ticket because I cannot wait for years in this state! This needs to be fixed ASAP, it’s a critical feature which renders the IDE into more of a problem than a tool!

    Environment: LinuxMint 17 (LTS) / KDE.

    UPDATE: I’ve disabled all custom plugins that I had, tried the “Invalidate cache & restart”, I’ve even removed the database connection, considering Michael’s comment on database manager being slow. Nothing improved.

    As a side note, this is not only my problem, all members of my team that performed the upgrade to 2018.1 are affected, on both Linux and windows platforms.

    • Vladimir Luchansky says:

      April 2, 2018

      Best would be to reproduce the issue, collect logs via Help > “Collect and Show Logs in …” and submit them to Support via – there are currently several issues that will be fixed in upcoming 2018.1.1.

      • Dan Brown says:

        April 10, 2018

        I get this in 2018.1.1 for the “Find in Path” dialog. 5-10 second pause every time I open it where I can’t type, even press escape to close it. the Mouse works fine though.

  7. БитриксоидИзКолхоза says:

    March 31, 2018

    Popup menu section “Deployment” was more useful before hided in submenu.
    Now I need more click for deploy file to remote host.

    • Kris Triplett says:

      April 2, 2018

      Agreed. If I have a default server set, I would like to have the context menu shortcut back rather than having to go into the submenu.

      • Vladimir Luchansky says:

        April 2, 2018

        You can place the action where you need it to be via Settings/Preferences| Appearance & Behavior | Menus and Toolbars.

    • Vladimir Luchansky says:

      April 2, 2018

      You still can customize it in Settings/Preferences | Appearance & Behavior | Menus and Toolbars.

  8. БитриксоидИзКолхоза says:

    March 31, 2018

    xdebug remote debugging: “stop” not breaking script.
    It disabling in PHPStorm but still on air. Script can’t break and I should close PHPStorm to break it,

    • Vladimir Luchansky says:

      April 2, 2018

      What do you mean by “not breaking script”? If you stop debugging session in the middle of the page, the connection will be broken and web page will stay in that state on web server side as well – PHP interpreter won’t continue loading the script and web page won’t be rendered completely.

      • БитриксоидИзКолхоза says:

        April 3, 2018

        I mean that stop must be stop.
        PHPscript must be stopped and web page must be terminated.
        But if I take connection too long and press stop button in PHPStorm:
        – stop-button turn gray = ok
        – web page continue to load = not ok;
        – debug session continue: for example I may hover cursor to expression and see debug information = not ok.

        Only if in this case I close PHPStorm, debug session terminated completely.

        • Eugene Morozov says:

          April 4, 2018

          There’s a chance Xdebug initiates a new session after you stop the previous one.
          Try first disabling Listening for incoming connections, and then pressing Stop – would that work?

  9. NixLAB AB says:

    April 3, 2018

    This update killed the Symfony plugin, unfortunately that renders it unusable for me. Had to do a roll-back. I’m sure it will be fixed soon! Keep up the good work guys.


Subscribe for updates