SQL Beautifier

From unreadable to clean

Beautifying SQL is the act of taking a query that was written for a machine and rewriting it for a person. Databases happily accept a statement crammed onto one line, but humans need structure: somewhere for the eye to rest, a clear separation between the columns you select and the tables you read from, and indentation that mirrors how deeply a sub-query is nested. A beautifier supplies all of that automatically.

The result is not just prettier — it is more reliable. When every clause sits on its own line you can see at once whether a JOIN is missing its ON condition, whether a filter accidentally landed in the wrong place, or whether two columns were duplicated. Messy SQL hides bugs; beautified SQL exposes them.

What gets cleaned up

• Random spacing and stray tabs are normalised into consistent indentation.
• Each major clause — SELECT, FROM, WHERE, GROUP BY, ORDER BY — starts a fresh line.
• Selected columns and WHERE conditions break onto their own lines so long lists stop scrolling sideways.
• Keywords are recased to a single convention while your identifiers keep the case you typed.
• Sub-queries inside parentheses are indented one level deeper than their parent.

Every one of those changes is purely cosmetic, which is exactly what you want from a beautifier: maximum readability, zero risk.

A quick example

This is the kind of query an application framework might log:

select p.id,p.title,c.name from posts p join categories c on c.id=p.category_id where p.published=1 order by p.created_at desc

After beautifying:

SELECT
  p.id,
  p.title,
  c.name
FROM
  posts p
  JOIN categories c
  ON c.id = p.category_id
WHERE
  p.published = 1
ORDER BY
  p.created_at DESC

The join condition is now impossible to miss, the columns read like a list, and the sort key stands on its own. Same query, completely different experience.

Beautify before you commit

A good habit is to beautify a query before it goes into a migration file, a stored procedure or a pull request. Consistent formatting makes code review faster because reviewers spend their attention on the logic, not on deciphering layout. It also keeps version-control diffs small and meaningful: when everyone runs the same beautifier, a change to one column shows up as a one-line diff instead of a reshuffle of the whole statement. Because this tool runs entirely in your browser, you can clean up even sensitive production queries without sending a single character to a server.