What's the difference between this and the SQL Formatter?

Same underlying engine — this version adds indent-size and keyword-case controls so you can match a specific style guide instead of using fixed defaults.

Can I use lowercase keywords in production?

Yes — SQL keyword casing has no effect on execution in any major database. It's purely a readability convention.

SQL

SQL Beautifier

Reformat dense or minified SQL with your choice of indent width and keyword casing — useful for matching your team's style guide.

Paste your SQL

Indent size

Keyword style

Beautified output

SELECT p.name,
  p.price,
  c.name AS category
FROM products p
JOIN categories c ON p.category_id = c.id
WHERE p.price > 20
  AND p.in_stock = true
ORDER BY p.price DESC

How it works

This is the same clause-aware re-indenting engine as the SQL Formatter, with two style controls exposed: indent size (2 or 4 spaces) and keyword casing (UPPERCASE or lowercase). Use whichever matches your team's conventions.

As with the formatter, this reflows structure rather than validating correctness — it won't catch a typo in a column name, only make the query easier to read.

Examples

4-space, lowercase style

A common alternate house style.

select id,
    name
from users
where active = true

2-space, UPPERCASE style (default)

The most common convention.

SELECT id,
  name
FROM users
WHERE active = true

Frequently asked questions