SQL Formatter

Format and beautify SQL queries with keyword uppercasing, indentation, and proper line breaks.

Input SQL

Formatted SQL

SELECT u.id, u.name, u.email, o.order_id, o.total_amount
FROM users u
INNER JOIN orders o
  ON u.id = o.user_id
LEFT JOIN payments p
  ON o.order_id = p.order_id
WHERE u.status = 'active'
  AND o.created_at >= '2024-01-01'
  AND (o.total_amount > 100
  OR p.method = 'credit_card')
GROUP BY u.id, u.name, u.email
HAVING COUNT(o.order_id) > 5
ORDER BY o.total_amount DESC
LIMIT 50

Want a deeper dive into the concepts behind this tool? SQL Formatting Best Practices: Write Clean, Readable Queries

About SQL Formatter

SQL Formatter is a free online tool that beautifies and formats SQL queries. Well- formatted SQL is easier to read, review, and debug. Consistent formatting also improves code quality in team environments and makes complex queries more maintainable.

The tool automatically converts SQL keywords to uppercase, adds proper indentation, and inserts line breaks for better readability. All formatting is done entirely in your browser — your SQL queries are never sent to any server.

How to Use

Paste SQL — Enter or paste your SQL query in the input editor.
Format — Click the Format button to beautify the query with proper indentation and keyword uppercasing.
Copy result — Copy the formatted SQL using the copy button.

Formatting Rules

SQL keywords are converted to UPPERCASE (SELECT, FROM, WHERE, etc.).
Major clauses (SELECT, FROM, WHERE, JOIN, ORDER BY, GROUP BY, HAVING, LIMIT) start on new lines.
AND/OR conditions are indented within WHERE clauses.
Consistent indentation for sub-clauses.

Frequently Asked Questions

Q: Should SQL keywords be uppercase or lowercase?

SQL is case-insensitive for keywords, so both work functionally. However, uppercasing keywords (SELECT, FROM, WHERE) is the most widely adopted convention and is recommended by most SQL style guides. It visually distinguishes keywords from table and column names, improving readability.

Q: Which SQL dialects are supported?

The formatter works with standard SQL syntax and is compatible with most SQL dialects including MySQL, PostgreSQL, SQL Server, Oracle, and SQLite.

Q: Does it modify my query logic?

No. The formatter only changes whitespace, indentation, and keyword casing. It never modifies the logic or meaning of your SQL query.

Q: Can it format stored procedures and DDL statements?

The tool is optimized for DML statements (SELECT, INSERT, UPDATE, DELETE) and works well with most DDL statements (CREATE TABLE, ALTER TABLE). Complex stored procedures with vendor-specific syntax may have limited formatting support.

Related Tools

Regex Tester

Test and debug regular expressions with real-time matching and highlighting.

Markdown Preview

Write Markdown and see the rendered HTML preview in real-time.

Number Base Converter

Convert numbers between Binary, Octal, Decimal, and Hexadecimal formats.

CSS Minifier

Compress CSS by removing comments, whitespace, and unnecessary semicolons.

HTML Minifier

Compress HTML by removing comments, collapsing whitespace, and optimizing attributes.

JSON Schema Validator

Validate JSON data against JSON Schema Draft-07 with detailed error reporting.

Code Diff Viewer

Compare two code snippets with line-by-line diff and color-coded highlighting.

Chmod Calculator

Convert between numeric and symbolic Unix file permissions with presets.

Markdown to HTML

Convert Markdown to clean HTML with GFM support and live preview.

HTML to Markdown

Convert HTML tags to clean Markdown syntax with GFM table support.

JavaScript Minifier

Compress JavaScript by removing comments, whitespace, and unnecessary characters.

cURL to Code

Convert cURL commands to JavaScript, Python, Go, and PHP code instantly.

SQL Formatting Best Practices: Write Clean, Readable Queries10 min read

Introduction

