Which SQL dialects are supported?

PostgreSQL, MySQL, SQL Server, Oracle, SQLite, BigQuery, and ANSI SQL. Pick the one that matches your database so dialect-specific keywords format correctly.

Are keywords always uppercased?

By default, yes — uppercase keywords are the convention in most style guides and make the structure of a query scan-able. You can toggle to lowercase or preserve-case if your team uses a different style.

Can it format complex queries with CTEs?

Yes. CTEs (WITH clauses), subqueries, window functions, and recursive queries all get correct indentation and clause alignment. The formatter understands the structural hierarchy of the query.

Will formatting change the behavior of my SQL?

No. The formatter only changes whitespace and capitalization. Tokens, operators, identifiers, and string literals are preserved verbatim. The query you paste runs identically after formatting.

Is my SQL sent to any server?

No. Formatting runs entirely in your browser. The query never leaves the page.

SQL Formatter — Free Online Tool

SQL Formatter & Beautifier

Private by design — runs entirely in your browser

Format and pretty-print SQL queries in your browser. Toova uppercases keywords, aligns clauses, and indents subqueries into readable form — useful when reviewing dense queries from logs, ORMs, or other developers.

Why format SQL

Dense single-line SQL is unreadable. Aligned, indented SQL with uppercase keywords is what every senior database engineer writes by hand. Toova does the formatting automatically — paste a query from a slow log, an ORM dump, or a colleague, and get back something you can actually review. Joins, subqueries, CTEs, and window functions all get clear visual hierarchy.

Dialect-aware

SQL has dialects — PostgreSQL, MySQL, SQL Server, Oracle, SQLite, BigQuery — and each one has its own keywords and syntax extensions. Toova lets you pick the dialect so dialect-specific keywords (RETURNING, LATERAL, MERGE) are recognized and formatted correctly. The default is ANSI SQL, which handles most common queries.

Local-only

Formatting happens entirely in your browser. The SQL you paste — including queries that reference internal table names, customer IDs, or anything proprietary — never leaves the page. The Network tab will stay empty during formatting, and the page works offline after first load. Safe for slow-log queries, debugging, and code review.

Frequently Asked Questions

Which SQL dialects are supported?: PostgreSQL, MySQL, SQL Server, Oracle, SQLite, BigQuery, and ANSI SQL. Pick the one that matches your database so dialect-specific keywords format correctly.
Are keywords always uppercased?: By default, yes — uppercase keywords are the convention in most style guides and make the structure of a query scan-able. You can toggle to lowercase or preserve-case if your team uses a different style.
Can it format complex queries with CTEs?: Yes. CTEs (WITH clauses), subqueries, window functions, and recursive queries all get correct indentation and clause alignment. The formatter understands the structural hierarchy of the query.
Will formatting change the behavior of my SQL?: No. The formatter only changes whitespace and capitalization. Tokens, operators, identifiers, and string literals are preserved verbatim. The query you paste runs identically after formatting.
Is my SQL sent to any server?: No. Formatting runs entirely in your browser. The query never leaves the page.