SQL Formatter with Uppercase Keywords

What is a SQL formatter?

A SQL formatter takes a query that has collapsed into one long line — copied from application logs, an ORM's debug output, or a slow-query report — and lays it out with each major clause (SELECT, FROM, WHERE, JOIN, GROUP BY, ORDER BY) on its own line, with keywords uppercased for consistency. The structure of the query becomes visible: what's being selected, which tables are joined, and where the filtering happens.

Formatting runs entirely in your browser. Queries often embed real data in their literals — customer emails, IDs, internal table names — and none of it is uploaded, stored, or logged here.

When to use it

The most frequent trigger is a query you didn't write: an ORM-generated statement from Hibernate or Prisma logs, a query captured in a slow-query log, or a monster SELECT a teammate pasted into chat. Formatting it is the first step of understanding it — you can't reason about join order or spot a missing WHERE condition in a 400-character line.

It's also useful before committing: raw SQL in migrations, report definitions, and analytics notebooks lives longer than most application code, and consistent clause-per-line layout with uppercase keywords makes future diffs reviewable. When a code review comment says "what does this query actually do?", pasting a formatted version — or better, the permalink that reproduces it — usually answers the question.

Example

Paste select u.name, count(o.id) from users u left join orders o on o.user_id = u.id where u.active = 1 group by u.name order by 2 desc and Format returns it with SELECT, FROM, LEFT JOIN, WHERE, GROUP BY and ORDER BY each starting a new line, keywords uppercased. The reshaped query makes it obvious at a glance that this is a per-user order count over active users. Use "Copy link to this result" to share a permalink that restores the exact query for whoever opens it — handy in code reviews and bug reports.