Paste a messy or one-line SQL query and get it back with each clause on its own line and everything indented. Pick your database dialect, choose the indentation, and copy the clean result. Everything runs in your browser, so your query stays on your device.
SQL queries often get written or copied as one long line, which is hard to read and easy to make mistakes in. A formatter rewrites the query with each clause on its own line and the parts indented, so the structure of the query is clear at a glance. It does not change what the query does, only how it is laid out. This tool formats your SQL for the database you choose and can put the keywords in uppercase.
Rewrites your query on multiple lines with each clause on its own line and the parts indented. Long, one-line queries become easy to read and review.
select id,name from users where active=1AfterSELECT
id,
name
FROM
users
WHERE
active = 1Pick the database you are writing for, such as MySQL, PostgreSQL, SQLite, or SQL Server. The formatter follows that dialect's keywords and quoting.
MySQL, PostgreSQL,
SQLite, SQL Server...AfterFormatted for your
chosen databaseWrites SQL keywords like SELECT, FROM, and WHERE in capitals, which is the common house style. Turn it off to keep your keywords exactly as typed.
select id from usersAfterSELECT id FROM usersChoose 2 or 4 spaces for each level of indentation, so the result matches the style used in the rest of your project.
2 spaces or 4 spacesAfterYour choice per levelDatabases agree on the basics but differ in the details, especially in how they quote names. Picking the right dialect helps the formatter read your query the way your database will:
| Database | Quotes names with | Example |
|---|---|---|
| MySQL | Backticks | SELECT `order` FROM `sales` |
| PostgreSQL and SQLite | Double quotes | SELECT "order" FROM "sales" |
| SQL Server | Square brackets | SELECT [order] FROM [sales] |
Text values use single quotes in every dialect: WHERE name = 'Sam'. Standard SQL works for most simple queries when you are not sure which dialect you have.
The formatter only changes the layout. It does not know your tables, so a query that formats cleanly can still fail when you run it because of a misspelled column or a missing table. It will even lay out an unfinished query like SELECT * FROM without complaint.
Formatting is still one of the best ways to find mistakes by eye. Once each clause is on its own line, a missing join condition, a stray comma, or a filter in the wrong place is much easier to spot.
A formatter helps any time a query is hard to read. These are the cases that come up most: