Is my SQL uploaded anywhere?

No. The formatter runs entirely in your browser using JavaScript. Your query is never sent to a server, so it is safe to format queries that reference sensitive table or column names.

How accurate is the formatting?

The tool tokenises on whitespace, parentheses, and quotes, then emits each major clause (SELECT, FROM, WHERE, JOIN, GROUP BY, ORDER BY and so on) on its own line with the body indented. It re-lays-out the query but does not parse or validate the SQL, so it will not catch syntax errors.

Does it change string literals?

No. Quoted strings and identifiers ('...', "...", `...`) are detected during tokenisation and copied through verbatim, so their contents and casing are never altered.

Does it upper-case my table and column names?

No. Only recognised SQL keywords are upper-cased. Identifiers like table and column names keep whatever case you typed, so it is safe with case-sensitive databases.

Can I choose the indent width?

Yes. You can format with either 2 or 4 spaces of indentation for the indented clause bodies and continuation lines.

Does it support INSERT, UPDATE and DELETE?

Yes. It recognises the clauses of SELECT, INSERT, UPDATE and DELETE statements and lays each major clause onto its own line.

SQL Formatter & Beautifier

Paste a cramped one-line SQL query and get back a readable, reviewable layout. Each major clause goes on its own line, recognised keywords are upper-cased, and long conditions and select lists wrap onto indented continuation lines — ideal for pull requests, documentation, and debugging.

How it works

The formatter is a layout pass, not a parser:

Tokenise. The query is broken into tokens on whitespace, parentheses, and quote boundaries. Quoted strings and identifiers ('...', "...", `...`) are detected here and passed through untouched.
Line breaks. Major clauses — SELECT, FROM, WHERE, the JOIN family, GROUP BY, ORDER BY, LIMIT, and more — start a new line. AND/OR and commas in the SELECT list break onto indented continuation lines.
Casing. Only recognised keywords are upper-cased; your identifiers keep their original case.

Because it re-lays-out rather than validates, it will not flag syntax errors — but it also never changes what your query does.

Example

Input:

select id, name, email from users where active = true and country = 'GB' order by name

Formatted (2-space indent):

SELECT
  id,
  name,
  email
FROM users
WHERE active = true
  AND country = 'GB'
ORDER BY name

Note the string literal 'GB' is preserved exactly. It is privacy-first plain JavaScript — your query never leaves your device.