Glossary › Developer basics

code formatter

A program that automatically standardizes the appearance of source code – indentation, line breaks, spaces – without altering its functionality.

In plain terms

Imagine ten people co-writing a long document, and everyone formats differently: one with double spacing, another without indentation, a third with tabs here and spaces there. The content is good, but reading is tiring. The code formatter is like a strict typesetting editor: with a single button press, it brings everything to the same format.

This is important for code because code is read far more often than it is written. If every file looks the same, developers can focus on logic rather than appearance, and team debates about where to place curly braces disappear.

The formatter only arranges the appearance, does not fix errors, and does not improve the program. Poorly functioning code functions just as poorly after formatting, only looking nicer.

In the AI era, it has taken on a new role: code written by coding agents is also passed through it, so the work of the machine and the human looks the same.

How it works

1. The formatter reads the source file and does not treat it as plain text; instead, it recognizes its structure: what is an instruction, what is a block, what is a pair of parentheses.
2. From this, it builds an internal draft, a so-called syntax tree, which preserves the code structure and comments but largely discards the original formatting.
3. It rewrites the code from the draft according to fixed style rules: consistent indentation, spacing and placement of empty lines, maximum line length for most tools, and the type of quotation marks.
4. It breaks overly long lines, removes unnecessary spaces, then writes the result back to the file.
5. In practice, this runs automatically: when you save in the editor, before you submit your changes, or in the shared automated check that rejects unformatted code.

An everyday example

Who is affected

A common misconception

Limits and risks

• It does not check whether the code is correct, nor does it help with poor naming or ill-considered structure.
• If you run it for the first time in an old project, it rewrites most files at once, making it harder to trace previous changes.
• If team members or agents use different formatters or settings, files get formatted back and forth, and real changes get lost in the noise.
• Syntactically incorrect, unfinished code cannot be processed by most formatters, causing them to stop with an error message.

Similar, but not the same

• linter – The linter searches the code for suspicious or error-indicating solutions and warns about them, while the formatter only rewrites the appearance.
• refactoring – Refactoring alters the internal structure of code, while formatting only adjusts line breaks and spacing.
• compiler – The compiler turns code into an executable program; the formatter returns the same code with a cleaner appearance.

Related concepts

A brief history

The automatic "pretty-printing" of code dates back to the early decades of programming. The template for today's uncompromising formatters was provided by the gofmt tool released with the Go language in 2009, while in web development, Prettier, released in 2017, popularized it.

Where things stand

By the end of 2026, code formatters are standard equipment in software development: most editors and verification processes have them built in. It is also a common step in coding agents' workflows to format the generated code using the project's formatter.

Status: 2026 November

Also known as

code formatter · code formatter tool · automatic code formatting · formatter · code formatter · formatter · pretty printer · autoformatter

Sources

• Wikipedia: Prettyprint
• Go documentation: gofmt
• Prettier – official documentation

This entry was machine-edited and has undergone machine expert review; the “In the news” section updates automatically from Agent Age stories.