Databases

SQL Formatter

Format SQL queries in a readable way directly in the browser. The tool does not execute SQL; it only rearranges keywords, indentation and line breaks for better readability.

Input

Options

Analysis

No query formatted yet.
Characters 0
Tokens 0
Table hints 0
Parentheses -

This tool checks only simple structural hints. It is not a full SQL parser and does not execute database queries.

Formatted output

Ready

Formatting rules

  • Keywords such as SELECT, FROM, WHERE, JOIN and ORDER BY are detected.
  • Strings in single quotes, double quotes and backticks are preserved.
  • Comments can be kept or removed from the output.
  • The formatter is intended for typical queries, views, reports and debug output.
  • For complex dialect-specific SQL, review the result before production use.

How it works and where it stops

The formatter tokenizes the input locally. It recognizes keywords and common clauses such as SELECT, FROM, WHERE, JOIN, GROUP BY, ORDER BY, WITH and RETURNING. It then heuristically builds indentation, clause breaks, comma spacing, line breaks and optional comments.

The dialect selection is currently a guidance label; it does not activate a full PostgreSQL, MySQL, SQL Server or SQLite parser. The tool does not validate grammar, execute SQL or connect to a database. SQL that looks well formatted is therefore not automatically valid, safe or suitable for a particular dialect.

Strings, comments and examples

  • Single quotes, double quotes and backticks are treated as content; for example, SELECT 'SELECT FROM WHERE' AS text; remains a string rather than creating new clauses.
  • Doubled quotes and common backslash escapes are recognized. SELECT 'O''Brien'; should therefore not be split in the middle of the value.
  • Line comments with -- and block comments with /* ... */ can be kept or removed. Comment markers inside a string are not treated as comments.
  • Typical queries, joins, subqueries, CTEs and reports are good candidates for a quick readability pass; complex window functions, stored procedures, dynamic SQL and vendor-specific extensions require manual review.

Security and reuse

The tool executes no commands and does not send SQL text to a server. It does not replace parameter binding, permission design, transaction review, injection analysis or a domain review. Do not put credentials or production secrets into examples; inspect an export before sharing it.