Review an extraction for a report
Identify selected columns, source tables, filters and ordering. Clear layout supports examining the logic without checking which data actually exists.
SQL formatter
Format queries using the formatter’s general SQL dialect without a database connection. Processing runs locally in your browser.
- Clipboard
- Export
Data not sent
This query could not be formatted. Check its syntax and any dialect-specific SQL constructs.
Result
Was this tool useful?
How does this tool work?
SQL copied from a log may fit on one line while hiding its structure. This formatter separates clauses, lays out expressions and capitalizes recognized keywords for easier review. It never connects to a database or executes instructions: SELECT, INSERT and DELETE remain text. Use it to understand a query before investigating it in your own environment, prepare a code review or publish a readable example. Query names and literal values are processed on your device.
The engine recognizes SQL tokens instead of globally replacing words such as from and where. A quoted SQL string containing those words stays a literal value rather than being capitalized as a clause. Expressions and lists use two-space indentation.
The form uses the formatter’s general SQL mode. It currently has no PostgreSQL, MySQL, T-SQL or other dialect selector. Vendor extensions, unusual identifier quoting, procedural blocks and parameters may be rejected or laid out differently from your usual tooling. The ISO reference describes SQL’s framework; it does not certify this parser for every database.
Successful formatting is not server validation. The engine knows nothing about your tables, columns or account permissions. A readable statement can still reference nonexistent objects, return unintended results or affect more rows than expected.
Formatting does not reorder clauses to optimize execution plans or recommend indexes. It does not parameterize a query either: handling user-supplied values remains your application’s responsibility. Retain bound parameters wherever your driver supports them.
How to use this tool
Paste the SQL query
Import a .sql file or paste instructions without log prefixes. Check that strings and comments are complete before requesting layout.
Format in general SQL mode
Run formatting and inspect the recognized clauses. If it fails, check syntax and dialect-specific extensions. No statement has been sent to a database.
Compare before reuse
Review literals and conditions before copying or downloading the .sql result. Editing the input hides the previous output so different versions are not confused.
Use cases
Prepare a query review
Separate clauses to discuss a condition or join. Remove sensitive values before sharing the excerpt, even though formatting happens locally.
Describe a minimal reproduction
Reduce a query to the relevant example before formatting it for a technical issue. This tool does not create the tables or records required to reproduce it.
Examples
Retain keyword text inside a string
SELECT, FROM and WHERE are recognized as clauses. The literal from where select stays unchanged because it is data enclosed in quotes.
Input
select 'from where select' as label from items where id=1Result
SELECT
'from where select' AS label
FROM
items
WHERE
id = 1Lay out a column list and ordering
id and name appear separately, with FROM and ORDER BY structuring the query. Column order and the implicit sorting direction are not rewritten.
Input
select id,name from users order by idResult
SELECT
id,
name
FROM
users
ORDER BY
idTips and best practices
- Validate statements in a test database using the correct dialect before running them against important data.
- Comments can contain engine-specific instructions. Inspect them and vendor extensions rather than treating layout as proof of compatibility.
- Investigate slow queries with your database’s execution plan. Formatting cannot reveal actual operation costs.
- Table names, addresses and filter literals can expose internal details in a shared example; anonymize them deliberately.
Sources and references
- ISO/IEC 9075 — Database languages SQL (opens in a new tab), ISOPage in English
Frequently asked questions
Does the formatter execute my query?
No. It processes text without a database connection. Update and deletion statements are never executed by this tool.
Why can syntax accepted by my database be rejected?
This form uses general SQL mode. Not all proprietary extensions and procedural constructs are recognized. Use your environment’s formatter when those features are essential.
Are keywords inside strings changed?
No. Literals are distinguished from clauses, preventing a naive replacement of from or where inside data. Still inspect the excerpt before adding it to a project.
Is formatted SQL faster or protected against injection?
Layout changes neither the database’s execution plan nor how user values are bound. Performance and injection prevention require separate checks in the application and database engine.
Related tools
Keep going with these tools
Tools similar or complementary to this one.
Similar tools
Generate SQL INSERT statements from Excel, CSV, or JSON.
DevelopmentUse this tool
Generate realistic fake datasets in JSON, CSV or SQL.
DevelopmentUse this tool
Generate TypeScript interfaces, types, Zod schemas, or JSON Schema from sample JSON.
DevelopmentUse this tool
Read next
GuideConcepts and technologiesIntermediate
ISO week, Unix timestamp and dates in computing: understanding time representations
Understand ISO 8601 week numbers, Unix timestamps in seconds or milliseconds, and the difference between human-readable dates and technical time values.
28 August 20264 min