SQL Formatter

Long queries copied from logs, ORMs or reporting tools usually arrive as a single unreadable line. This formatter lays SQL out the way people read it: each clause — SELECT, FROM, JOIN, WHERE, GROUP BY — on its own line, columns and conditions indented beneath it, and statements separated. It reads the query with the grammar of the dialect you choose, so it understands backtick, bracket and double-quoted names, dollar-quoted strings and each database’s parameter style, and it never changes text inside strings or comments. Formatting only changes whitespace and, if you ask, the case of keywords — the query does exactly the same thing afterwards.

1. Choose your database’s dialect. Standard SQL works for most simple queries.
2. Pick keyword case — UPPER, lower, or as you typed it — and 2 spaces, 4 spaces or tabs.
3. Paste a query or a whole script. The formatted version appears as you type.
4. If a query can’t be parsed, the message says where. A more specific dialect often fixes it.
5. Copy the result.

• It formats SQL; it doesn’t check that a query is valid for your schema, or run it. A query can format cleanly and still fail on the database.
• Stored procedure bodies and vendor-specific procedural code (complex PL/SQL or T-SQL blocks) are formatted line by line and may not be laid out as neatly as plain queries.
• Templating syntax such as {{ jinja }} or ${variables} inside SQL may not parse; replace it with a placeholder first.
• Input is limited to 1 MB.
• Formatting happens in your browser with the open-source sql-formatter library. Queries — which can include table names, customer data in literals and business logic — are never sent anywhere or run against any database.

No. Only spaces, line breaks and — if you choose — keyword capitals change. String literals, quoted identifiers and comments are copied exactly, and SQL keywords aren’t case-sensitive.

Usually because the query uses syntax from a specific database, such as PostgreSQL’s :: casts, MySQL backticks or SQL Server square brackets, while the dialect is set to Standard SQL. Choose your database, and check for an unclosed bracket or quote near the position shown.

Either works. Upper-case keywords make the structure stand out and are traditional; many modern style guides use lower case. The important thing is that a codebase is consistent.

Yes. Multiple statements are formatted and separated by a blank line, and the footer shows how many statements it found.