Format first, then share
If your SQL contains customer data, internal table names, or business logic, format it locally first and redact anything sensitive before pasting it into docs or tickets. See how to format SQL queries safely for the full workflow.
What the SQL formatter changes
| Control | What it helps with |
|---|---|
| Keyword case | Use uppercase keywords for traditional SQL reviews or lowercase when that matches your project style. |
| Indent size | Choose 2 spaces, 4 spaces, or tabs so copied output fits your docs, tickets, or code review convention. |
| Minify SQL | Collapse a query after review when you need a compact value for a config field or tool input. |
| Diff workflow | Format both versions before opening the diff checker so meaningful query changes are easier to see. |