OpusDesk Hub What this tool does
Format common SQL keywords and whitespace with two- or four-space indentation. Quoted values, identifiers, comments and dollar-quoted bodies are preserved as entered. Unterminated protected segments are rejected. This heuristic formatter does not execute SQL or validate a database dialect.
How to use SQL Formatter
- Paste your SQL query. Paste SQL into the formatter input. Common keywords such as SELECT, FROM and WHERE can be reformatted; quoted values, identifiers, comments and dollar-quoted bodies are preserved. An unterminated protected segment produces an error.
- Choose formatting options. Choose two- or four-space indentation, then select Format. Recognized code keywords become uppercase; text inside protected segments keeps its original case and spacing.
- Copy the formatted output. Review the output before copying it. Formatting does not establish that a statement is valid or equivalent in your database dialect; use your database tooling for validation.
How this tool works
The component masks quoted values, identifiers, comments and dollar-quoted bodies, formats surrounding code, then restores the original segment bytes. It never executes the query.
- Engine: Protected-segment scanner with keyword and whitespace formatting rules
- Supported input: Common SQL code with quoted values and identifiers, line or nested block comments and dollar-quoted bodies
- Output: formatted SQL text
Worked example
Input: select id,name from users where active=1
Output: SELECT fields, FROM, and WHERE arranged on readable lines
Limits, edge cases, and troubleshooting
Use it to improve readability before review. Check vendor-specific functions and quoted identifiers after formatting.
- The statement must fit in browser memory.
- Unterminated quoted values, identifiers, block comments and dollar-quoted bodies are rejected.
- Formatting outside protected segments is heuristic; it does not validate a database dialect or the SQL inside a preserved body.
When to use another workflow
Use your database IDE or a dialect-aware parser for linting, query plans, schema validation, and automated repository formatting.
| Option | Best for | Trade-off |
|---|---|---|
| This browser tool | Quick, private, one-off work | Limited by browser memory and the documented feature set |
| Desktop or command-line tool | Batch jobs and repeatable automation | Requires installation and setup |
Supported inputs and limits
- Common SQL code with quoted values and identifiers, line or nested block comments and dollar-quoted bodies
- The statement must fit in browser memory.
- Unterminated quoted values, identifiers, block comments and dollar-quoted bodies are rejected.
- Formatting outside protected segments is heuristic; it does not validate a database dialect or the SQL inside a preserved body.
Frequently asked questions
What SQL dialects does the SQL formatter support?
The formatter applies heuristic keyword and whitespace rules; it is not a SQL parser or dialect validator. Quoted values and identifiers, line and nested block comments, and dollar-quoted bodies are preserved as entered. Unterminated protected segments are rejected. Use a dialect-aware tool to validate database-specific syntax.
Can the SQL formatter handle complex queries with multiple JOINs?
It can reflow common keywords and use parenthesis-based indentation, but it does not parse complete query structure. Review JOINs, subqueries and CTEs manually. Preserving a protected body does not validate the SQL inside it.
Is information sent to a server?
Tool inputs are processed in this browser. This product does not use analytics or send your input to an external API. Clicking an external website link still visits that website.