SQL Formatter rewrites the whitespace around your queries so the structure becomes legible in a glance. It uppercases reserved words, breaks long clauses onto their own lines, and indents sub-expressions so that nested joins, subqueries, and CTEs line up the way you would draw them on paper.

A tidy query is not cosmetic — it is the cheapest form of documentation. A reviewer can tell in one scan whether a JOIN is INNER or LEFT, whether a filter belongs in the ON clause or the WHERE clause, and whether the window function references the right partition. Inline queries from an ORM or a copy-pasted log rarely arrive in that shape, so the formatter bridges the gap.

Formatting happens entirely in your browser using a pure-JavaScript tokenizer. The query text never reaches a server, which matters when the SQL references schema names, internal column aliases, or embedded literal values you would rather not send over the wire.

How to Use

Paste the raw SQL into the left editor — a single-line dump from a log, an ORM trace, or a hand-written draft all work.
Click Format. Keywords are uppercased and clauses are placed on their own lines with consistent indentation.
Review the result in the right pane. If the shape is still off, adjust the input (for example, add missing parentheses) and format again.
Copy the formatted query to the clipboard or download it as a .sql file.
Paste the cleaned version into your migration, pull request, or database tool.

Examples

Three queries that cover the most common shapes: a filtered SELECT, a multi-table JOIN, and a CTE feeding a window function.

Example 1: Simple SELECT with WHERE and ORDER BY

A one-line query turns into a block where each clause sits on its own line, making the filter criteria obvious at a glance.

Input

select id, name, email from users where active = true and created_at > '2026-01-01' order by created_at desc limit 50;

Output

SELECT
  id,
  name,
  email
FROM users
WHERE active = TRUE
  AND created_at > '2026-01-01'
ORDER BY created_at DESC
LIMIT 50;

Example 2: Multi-table JOIN

Each JOIN starts on a new line with its ON condition aligned beneath it, so the relationships between tables are easy to audit.

Input

select o.id, u.name, p.title from orders o inner join users u on o.user_id = u.id left join products p on o.product_id = p.id where o.status = 'paid';

Output

SELECT
  o.id,
  u.name,
  p.title
FROM orders o
INNER JOIN users u
  ON o.user_id = u.id
LEFT JOIN products p
  ON o.product_id = p.id
WHERE o.status = 'paid';

Example 3: CTE with a window function

Common table expressions and window functions benefit the most from formatting — the PARTITION BY and ORDER BY arguments get their own indentation so the window definition reads naturally.

Input

with ranked_sales as (select user_id, amount, row_number() over (partition by user_id order by amount desc) as rn from sales) select * from ranked_sales where rn = 1;

Output

WITH ranked_sales AS (
  SELECT
    user_id,
    amount,
    ROW_NUMBER() OVER (
      PARTITION BY user_id
      ORDER BY amount DESC
    ) AS rn
  FROM sales
)
SELECT *
FROM ranked_sales
WHERE rn = 1;

Target language details

Version assumptions and style choices baked into the generated output. If your runtime is older, you may need to adjust syntax (e.g. drop optional chaining, use `var` instead of `const`).

Language	Version	Output style
SQL	ANSI-92 + dialect hints for PostgreSQL / MySQL / SQLite	Keywords uppercased, dialect-specific functions flagged.

Key Features

Keyword uppercasing — SELECT, FROM, WHERE, JOIN and other reserved words are normalized so they stand out against identifiers.
Per-clause line breaks — each major clause (FROM, WHERE, GROUP BY, ORDER BY, LIMIT) starts on its own line.
AND/OR alignment — conditions inside WHERE and HAVING are indented consistently so boolean logic is easy to scan.
CTE and subquery support — nested queries are indented one level deeper than the outer query.
Dialect-friendly — works with MySQL, PostgreSQL, SQL Server, Oracle, and SQLite syntax.
Preserves string literals, comments, and identifier quoting without altering any data.
Runs 100% locally — query text never leaves the browser tab.

Frequently Asked Questions

Does the formatter change the meaning of my query?

