Format a VS Code document or only the selected code

Choose the scope before formatting

Whole-document formatting can change lines outside the area you were editing. Selection formatting narrows the intended scope, but still depends on the formatter and language support. Decide which result you need before running the command, especially in a repository where formatting changes can obscure a small functional edit.

Check which formatter owns the file

A missing formatter, multiple available formatters or project-specific configuration can explain an unexpected result. Inspect the editor’s formatter choice rather than assuming the key combination guarantees a particular style. Extension and workspace settings can affect both the available formatting actions and their output.

Review the diff after the action

Formatting is an edit, so check the resulting changes before saving or committing them. Confirm that the expected scope was respected and that unrelated lines did not change unnecessarily. Practise on a disposable file if you are evaluating a new formatter or changing the project’s formatting configuration.

Review the resulting diff

Format a disposable example first, then inspect the diff before accepting a project-wide style change. A formatter can rearrange whitespace across many lines without changing the intended program logic. Confirm which formatter and project configuration produced the result before saving.

Documented commands for this workflow

Scroll the table sideways to see every column.

Keep going

• Expand and shrink a structured VS Code selection
• Comment VS Code lines without confusing line and block comments