Does this tool validate SQL?

No. The SQL Formatter only reformats whitespace, indentation, and keyword casing. It does not parse or validate SQL syntax. Invalid SQL will still be formatted as-is without error messages about syntax problems.

SQL Formatter

Format and prettify SQL queries -- free, private, runs entirely in your browser

Indent: Uppercase keywords Dialect:

Input SQL

Formatted Output

Your SQL never leaves your browser. No server, no logging, no account.

Why Format SQL?

Raw SQL written under deadline pressure or copied from logs is often a wall of text with inconsistent casing, no indentation, and keywords crammed onto the same line as their clauses. Formatted SQL is dramatically easier to read, debug, and maintain.

Readability -- each major clause on its own line, indented JOIN conditions and subqueries
Debugging -- spotting a missing JOIN condition or wrong WHERE predicate is much faster when each clause is isolated
Code review -- reviewers can follow the logic of a query without mentally parsing run-on text
Version control diffs -- consistent formatting means git diff shows only real logic changes, not whitespace noise
Onboarding -- new team members understand a schema or query faster when it follows a predictable layout

SQL Formatting Conventions

There is no single standard, but these conventions are widely followed and what this tool applies:

Keyword casing -- write SQL keywords in UPPERCASE (SELECT, FROM, WHERE) and table/column names in lowercase or mixed case. This visually separates language constructs from data identifiers.
One major clause per line -- each of SELECT, FROM, WHERE, GROUP BY, ORDER BY, HAVING, LIMIT starts on a new line.
Indent JOIN conditions -- the ON clause and joined table are indented relative to the JOIN keyword.
AND/OR on new lines -- boolean operators within WHERE and HAVING start on their own indented line for easy scanning.

Example -- unformatted:

select u.id,u.name,o.total from users u join orders o on u.id=o.user_id where o.total>100 and u.active=1 order by o.total desc limit 10

Example -- formatted:

SELECT
  u.id,
  u.name,
  o.total
FROM users u
JOIN orders o
  ON u.id = o.user_id
WHERE o.total > 100
  AND u.active = 1
ORDER BY o.total DESC
LIMIT 10

Supported SQL Statements

This formatter handles the most common SQL constructs found in application code and data work:

SELECT -- including column lists, aliases, DISTINCT, TOP
INSERT INTO ... VALUES and INSERT INTO ... SELECT
UPDATE ... SET with WHERE conditions
DELETE FROM with WHERE conditions
CREATE TABLE with column definitions and constraints
ALTER TABLE -- ADD COLUMN, DROP COLUMN, ADD CONSTRAINT
DROP TABLE / DROP INDEX / DROP VIEW
JOIN variants -- INNER JOIN, LEFT JOIN, RIGHT JOIN, FULL OUTER JOIN, CROSS JOIN
Subqueries -- nested SELECT in FROM, WHERE, and SELECT list
CTEs (WITH clauses) -- common table expressions for readable multi-step queries
Window functions -- OVER, PARTITION BY, ORDER BY inside OVER, ROW_NUMBER, RANK, DENSE_RANK, LAG, LEAD
UNION / INTERSECT / EXCEPT -- set operations between SELECT statements
CASE WHEN ... THEN ... ELSE ... END
Aggregate functions -- COUNT, SUM, AVG, MIN, MAX, COALESCE

Frequently Asked Questions

Does this validate SQL?

No. The formatter only adjusts whitespace, indentation, and keyword casing. It does not parse the SQL grammar or check for syntax errors. If your query has a typo or a missing parenthesis, it will be formatted as-is without any warning about the syntax problem.

Which SQL dialects are supported?

The tool supports Standard SQL and extends keyword recognition for MySQL and PostgreSQL when you select those dialects. The dialect setting primarily affects which words are treated as keywords for highlighting and casing -- the core formatting logic (clause placement, indentation) is the same across all three.

Is my SQL sent to a server?

No. All formatting runs in JavaScript directly in your browser tab. Your SQL query never leaves your machine. There is no backend server processing your queries, no usage logging, and no account required.