Skip to content
Allin
Sign up · Sign in

SQL Formatter

Format SQL queries with uppercased keywords and clause-by-clause line breaks for readability.

Related tools

All JSON, XML & formats tools →
ISO 8601 Date FormatterTurn any date, time and UTC offset into ISO 8601, RFC 3339, week/ordinal date, RFC 2822, HTTP date and Unix timestamps.XML Formatter / ValidatorPretty-print, minify and check whether XML is well-formed, all in your browser.YAML Formatter / ValidatorTidy YAML — normalize indentation, convert tabs to spaces and flag tab-indent errors.JSON formatterFormat, beautify or minify JSON — with instant validation.SQL IN clause generatorTurn a list of values (one per line) into a SQL IN (...) clause.CSS BeautifierReformat minified or messy CSS into clean, properly indented rules — or minify it back.HTML BeautifierTurn minified or tangled HTML into cleanly indented, readable markup — or minify it.JavaScript Minifier / BeautifierMinify or beautify JavaScript in your browser, with a tokenizer that respects strings, regex and comments.

SQL Formatter works straight from this page — free, instant, nothing to install. You will find it under JSON, XML & formats, with ISO 8601 Date Formatter and XML Formatter / Validator for the neighbouring cases.

How to use it

  1. Open the tool — no signup or install needed.
  2. Enter your input or adjust the available options.
  3. Get your result instantly, then copy or download it.

Frequently asked questions

What does SQL Formatter do?

Format SQL queries with uppercased keywords and clause-by-clause line breaks for readability.

When would I actually use this?

Making a machine-generated blob readable, finding the character where a parse fails, and shrinking a file before it ships.

What is the most common mistake?

Assuming valid means correct. A document can parse cleanly and still have the wrong shape for whatever will read it — validation checks the syntax, not the schema.

Is there a tool for the next step?

XML Formatter / Validator is the closest one after this: Pretty-print, minify and check whether XML is well-formed, all in your browser.

What else is worth having open alongside it?

YAML Formatter / Validator and JSON formatter — they come up in the same task often enough to be worth a second tab.

Where do the figures come from?

Parsing and serialisation follow each format's specification. Key order and whitespace are not semantically meaningful in JSON or YAML, so a reformatted document is equivalent even when the bytes differ.

Further reading

All guides →
GuideSQL Formatting and the IN Clause That Breaks ProductionBuilding an IN list by string concatenation is both the classic injection vector and a performance cliff. Parameterisation fixes the first structurally, because the plan is compiled before any value arrives. The second needs arithmetic: the vendors' documented parameter ceilings, and what a query whose text changes with every list length does to a plan cache.ExplainerXML to JSON: Attributes, Repetition, and the Single-Element Array TrapTwo documents that differ only in how many children exist produce two different JSON shapes, and no converter can tell them apart without a schema. Plus what this one really does with attributes, mixed content and whitespace — and the one thing it still cannot record.ExplainerYAML Looks Friendly and BitesYAML is JSON plus a type-inference layer, and the inference is the dangerous part. The same file run through a YAML 1.2 parser and a YAML 1.1 parser: no is a string in one and false in the other, 01234 is 1234 in one and 668 in the other, and 12:30:00 is a number in one of them.GuideWhat a Minifier Can Remove, and What It Must NotMinification has to preserve meaning, and the interesting part is the whitespace that carries meaning: the descendant combinator, the spaces inside calc(), the gap between two inline elements. Measured here on real files, including how much brotli was going to save you anyway.GuideBeautify or Minify: What Each Is For, and What It Does to the WeightFour real stylesheets run through the minifier, measured raw and after gzip. Stripping every space saved 48, 103, 104 and 147 compressed bytes; stripping comments saved 57, 1 358, 2 420 and 1 042. Plus the five inputs this minifier breaks.ComparisonJSON vs XML: What's the Difference?JSON and XML both store structured data as text, but they trade off differently. Here's how each looks, where each wins, and how to choose.