SQL Indentation: 2 Spaces, 4 Spaces, or Tabs? Formatting Standards

By Sharon Ben-Moshe · October 12, 2026 · 1 min read

Sharon Ben-Moshe is the founder of sqlfmt, a browser-based SQL formatter and validator with misspelled-keyword suggestions across PostgreSQL, MySQL, SQLite, SQL Server, and BigQuery.

Resolve the indentation debate in SQL. Compare 2 spaces, 4 spaces, and tabs. Learn clause alignment styles and subquery indentation depth.

Quick answer

The industry standard for modern SQL codebases is 2 spaces per indentation level. While 4 spaces and tabs remain common in legacy environments, 2-space indentation prevents wide horizontal scrolling in nested CTEs, window functions, and subqueries while rendering consistently across git diffs, terminals, and code review tools.

FAQs

Why do modern SQL style guides prefer 2 spaces over 4 spaces?

SQL queries frequently nest multiple clauses (WITH, SELECT, FROM, JOIN, ON, WHERE, GROUP BY, HAVING, ORDER BY). With 4 spaces, deeply nested subqueries and CASE statements quickly exceed 100 characters per line, forcing horizontal scrolling.

Why are tabs problematic in SQL scripts?

Different tools and editors interpret tabs differently (rendering them as 2, 4, or 8 spaces). In Git pull requests and terminal diffs, tab misalignment disrupts clause visual hierarchy.

What is 'river alignment' in SQL?

River alignment right-aligns major SQL keywords (SELECT, FROM, WHERE) so their trailing characters form a vertical line. While visually stylized, it is difficult to maintain without specialized tooling and creates noisy git diffs when adding keywords.

Should subqueries inside WHERE clauses be indented?

Yes. The enclosing parentheses of a subquery should be on their own line or indented, with the inner query indented one level deeper (2 spaces) to visually isolate scope.

SQL Formatting

Building an Enterprise SQL Style Guide: Formatting Standards, Linting, and Team Conventions

By Sharon Ben-Moshe · Oct 13, 2026

The complete blueprint for an enterprise SQL style guide. Standardize formatting, keyword casing, indentation, naming conventions, and CI linting.

Read post

SQL Formatting

The Master Guide to SQL Common Table Expressions (CTEs): Syntax, Optimization Fences, and Recursion

By Sharon Ben-Moshe · Oct 13, 2026

The definitive guide to SQL Common Table Expressions (CTEs). Master chaining, recursive hierarchies, data-modifying CTEs, and optimization fences.

Read post

SQL Formatting

Try it now

Paste your SQL into sqlfmt — format, validate, and catch typos free in your browser.

Open SQL Formatter →

Key takeaways

Standardize on 2 spaces per indentation level for modern SQL repositories.

Keep major keywords (SELECT, FROM, WHERE, GROUP BY) left-aligned to minimize git diff noise.

Indent clause content (column lists, join predicates, filter conditions) 2 spaces deeper than the parent keyword.

Automate indentation in CI and pre-commit hooks to avoid formatting arguments in pull requests.

Flat left alignment versus river alignment

River alignment aligns keyword edges, but changing a query requires re-aligning every line. Flat left-alignment with 2 spaces is far cleaner and git-friendly:

Modern flat 2-space indentation style

-- Clean, git-friendly 2-space left-aligned style
SELECT
  u.id,
  u.username,
  u.email,
  COUNT(o.id) AS total_orders,
  SUM(o.amount) AS lifetime_value
FROM users u
LEFT JOIN orders o
  ON u.id = o.user_id
  AND o.status = 'completed'
WHERE u.created_at >= '2026-01-01'
  AND u.is_active = true
GROUP BY
  u.id,
  u.username,
  u.email
HAVING COUNT(o.id) > 5
ORDER BY lifetime_value DESC;

Indenting nested CTEs and subqueries

When combining CTEs, indent the query inside the CTE parentheses to clearly delineate scope:

Proper indentation for nested CTE expressions

WITH active_customers AS (
  SELECT
    id,
    company_name
  FROM customers
  WHERE status = 'active'
),
recent_orders AS (
  SELECT
    customer_id,
    SUM(total) AS revenue
  FROM orders
  WHERE order_date >= CURRENT_DATE - INTERVAL '30 days'
  GROUP BY customer_id
)
SELECT
  ac.company_name,
  COALESCE(ro.revenue, 0.00) AS monthly_revenue
FROM active_customers ac
LEFT JOIN recent_orders ro
  ON ac.id = ro.customer_id;

SQL Indentation: 2 Spaces, 4 Spaces, or Tabs? Formatting Standards

Quick answer

FAQs

Why do modern SQL style guides prefer 2 spaces over 4 spaces?

Why are tabs problematic in SQL scripts?

What is 'river alignment' in SQL?

Should subqueries inside WHERE clauses be indented?

Building an Enterprise SQL Style Guide: Formatting Standards, Linting, and Team Conventions

The Master Guide to SQL Common Table Expressions (CTEs): Syntax, Optimization Fences, and Recursion

How to Format Recursive CTEs in SQL: Hierarchical Query Structure

Key takeaways

Flat left alignment versus river alignment

Indenting nested CTEs and subqueries

Official references

Quick answer

FAQs

Why do modern SQL style guides prefer 2 spaces over 4 spaces?

Why are tabs problematic in SQL scripts?

What is 'river alignment' in SQL?

Should subqueries inside WHERE clauses be indented?

Keep reading

Building an Enterprise SQL Style Guide: Formatting Standards, Linting, and Team Conventions

The Master Guide to SQL Common Table Expressions (CTEs): Syntax, Optimization Fences, and Recursion

How to Format Recursive CTEs in SQL: Hierarchical Query Structure

Key takeaways

Flat left alignment versus river alignment

Indenting nested CTEs and subqueries

Related SQL guides

Official references