SQL Formatter Guide: Beautify & Format SQL Queries Online (2026)

Unformatted SQL is one of the most common sources of bugs and wasted developer time:

• Readability — A 50-line query on one line is unreadable. Proper formatting reveals the query structure at a glance.
• Bug detection — Missing JOINs, wrong WHERE conditions, and accidental cross joins are visible in formatted SQL but hidden in compressed queries.
• Code review — Reviewers can focus on logic instead of deciphering formatting. Consistent style eliminates "formatting-only" diffs.
• Maintenance — The next developer (or future you) needs to understand and modify the query. Readable SQL is maintainable SQL.
• Documentation — Well-formatted queries serve as their own documentation of data relationships.

Before (Unformatted)

SELECT u.id,u.name,u.email,o.order_id,o.total FROM users u INNER JOIN orders o ON u.id=o.user_id WHERE u.status='active' AND o.created_at>='2026-01-01' ORDER BY o.total DESC LIMIT 100;

After (Formatted)

SELECT
  u.id,
  u.name,
  u.email,
  o.order_id,
  o.total
FROM users u
INNER JOIN orders o
  ON u.id = o.user_id
WHERE u.status = 'active'
  AND o.created_at >= '2026-01-01'
ORDER BY o.total DESC
LIMIT 100;

Key Conventions

JOIN Formatting

SELECT
  c.customer_name,
  o.order_date,
  p.product_name,
  oi.quantity
FROM customers c
INNER JOIN orders o
  ON c.id = o.customer_id
LEFT JOIN order_items oi
  ON o.id = oi.order_id
LEFT JOIN products p
  ON oi.product_id = p.id
WHERE c.country = 'IN'
  AND o.order_date >= '2026-01-01';

Subquery Formatting

SELECT
  u.name,
  u.email,
  sub.total_orders
FROM users u
INNER JOIN (
  SELECT
    user_id,
    COUNT(*) AS total_orders
  FROM orders
  WHERE status = 'completed'
  GROUP BY user_id
  HAVING COUNT(*) > 5
) sub
  ON u.id = sub.user_id
ORDER BY sub.total_orders DESC;

A good SQL formatter supports dialect-specific syntax. ToolsArena's formatter handles MySQL, PostgreSQL, SQL Server, and standard SQL.

• SELECT * — Always list specific columns. SELECT * hides schema changes and transfers unnecessary data.
• One-liner queries — Any query with a JOIN or WHERE clause should be multi-line.
• Inconsistent casing — Mixing "Select", "SELECT", and "select" in the same codebase confuses everyone.
• No aliases — users.id repeated 10 times vs u.id — aliases make queries dramatically shorter and clearer.
• Magic numbers — WHERE status = 3 — use named constants or comments explaining what 3 means.
• Deeply nested subqueries — More than 2 levels of nesting = refactor to CTEs.

Essential Decisions

• Keyword casing — UPPERCASE (most common) or lowercase
• Indentation — 2 spaces or 4 spaces (pick one, enforce it)
• Comma position — Trailing column1, (more common) or leading , column1 (easier to comment out)
• Line length — 80 or 120 character max
• Alias convention — First letter (u for users) or abbreviation (usr)
• JOIN style — Always explicit (INNER JOIN, LEFT JOIN) — never implicit comma joins

Enforcement Tools

• SQLFluff — Open-source SQL linter with auto-fix (CI/CD integration)
• pgFormatter — PostgreSQL-specific formatter
• Pre-commit hooks — Auto-format SQL files before commit
• ToolsArena SQL Formatter — Quick formatting for ad-hoc queries without installing tools