Why does the SQL formatter fail on my query?

Most formatters still need input they can tokenize reliably. Broken quotes, incomplete comments, pasted shell prompts, or truncated SQL from logs can prevent formatting.

Does formatting validate that my SQL is correct?

No. It improves readability only. It does not validate schema names, execution plans, permissions, transaction safety, or runtime behavior.

Will this work as a Postgres SQL formatter and MySQL SQL formatter?

It can format many common statements from both dialects, but formatting support is not the same thing as full engine-level parsing or compatibility.

Why did keyword casing change?

SQL beautifiers often normalize keywords like `select`, `from`, and `join` for consistency. That is a presentation change, not a semantic one.

Can I safely paste sensitive queries here?

The tool runs in the browser, so formatting happens locally rather than on a server. You should still use normal judgment around secrets embedded directly in SQL text.

SQL Formatter

Format SQL queries locally with dialect-aware whitespace rules.

Dialect

Keyword case

Indentation

SQL input

Formatted SQL

SQL Formatter only adjusts whitespace and layout for the selected dialect. It is not a semantic validator, and output may normalize casing, line breaks, and spacing. Editing the SQL or changing any formatting option clears the current result until you format again.