SQL formatter & minifier

Readable SQL in, tight SQL out.

A real parser, not a regex. Beautify messy queries, minify them for transport, strip comments, convert keyword casing, lint for unbalanced brackets, and wrap the result in a string literal for your language. Everything runs locally — nothing is uploaded.

Input

Output

Formatted SQL appears here.

in 0 B out 0 B change — lines 0 statements 0 tokens 0 status ready

Formatting options

Indentation

Keyword case

Function case

Identifier case

Comma position

List items on own line

Wrap brackets wider than

AND / OR on new lines ON clause on its own line

Blank line between statements Strip comments when minifying

Minify: one statement per line Reformat as I type

Drop it into your codebase

Embed as a string literal

Takes whatever is currently in the output pane and escapes it for your language, quotes and backslashes handled.

Language

—

Faster without the mouse

What this tool does

Format

Tokenises the statement properly, so strings, comments, quoted identifiers and dollar-quoted blocks are never mangled. Clauses break onto their own lines, joins align, subqueries indent, and CASE blocks nest.

Minify

Collapses to the shortest safe form, keeping a space only where removing it would change meaning. Comments can be stripped or kept, and the status bar shows exactly how many bytes you saved.

Case conversion

Keywords, functions and identifiers each get their own casing rule, so you can uppercase SELECT while leaving customer_id exactly as written.

Lint

Flags unclosed brackets, unterminated strings, runaway block comments, trailing commas before FROM, and missing final semicolons — before your database does.

Dialects

Backticks for MySQL, square brackets for SQL Server, $$ blocks and :: casts for PostgreSQL, plus # comments where the dialect allows them.

Keyboard

⌘/Ctrl + Enter format · ⌘/Ctrl + M minify · ⌘/Ctrl + Shift + C copy output · Tab inserts an indent inside the editor rather than moving focus.

Reference

Formatting conventions used here

These are the defaults. Every one of them is adjustable in the options panel above.

Rule	What happens	Why
Clause keywords	Start a new line at the current nesting level	Makes the shape of a query scannable at a glance
SELECT list	One column per line, indented once	Keeps diffs to a single line when a column is added
JOIN … ON	JOIN at clause level, ON indented below it	Separates what you're joining from how
AND / OR	New line, indented under the condition	Predicate order becomes reviewable
Subqueries	Bracket opens, contents indent, bracket closes on its own line	Nesting depth is visible without counting brackets
Short brackets	Stay inline when under the wrap width	`IN (1, 2, 3)` gains nothing from three lines
CASE blocks	WHEN and ELSE indent, END returns to the CASE level	Branches line up so a missing one is obvious
Statements	Separated by a blank line after each semicolon	Scripts read as a sequence rather than a wall

Questions

Common questions

Is my SQL sent anywhere?

No. The parser, formatter and minifier all run in your browser as plain JavaScript. There is no network call at any point, which is the main reason this is safe to use with production queries that contain real table names, schemas or embedded values.

Why minify SQL at all?

Three common reasons: shrinking queries that travel over the wire on every request, fitting a statement into a single line for a log entry or a config value, and normalising whitespace so two queries can be compared for equality. It also strips comments, which matters if those comments mention internals you don't want shipped to a client.

Will minifying change how my query behaves?

It shouldn't. Whitespace outside of string literals and quoted identifiers is not significant in SQL, and the minifier keeps a space wherever removing one would join two tokens together. The one thing to watch is comments: line comments run to the end of a line, so if you keep them while collapsing everything onto one line, the parser preserves the newline after each one rather than commenting out the rest of your query.

Does it validate my SQL?

It lints rather than validates. It will catch unbalanced brackets, unterminated strings, unclosed block comments and trailing commas — the structural mistakes that stop a statement parsing at all. It does not know your schema, so it cannot tell you a column is misspelled or a join condition is wrong.

Should keywords be uppercase?

It's a convention, not a rule — SQL keywords are case-insensitive. Uppercase keywords with lowercase identifiers is the most widely used style because the contrast makes structure pop without any syntax highlighting. Some modern teams prefer all-lowercase for a quieter look. What matters is that a codebase picks one, which is why keyword, function and identifier casing are three separate settings here.

Leading or trailing commas?

Trailing commas read more naturally. Leading commas make it harder to leave a dangling comma behind when you delete the last column of a SELECT, which is a genuinely common error, and they keep version-control diffs to one line. Both are supported.

What else can you check?

Everything here runs in your browser the same way this formatter does — no upload, no account, no waiting.

Want to see the full path to a site? DNS, redirects, every hop, the CDN, TLS and the origin server. Want to know your public IP? See your IPv4 and IPv6 addresses, location, ISP and ASN. Want to check your tower & route? Live ping, speed, DNS, traceroute and a map of nearby points. Want to ping from around the world? Real latency from real probes across 12 countries, live on a map. Want to locate any IP address? City, region, country and coordinates for any public IP. Want to know if an IP is risky? Proxy, VPN, Tor, hosting and abuse-report indicators. Want to know if you're blacklisted? Check an address against major spam and abuse DNSBLs. Want to know who owns an IP? Network owner, ASN, CIDR range and abuse contact. Want to explore an AS number? Announced prefixes, BGP neighbours and registry details. Want to test your connection speed? Measure real download, upload, ping and jitter. Want to see what changed? Word-level diff between two blocks of text or code. Want to know if a DNS change is live yet? Compare answers from five independent public resolvers.

Copied

Drop a .sql file to load it