Format SQL for easier review

Select the database's dialect

Choose Standard SQL, PostgreSQL, MySQL, or SQLite to match the source query. Quoting, operators, and vendor extensions differ. Paste a complete statement and select Run tool.

Formatting runs in the browser without a database connection. An unsupported construct can fail in the formatter even when the database accepts it. Preserve the original instead of removing syntax just to satisfy a formatting parser.

Inspect each clause

Read selected columns, source tables, join conditions, filters, grouping, and ordering separately. A clear layout helps expose a broad filter or missing join condition, but the formatter does not identify these logic errors.

For UPDATE or DELETE, independently verify the intended scope before execution. For SELECT, consider duplicated rows from joins and filters involving nulls. Readability does not establish a correct result set.

Validate in the real environment

Compare original and formatted text if anything looks unexpected, especially comments and dialect-specific quoting. Formatting success says nothing about whether tables, columns, permissions, or indexes exist.

Use database explain facilities, test data, and your normal review process. Parameterize application inputs in application code; this formatter does not escape values or prevent SQL injection.

Worked example

select id from users where active = 1

select
  id
from
  users
where
  active = 1

Clauses become easier to scan. No database checked whether users or active exist.

SQL dialect:

sql

Open SQL Formatter