Does this support multiple SQL dialects?

The formatter is dialect-friendly: it keeps string literals, quoted identifiers, and comments untouched, so MySQL, PostgreSQL, SQL Server, and SQLite queries all format correctly.

Can I minify a SQL query?

Yes — the minify mode collapses whitespace to a single line while preserving string literals and comments.

What does the SQL linter check?

It flags UPDATE or DELETE without WHERE, SELECT *, comparisons with NULL, unbalanced parentheses, trailing commas, NOT IN (NULL), and dialect-specific mistakes such as LIMIT in Oracle or SQL Server. Warnings are heuristics, not a replacement for database-level checks.

How do I see the query execution plan?

Choose your database or leave auto-detect on, then copy the generated EXPLAIN command. Oracle uses EXPLAIN PLAN with DBMS_XPLAN, PostgreSQL uses EXPLAIN (ANALYZE, BUFFERS), MySQL uses EXPLAIN ANALYZE, and SQL Server uses SHOWPLAN_ALL.

SQL Formatter & Beautifier

Format messy SQL into readable, indented queries with uppercase keywords — or collapse it to a single line. Review risky statements, then copy the right EXPLAIN command for your database. String literals and comments are always preserved.

Dialect

SQL input

Formatted

SELECT u.id, u.email, count(o.id) AS orders
FROM users u
LEFT JOIN orders o
ON o.user_id = u.id
WHERE u.created_at >= '2024-01-01' AND o.status = 'paid'
GROUP BY u.id, u.email
HAVING count(o.id) > 1
ORDER BY orders DESC
LIMIT 10;

Original: 229 B Output: 229 B

Query review (MySQL / MariaDB)

0 errors0 warnings0 tips

No issues found. The linter checks structure and common risks, not syntax or permissions.

Warnings are heuristics based on the statement text. Always validate destructive changes in a transaction or on a copy before running them against production.

Execution plan command

Run this in your database client to see how the optimizer plans the query.

EXPLAIN ANALYZE
select u.id, u.email, count(o.id) as orders
from users u
left join orders o on o.user_id = u.id
where u.created_at >= '2024-01-01'
and o.status = 'paid'
group by u.id, u.email
having count(o.id) > 1
order by orders desc
limit 10;

EXPLAIN ANALYZE runs the query and reports actual timings (MySQL 8.0.18+). On older versions use EXPLAIN and check the key and rows columns.

What the formatter does

Keywords — uppercases clauses like SELECT, FROM, and ORDER BY.

Layout — starts each clause on a new line and indents subqueries and parentheses.

Safety — string literals, quoted identifiers, and comments are never touched.

Frequently asked questions

Does it support my database dialect?

Yes. Because literals are protected first, the output is safe across MySQL, PostgreSQL, SQL Server, SQLite, and Oracle. Quoted string prefixes like E'…' and N'…' are handled too.

What does the query review check?

It scans the statement for UPDATE or DELETE without WHERE, SELECT *, comparisons with NULL, trailing commas, unbalanced parentheses, NOT IN (NULL), and dialect mistakes such as LIMIT in Oracle or SQL Server. Treat the results as a safety checklist, not a full SQL parser.

Which EXPLAIN command is generated?

Auto-detect or pick Oracle, PostgreSQL, MySQL, or SQL Server. The tool outputs EXPLAIN PLAN with DBMS_XPLAN, EXPLAIN (ANALYZE, BUFFERS), EXPLAIN ANALYZE, or SHOWPLAN_ALL respectively.

Is my SQL sent anywhere?

No. Formatting and review happen entirely in your browser — paste any query, including ones with sensitive data, without worry.

Why uppercase keywords?

Uppercase keywords make a query's structure (SELECT vs FROM vs WHERE) visible at a glance, which is the convention in most style guides and database documentation.

Build custom software with us

From internal tools to full platforms — we deliver end to end.

Start a Project

Was this tool useful?

Runs in your browser — nothing is uploaded.