SQL Formatter

Nobody reads a 400-character single-line query from an ORM log and enjoys it. Paste it above and get it back properly indented — keywords uppercased, clauses on their own lines, subqueries nested at the right depth — in the dialect you're actually working with: standard SQL, MySQL, PostgreSQL, SQLite, SQL Server, BigQuery or PL/SQL.

Formatting runs entirely in your browser, which matters when the query you're pretty-printing contains real table names and business logic you'd rather not paste into a stranger's server.

FAQ

Which SQL dialect should I pick?

Pick the database the query runs against. Dialects differ in identifier quoting, functions and keywords — MySQL backticks won't fly in PostgreSQL. When in doubt, standard SQL is a safe default.

Does the formatter also validate my SQL?

Formatting implies parsing, so grossly malformed SQL will fail with an error — but it checks syntax, not semantics. It won't tell you a column doesn't exist.

Is my query sent to a server?

No. Formatting is 100% client-side; the query never leaves your browser.