SQL formatter
ClientPaste a query and choose a dialect when you can—output stays in your tab for copy and review.
SQL
?
Pretty-print only—pair with the Compress page for SQL minify. Pick a dialect that matches your engine when possible.
Input
Formatted
Common use cases
- Turn a minified or one-line query into indented SQL for code review or documentation.
- Match a dialect when the formatter supports it so keywords and strings align with your database.
- Pair with SQL minify on the compress page when you need the smallest payload for embedding.
Common mistakes to avoid
Expecting identical output across every database
Dialects differ. If something looks wrong, try another dialect preset or format manually for vendor-specific syntax.
Formatting secrets into shared screenshots
Queries may contain passwords or tokens. Redact before pasting into chats or tickets.
Relying on the formatter to validate semantics
Pretty output can still be invalid for your engine. Run explain or tests on the real database when it matters.
FAQ
Is my SQL sent to Toolcore servers?
No. Formatting runs in your browser tab.
Where is SQL minify?
Use the compress & minify tool and choose the SQL tab for a smaller single-line form.
Why does my stored procedure look odd?
Complex procedural extensions may not match every dialect preset. Treat output as a starting point.
More tools
Related utilities you can open in another tab—mostly client-side.
Compress & minify
ClientHTML, JS, CSS, XML, SQL, JSON minify; batch JPEG/WebP image compression.
JSON formatter
ClientJSON format online: pretty-print, minify, validate, escape, download .json.
JSON → SQL INSERT
ClientINSERT statements from a JSON array of objects—escaped strings, local only.
Encoding tools
ClientBase64 and URL on this page; hub lists hex, HTML entities, JWT, JSON helpers, crypto, and tokens.