PhpStorm 2025.2 Help

Configuring JavaScript debugger

PhpStorm provides a built-in debugger for your client-side JavaScript code. The built-in debugger starts automatically when you launch a debugging session.

To ensure successful debugging, it is enough to specify the built-in web server port and accept the default settings that PhpStorm suggests for other debugger options.

Before you start

  1. Make sure the JavaScript and TypeScript bundled plugin is enabled in the settings. Press Ctrl+Alt+S to open settings and then select Plugins. Click the Installed tab. In the search field, type JavaScript and TypeScript. For more information about plugins, refer to Managing plugins.

  2. Make sure the JavaScript Debugger bundled plugin is enabled in the settings. Press Ctrl+Alt+S to open settings and then select Plugins. Click the Installed tab. In the search field, type JavaScript Debugger. For more information about plugins, refer to Managing plugins.

Bundled plugins: JavaScript and TypeScript, JavaScript Debugger

Set the built-in web server port

PhpStorm has a built-in web server that can be used to debug your application in a web browser or preview your code in the PhpStorm built-in browser. This server is always running and does not require any manual configuration. Learn more from Debug an application that is running on the built-in server.

  1. Press Ctrl+Alt+S to open settings and then select Tools | Web Browsers and Preview.

  2. In the Built-in server area, specify the port where the built-in web server runs. By default, this port is set to the default PhpStorm port 63342 through which PhpStorm accepts connections from services. You can set the port number to any other value starting from 1024.

    Built-in server port

Customize the default debugger configuration

Suppress calls

  1. Open settings by pressing Ctrl+Alt+S and navigate to Build, Execution, Deployment | Debugger.

  2. Suppress calls to the files on the built-in server from other computers or from outside PhpStorm by clearing the Can accept external connections or the Allow unsigned requests checkbox respectively.

    Suppress external calls

Choose the way to remove breakpoints

By default, you can toggle breakpoints by clicking the left mouse button. To change this behavior:

  1. Open settings by pressing Ctrl+Alt+S and navigate to Build, Execution, Deployment | Debugger.

  2. In the Remove breakpoint area, select the appropriate option.

    Remove breakpoints

Specify scripts to skip

By default, the debugger does not step only into library scripts. To expand the suppression list:

  1. Open settings by pressing Ctrl+Alt+S and navigate to Build, Execution, Deployment | Debugger | Stepping.

  2. In the JavaScript area, select Do not step into scripts checkbox and add the URL addresses to skip using the Add button  and the Remove button.

    JavaScript debugger: skip scripts

Advanced options

  • Open settings by pressing Ctrl+Alt+S and navigate to Build, Execution, Deployment | Debugger | Data Views.

    Enable or disable Inline Debugging, specify when you want to see tooltips with object values and expressions evaluation results, and so on.

    JavaScript debugger: Data views
  • Open settings by pressing Ctrl+Alt+S and navigate to Build, Execution, Deployment | Debugger | Data Views.

    Specify whether you want object properties to be shown in object nodes. If so, specify the properties. Use and to manage the list of properties.

    Properties to show on object nodes

Start a debugging session with your preferred Chrome user data

You may notice that your debugging session starts in a new window with a custom Chrome user data instead of your own, habitual, one. As a result, the window looks unusual, for example, your bookmarks, the browser history, and the extensions are missing, which altogether breaks your development experience. That happens because PhpStorm uses the Chrome Debugging Protocol and runs Chrome with the --remote-debugging-port option. However, if Chrome is already started, a debugging port can't be opened for any new or existing Chrome instance that has the same user data directory. Therefore, PhpStorm always starts a debugging session in a new window with a custom user data directory.

To open a new Chrome instance with your familiar look-and-feel, configure Chrome in PhpStorm to start with your user data directory.

Custom Chrome user data

Configure Chrome in PhpStorm to start with your preferred Chrome user data

  1. Save your preferred Chrome user data on your computer in a separate custom directory different from the Chrome default user data directory.

    You need to save your preferred user data in a separate custom directory because Chrome 136 and later does not support debugging in the default user directory. Learn more from the Chrome official website.

  2. Press Ctrl+Alt+S to open settings and then select Tools | Web Browsers and Preview.

  3. To create a new Chrome configuration, click Add. A new item appears in the list. In the Path field, specify the path to the Chrome installation folder.

  4. Select the new configuration and click the Edit button (Edit).

  5. In the Chrome Settings dialog, select the Use custom user data directory checkbox and specify the path to the custom directory with your preferred user data.

    If you have several user data profiles, each of them is stored in a separate subdirectory. To use a profile, specify it in the Command line options field as follows:

    --profile-directory="<profile_to_use>"
    Specify a custom profile subdirectory
  6. Mark your Chrome browser configuration default as described in Choosing the default PhpStorm browser. Do not forget to select the necessary browser from the Browser list when creating a run/debug configuration.

05 August 2025