PhpStorm 2026.2 Help

Laravel Pint

On this page, enable and configure the Laravel Pint quality tool.

Item

Description

Configuration

Select the required interpreter from the list. The list contains all the currently configured local and remote PHP interpreters. For more information, refer to Configure local PHP interpreters and Configure remote PHP interpreters.

Clicking the Browse button to the right of the drop-down list opens Laravel Pint Dialog.

Show ignored files

Click to open the Laravel Pint Ignored Files dialog, which lists the files that Laravel Pint skips. PhpStorm suggests adding a new file to the list during inspection when waiting for response from the Laravel Pint exceeds the limit specified in the Tool process timeout field. This is done to prevent slowing down processing. For each file, PhpStorm displays its name and location.

  • To add a file, click the Add button and locate the desired file in the dialog that opens.

  • To delete a file from the list and have Laravel Pint process it again, select the file and click the Remove file button the Remove button.

  • To remove all the files from the list, click the Close button.

Reformat only uncommitted files

Select the checkbox to only modify the files that have uncommitted changes.

Path to pint.json

Specify the path to your own pint.json configuration file. pint.json files are optional: they are used to enable/disable specific rules from the predefined Laravel Pint presets, or to reuse custom rulesets from PHP CS Fixer.

Ruleset

Select one of Laravel Pint's predefined group of rules.

Run mode

Configure how often Laravel Pint is triggered to analyze code:

  • On the fly – Laravel Pint runs automatically in the background. Issues are highlighted in the editor as you type.

  • On idle – Laravel Pint runs after you stop typing and the inactivity period specified in the Idle threshold (ms) field passes.

  • On save – Laravel Pint is triggered only when the file is saved either manually or via PhpStorm's autosave. Issue highlighting is updated only when the file state is persisted to disk.

Idle threshold (ms)

Define the delay time in milliseconds after code modification before Laravel Pint runs.

Minimum interval (ms)

Define the minimum time in milliseconds that must pass between two consecutive runs of Laravel Pint on the same file. This prevents Laravel Pint from running too frequently in case of frequent file savings or heavy typing.

Laravel Pint Dialog

The dialog opens when you click the Browse button next to the Configuration list on the Laravel Pint page.

Use this dialog to configure the used PHP interpreter, path to the Laravel Pint executable file, as well as Laravel Pint's behaviour. For more information, refer to Laravel Pint.

Item

Description

Interpreters pane

The left-hand pane of the dialog shows the default PHP interpreter to use the Laravel Pint from. To add a different interpreter, click the Add button and select an item from the list of CLI interpreters configured in the project.

Laravel Pint path

In this field, specify the location of the Laravel Pint script: pint.bat for Windows or pint for Linux and macOS.

PhpStorm detects the path to the Laravel Pint executable file in the vendor/bin folder and fills in the field automatically, but you can edit it if necessary. Type the path manually or click the Browse button and select the path in the dialog that opens.

To check that the specified path to pint.bat or pint ensures interaction between PhpStorm and Laravel Pint, that is, the tool can be launched from PhpStorm and PhpStorm will receive problem reports from it, click the Validate button. If validation passes successfully, PhpStorm displays the information on the detected Laravel Pint version.

Tool process timeout

In this field, specify how long you want PhpStorm to wait for a result from Laravel Pint. If the timeout is exceeded, the process is terminated to prevent excessive CPU and memory usage. This lets you fine-tune the Laravel Pint process behavior depending on the configuration of your computer and the rule sets used.

29 May 2026