Format PHP code following PSR-12 coding style with configurable indentation and brace placement.
Paste PHP source into this tool and it rewrites only the whitespace to follow PSR-12, the PHP-FIG extended coding style guide: four-space indentation, class and method braces on their own line, control-structure braces on the same line as the keyword, and spaces around operators. Strings and comments pass through unchanged. The usual surprise is how little the tool does: it cannot repair syntax errors, add a missing visibility keyword, or convert double quotes to single quotes, and switching to tabs or same-line braces quietly steps outside PSR-12.
A concrete input and expected output from the current implementation.
Input
<?php
namespace App;
class Greeter{
public function greet(string $who):string{
return "Hello, ".$who;
}
public function farewell():string{
return "Goodbye!";
}
} Expected output
<?php
namespace App;
class Greeter
{
public function greet(string $who): string
{
return "Hello, " . $who;
}
public function farewell(): string
{
return "Goodbye!";
}
} The class and method opening braces move to their own line, the body indents by four spaces, spaces appear around the concatenation operator and after the return-type colon, and blank lines are inserted where PSR-12 requires them: after the namespace declaration and between methods. The strings, the parameter list, and the identifiers are preserved exactly.
The output differs from the input only in indentation, spacing, and blank lines. String literals, comments, and identifiers pass through unchanged, because altering them could change what the program does. If the input does not parse - unbalanced braces, a missing semicolon - the tool cannot reliably tell where statements start and end, so confirm it reports the error instead of emitting shifted output.
The defaults implement PSR-12: four-space indentation; class, interface, and method opening braces on the next line; control-structure braces on the same line as the keyword; one space after keywords and around binary operators; one blank line between methods; and a blank line after namespace and use declarations. The indentation and brace-placement options exist for non-PSR-12 tastes - choosing them means the result will not match the standard.
PSR-12 limits lines to 120 characters, but it does not prescribe how to wrap a long argument list, and breaking a line is a judgment call the formatter will not make for you. Overlong lines are therefore left as-is. Wrap them by hand, or run phpcs with the PSR12 standard to get a list of every line that exceeds the limit.
No. PSR-12 requires every method and property to declare public, protected, or private, and a missing visibility is a common violation - but adding a keyword is a code change, not spacing, and the tool cannot know which of the three you intended. Add it yourself; a PSR-12 check will keep flagging the file until you do.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Format, validate, and beautify JSON with syntax highlighting and error detection.
Encode text or files to Base64 and decode Base64 strings back to their original form.
Format and indent SQL queries for better readability across all major dialects.
Convert HTML markup into clean Markdown syntax with support for tables and lists.
Write Markdown and see the rendered HTML output in real time with live preview.
Visualize unified diffs and patch files with color-coded additions and deletions.