SQL Formatter
Format and beautify SQL queries with proper indentation and keyword casing
What is SQL Formatter?
SQL queries written in a hurry, generated by ORMs, exported from query builders, or pasted from logs are often a single long line or inconsistently indented mess that is nearly impossible to read and review. Formatting SQL is not just cosmetic — properly indented queries with consistent keyword casing reveal the logical structure of JOINs, subqueries, CTEs, and WHERE conditions that determine correctness and performance. Our free SQL Formatter takes any SQL query — SELECT statements, INSERT/UPDATE/DELETE operations, CREATE TABLE definitions, stored procedures, or CTEs — and formats it with consistent uppercase keywords (SELECT, FROM, WHERE, JOIN), proper indentation of nested conditions and subqueries, aligned columns in SELECT lists, and clear visual separation of major clauses. The formatter supports standard SQL, MySQL, PostgreSQL, Microsoft SQL Server, and SQLite syntax variants. Formatted SQL is easier to read in code reviews, easier to debug by visually scanning the JOIN conditions and WHERE predicates, and easier to spot performance problems like missing indexes or unintended Cartesian products.
How to Use SQL Formatter
- 1
Paste Your SQL Query
Paste any SQL — a minified ORM-generated query from a log, a manually written query, a CREATE TABLE statement, a stored procedure, or a complex CTE chain.
- 2
Choose Your SQL Dialect
Select your database dialect: Standard SQL, MySQL, PostgreSQL, SQL Server, or SQLite. Each dialect has slightly different syntax for functions, quoting, and keywords.
- 3
Copy the Formatted Output
The formatted SQL appears with consistent uppercase keywords, indented clauses, and visual separation of JOIN conditions and WHERE predicates. Copy it for your query editor, documentation, or code review.
Use Cases
Debugging ORM-Generated Queries
ORMs like Hibernate, ActiveRecord, Sequelize, and SQLAlchemy log their generated SQL as a single compressed line. When a query produces wrong results or is unexpectedly slow, paste the logged SQL here to see the full structure — all the JOINs, subqueries, and WHERE conditions laid out clearly — so you can identify a missing condition, a wrong JOIN type, or an N+1 query pattern.
Code Review of Database Migrations
Database migrations containing ALTER TABLE, CREATE INDEX, and complex UPDATE statements are easier to review when formatted. A well-formatted migration clearly shows which tables are affected, what conditions apply to UPDATE/DELETE statements (preventing accidental full-table updates), and whether index definitions are correct for the targeted columns.
Writing SQL Documentation and Runbooks
Operational runbooks and database documentation often include SQL queries for data audits, health checks, and diagnostic reports. Formatting these queries before including them in documentation makes them significantly more readable for team members who need to understand, verify, or modify the queries months later.
Features
Uppercase SQL Keywords
Formats all SQL keywords (SELECT, FROM, WHERE, JOIN, ON, GROUP BY, HAVING, ORDER BY, LIMIT) in uppercase for the standard convention that maximises readability.
Indented Subqueries and CTEs
Nested subqueries and Common Table Expressions (CTEs) are indented to make their scope and relationships to the outer query immediately clear.
Multi-Dialect Support
Handles syntax differences between MySQL, PostgreSQL (with $$ dollar-quoting and :: type casting), SQL Server (with [] identifiers), and standard SQL.
Preserves Query Logic
Formatting is purely cosmetic — all aliases, conditions, function calls, and string literals are preserved exactly. The formatted query is functionally identical to the input.
Frequently Asked Questions
Uppercase SQL keywords (SELECT, FROM, WHERE) are a widely adopted convention that visually separates the structural SQL elements from the user-defined identifiers (table names, column names, aliases). This makes the query's logic easier to read at a glance. While most databases are case-insensitive for keywords, lowercase keywords in queries mixed with lowercase identifiers make the structure harder to parse visually.
A Common Table Expression (CTE) is a named temporary result set defined with the WITH clause before a main query: WITH active_users AS (SELECT ... FROM ...) SELECT * FROM active_users. They are powerful for breaking complex queries into readable named steps. The formatter indents each CTE definition and aligns the WITH clause, AS keyword, and opening parentheses to clearly delineate each named result set.
Yes, the formatter handles procedural SQL including CREATE PROCEDURE, CREATE FUNCTION, BEGIN...END blocks, IF/ELSE conditionals, and LOOP constructs for MySQL, PostgreSQL (PL/pgSQL), and SQL Server (T-SQL). Indentation follows the block structure of the procedural code, though very complex dynamic SQL within stored procedures may format less predictably.
Key differences: PostgreSQL uses double quotes for identifiers (SELECT "first_name") while MySQL uses backticks (SELECT `first_name`). PostgreSQL uses $1, $2 for parameterised query placeholders while MySQL uses ?. PostgreSQL supports the :: cast operator (SELECT '2024-01-01'::date) with no MySQL equivalent. PostgreSQL uses ILIKE for case-insensitive LIKE while MySQL's LIKE is case-insensitive by default on most collations.
No. SQL formatting is purely visual — whitespace and keyword casing have zero effect on query execution. The database parser normalises the query before execution regardless of how it was written. Performance is determined entirely by the logical structure: which tables are joined, what indexes exist, which predicates filter data early, and whether subqueries can be rewritten as JOINs.
Need a Professional Website?
JAIDOO EMPIRE builds fast, SEO-optimised websites for businesses worldwide. All free tools are built and maintained by our team.
Start Your Project
