SQL Formatter
Pretty-print a SQL statement.
How to use SQL Formatter
Uppercase SQL keywords and break major clauses onto their own lines for readable queries.
Open SQL Formatter on toolpermarket, then enter the values you want to work with.
In the SQL field, paste a single SQL statement to pretty-print. Keywords are recognised case-insensitively and uppercased.
Press Format to compute the result. The output appears immediately below the form. Tweak any field and run it again to check a different scenario.
Read the result and use it as needed. If the number looks off, re-check your inputs and run it again — the math is deterministic, so the same entries always return the same answer.
Worked example. "select id,name from users where age>18 order by name desc" becomes a readable multi-line query with each clause on its own line.
Tips for accurate results.
Major clauses (SELECT, FROM, WHERE, GROUP BY, ORDER BY, JOINs, etc.) each start on a new line.
Keywords are uppercased so the query reads consistently regardless of how you typed it.
It is a formatter, not a validator — it will lay out invalid SQL too, so still test the query.
When to use SQL Formatter. Cleaning up a query copy-pasted from logs or a teammate. Making a long statement reviewable in a code review. Normalising SQL before saving it to a migration file.
When you actually reach for this
- You are reviewing a long, single-line query from a log or ORM and need to see joins and clauses clearly.
- You want a consistent layout for SQL in docs or PRs so the structure is scannable.
Where this tool stops being accurate
- Formatting does not validate the query — a malformed statement is laid out as best-effort and may still error at runtime.
- Dialect matters: keyword casing and function names differ between MySQL, Postgres, and SQL Server, so pick the right dialect.
Frequently asked questions
Which clauses get their own line?
The common ones: SELECT, FROM, WHERE, GROUP BY, HAVING, ORDER BY, LIMIT, OFFSET, the JOIN variants, UNION, and the write clauses INSERT/UPDATE/DELETE. Each starts on a fresh line.
Does it change my query logic?
No. It only adjusts whitespace and the case of keywords; it does not rewrite expressions, rename identifiers, or alter what the statement does.
Will it catch syntax errors?
No. It is a formatter, not a parser. It will neatly print malformed SQL just as happily as correct SQL, so always run the formatted query against your database to be sure.
Will reformatting my SQL change the result?
No, whitespace is insignificant in SQL, so only readability changes. Just keep the same dialect selected so keywords are recognized.
Why does it flag my proprietary function as unknown?
The formatter only knows standard and selected-dialect keywords; vendor functions (like Postgres extensions) are treated as identifiers, which is fine for layout but not for validation.