SQL Formatter

What is SQL?

SQL (Structured Query Language) is the standard language for working with relational databases. It’s used to query, insert, update, and delete data in databases like PostgreSQL, MySQL, SQLite, and SQL Server. SQL queries are written as text statements, and their readability depends heavily on how they’re formatted.

When SQL is generated programmatically, copied from logs, or pasted from external sources, it often arrives as a dense single line — keywords run together, indentation is absent, and subqueries are hard to follow. Reformatting it properly makes queries far easier to understand, debug, and share.

What Does This Tool Do?

This tool takes raw or minified SQL and formats it with consistent indentation, keyword capitalization, and line breaks. It supports standard SQL as well as common dialects. The result is clean, readable SQL that’s easier to review and modify.

How to Use This Tool

1. Paste your SQL query into the input area.
2. The formatted version appears immediately.
3. Adjust indentation size if needed.
4. Copy the result with the copy button.
5. For long queries, switch the View control to Output to read the formatted SQL at full width.

Common Use Cases

• Code review: Make a complex query readable before sharing it in a pull request or ticket.
• Debugging: Understand a query that was auto-generated by an ORM or query builder.
• Documentation: Format queries clearly before including them in documentation or reports.
• Learning: See well-formatted SQL to learn proper style and structure.

Before and After

A query as it typically arrives from a log or ORM:

select u.id,u.name,count(o.id) as orders from users u left join orders o on o.user_id=u.id where u.created_at>'2026-01-01' and u.status='active' group by u.id,u.name having count(o.id)>5 order by orders desc limit 20;

The same query formatted:

SELECT
  u.id,
  u.name,
  COUNT(o.id) AS orders
FROM
  users u
  LEFT JOIN orders o ON o.user_id = u.id
WHERE
  u.created_at > '2026-01-01'
  AND u.status = 'active'
GROUP BY
  u.id,
  u.name
HAVING
  COUNT(o.id) > 5
ORDER BY
  orders DESC
LIMIT
  20;

Same execution plan, radically different readability — the join condition, the two filters, and the aggregation threshold are now visible at a glance.

SQL Style Conventions Worth Adopting

• Uppercase keywords (SELECT, WHERE, JOIN) — visually separates structure from your identifiers.
• One column per line in long select lists — makes diffs reviewable when a column is added or removed.
• Leading AND/OR on condition lines — easy to comment out a single condition while debugging.
• Explicit JOIN … ON instead of comma joins — the join condition can’t be accidentally forgotten (the classic accidental cartesian product).
• Alias with AS — optional in most dialects but makes intent explicit.

Consistency matters more than any specific choice: a team that formats queries the same way reviews them faster.

Frequently Asked Questions