No. Only whitespace, line breaks, and keyword casing change. String literals, identifier quoting, and the order of tokens are left alone, so the rewritten query returns the same rows as the original.

Are vendor-specific statements supported?

The formatter handles the common cases — CREATE TABLE, ALTER TABLE, INSERT, UPDATE, DELETE, MERGE — across the major dialects. Exotic constructs like PL/pgSQL procedure bodies or T-SQL IF blocks may need a little hand-cleanup after formatting.

Why are my keywords still lowercase after formatting?

Double-check the formatter options — keyword casing can be toggled between uppercase, lowercase, and preserve-original. Also confirm that the tokens in question are actually SQL reserved words and not identifiers wrapped in backticks or double quotes, which are kept as-is.

Can it handle very long queries?

Yes. The tokenizer is linear in the input size, so queries with a few thousand lines format in well under a second on a modern laptop. The practical limit is browser memory, not the algorithm.

Does it validate the SQL?

The formatter tokenizes SQL but does not run semantic validation — missing columns, unknown tables, or type mismatches are caught by your database, not by this tool. It will, however, flag unterminated string literals and unbalanced parentheses while parsing.

SQL Formatter

Format and beautify SQL queries with keyword uppercasing, indentation, and proper line breaks.

Input SQL

Formatted SQL

SELECT u.id, u.name, u.email, o.order_id, o.total_amount
FROM users u
INNER JOIN orders o
  ON u.id = o.user_id
LEFT JOIN payments p
  ON o.order_id = p.order_id
WHERE u.status = 'active'
  AND o.created_at >= '2024-01-01'
  AND (o.total_amount > 100
  OR p.method = 'credit_card')
GROUP BY u.id, u.name, u.email
HAVING COUNT(o.order_id) > 5
ORDER BY o.total_amount DESC
LIMIT 50

Want a deeper dive into the concepts behind this tool? SQL Formatting Best Practices: Write Clean, Readable Queries

About SQL Formatter

How to Use

Paste SQL — Enter or paste your SQL query in the input editor.
Format — Click the Format button to beautify the query with proper indentation and keyword uppercasing.
Copy result — Copy the formatted SQL using the copy button.

Formatting Rules

SQL keywords are converted to UPPERCASE (SELECT, FROM, WHERE, etc.).
Major clauses (SELECT, FROM, WHERE, JOIN, ORDER BY, GROUP BY, HAVING, LIMIT) start on new lines.
AND/OR conditions are indented within WHERE clauses.
Consistent indentation for sub-clauses.

Frequently Asked Questions

Q: Should SQL keywords be uppercase or lowercase?

Q: Which SQL dialects are supported?

The formatter works with standard SQL syntax and is compatible with most SQL dialects including MySQL, PostgreSQL, SQL Server, Oracle, and SQLite.

Q: Does it modify my query logic?

No. The formatter only changes whitespace, indentation, and keyword casing. It never modifies the logic or meaning of your SQL query.

Q: Can it format stored procedures and DDL statements?

Related Tools

Regex Tester

Test and debug regular expressions with real-time matching and highlighting.

Markdown Preview

Write Markdown and see the rendered HTML preview in real-time.

Number Base Converter

Convert numbers between Binary, Octal, Decimal, and Hexadecimal formats.

CSS Minifier

Compress CSS by removing comments, whitespace, and unnecessary semicolons.

HTML Minifier

Compress HTML by removing comments, collapsing whitespace, and optimizing attributes.

JSON Schema Validator

Validate JSON data against JSON Schema Draft-07 with detailed error reporting.

Code Diff Viewer

Compare two code snippets with line-by-line diff and color-coded highlighting.

Chmod Calculator

Convert between numeric and symbolic Unix file permissions with presets.

Markdown to HTML

Convert Markdown to clean HTML with GFM support and live preview.

HTML to Markdown

Convert HTML tags to clean Markdown syntax with GFM table support.

JavaScript Minifier

Compress JavaScript by removing comments, whitespace, and unnecessary characters.

cURL to Code

Convert cURL commands to JavaScript, Python, Go, and PHP code instantly.

SQL Formatting Best Practices: Write Clean, Readable Queries10 min read

Introduction

How to Use

Paste the raw SQL into the left editor — a single-line dump from a log, an ORM trace, or a hand-written draft all work.
Click Format. Keywords are uppercased and clauses are placed on their own lines with consistent indentation.
Review the result in the right pane. If the shape is still off, adjust the input (for example, add missing parentheses) and format again.
Copy the formatted query to the clipboard or download it as a .sql file.
Paste the cleaned version into your migration, pull request, or database tool.

Examples

Three queries that cover the most common shapes: a filtered SELECT, a multi-table JOIN, and a CTE feeding a window function.

Example 1: Simple SELECT with WHERE and ORDER BY

A one-line query turns into a block where each clause sits on its own line, making the filter criteria obvious at a glance.

Input

select id, name, email from users where active = true and created_at > '2026-01-01' order by created_at desc limit 50;

Output

SELECT
  id,
  name,
  email
FROM users
WHERE active = TRUE
  AND created_at > '2026-01-01'
ORDER BY created_at DESC
LIMIT 50;

Example 2: Multi-table JOIN

Each JOIN starts on a new line with its ON condition aligned beneath it, so the relationships between tables are easy to audit.

Input

select o.id, u.name, p.title from orders o inner join users u on o.user_id = u.id left join products p on o.product_id = p.id where o.status = 'paid';

Output

SELECT
  o.id,
  u.name,
  p.title
FROM orders o
INNER JOIN users u
  ON o.user_id = u.id
LEFT JOIN products p
  ON o.product_id = p.id
WHERE o.status = 'paid';

Example 3: CTE with a window function

Common table expressions and window functions benefit the most from formatting — the PARTITION BY and ORDER BY arguments get their own indentation so the window definition reads naturally.

Input

with ranked_sales as (select user_id, amount, row_number() over (partition by user_id order by amount desc) as rn from sales) select * from ranked_sales where rn = 1;

Output

WITH ranked_sales AS (
  SELECT
    user_id,
    amount,
    ROW_NUMBER() OVER (
      PARTITION BY user_id
      ORDER BY amount DESC
    ) AS rn
  FROM sales
)
SELECT *
FROM ranked_sales
WHERE rn = 1;

Target language details

Version assumptions and style choices baked into the generated output. If your runtime is older, you may need to adjust syntax (e.g. drop optional chaining, use `var` instead of `const`).

Language	Version	Output style
SQL	ANSI-92 + dialect hints for PostgreSQL / MySQL / SQLite	Keywords uppercased, dialect-specific functions flagged.

Key Features

Keyword uppercasing — SELECT, FROM, WHERE, JOIN and other reserved words are normalized so they stand out against identifiers.
Per-clause line breaks — each major clause (FROM, WHERE, GROUP BY, ORDER BY, LIMIT) starts on its own line.
AND/OR alignment — conditions inside WHERE and HAVING are indented consistently so boolean logic is easy to scan.
CTE and subquery support — nested queries are indented one level deeper than the outer query.
Dialect-friendly — works with MySQL, PostgreSQL, SQL Server, Oracle, and SQLite syntax.
Preserves string literals, comments, and identifier quoting without altering any data.
Runs 100% locally — query text never leaves the browser tab.

Frequently Asked Questions

Does the formatter change the meaning of my query?

No. Only whitespace, line breaks, and keyword casing change. String literals, identifier quoting, and the order of tokens are left alone, so the rewritten query returns the same rows as the original.

Are vendor-specific statements supported?

Why are my keywords still lowercase after formatting?

Can it handle very long queries?

Yes. The tokenizer is linear in the input size, so queries with a few thousand lines format in well under a second on a modern laptop. The practical limit is browser memory, not the algorithm.

Does it validate the SQL?