SQL Formatter

Format, beautify, and minify SQL queries with syntax highlighting. Supports SELECT, JOIN, subqueries, CTEs, and more. Choose uppercase or lowercase keywords and custom indentation.

What is SQL Formatter?

A SQL Formatter takes raw, compressed, or inconsistently formatted SQL queries and reformats them with standardized indentation, line breaks, and keyword casing to produce queries that are readable, maintainable, and easy to review. SQL is one of the oldest and most widely used programming languages in existence, powering relational databases like PostgreSQL, MySQL, SQLite, Microsoft SQL Server, Oracle, BigQuery, and Snowflake. In practice, SQL queries are often written quickly in a single-line format inside application code strings, minified by ORM libraries, copied from database monitoring tools without formatting, or built programmatically using query builders—producing SQL that is technically correct but nearly impossible to read, debug, or review. A well-formatted SQL query is essential for code reviews (a reviewer cannot catch a JOIN condition bug in a 200-character single-line query), documentation, debugging complex performance issues, and onboarding new team members to a codebase. SQL formatting also enforces consistency across a team—standardizing whether keywords are UPPERCASE or lowercase, how CTEs are indented, and where line breaks appear in complex WHERE clauses, making the codebase more professional and easier to maintain.

How to Use SQL Formatter

Paste your SQL query—whether it is a simple SELECT statement or a complex multi-page query with CTEs, multiple JOINs, subqueries, and window functions—into the input area and click Format. The formatted output appears in the right panel with proper indentation, consistent line breaks after each major clause, and aligned column lists. Use the Indentation selector to choose 2-space indentation (compact, fits more on screen) or 4-space indentation (more visual hierarchy, preferred in many SQL style guides). Use the Keyword Case toggle to switch between UPPERCASE keywords (the traditional SQL convention: SELECT, FROM, WHERE, JOIN) and lowercase keywords (preferred in some modern style guides for readability). Toggle Syntax Highlighting to add color coding that visually distinguishes keywords, functions, strings, numbers, and identifiers—making complex queries easier to read. Click Minify to compress the formatted query into a single line with minimal whitespace—useful for embedding in ORM query builders, application configuration files, or anywhere that requires compact SQL strings. Copy the output with the copy button.

FAQ

What SQL clauses and features are supported?

The formatter supports the full range of standard SQL: SELECT (with DISTINCT, aliases, window functions), FROM, WHERE (with AND/OR/NOT and nested conditions), all JOIN types (INNER, LEFT, RIGHT, FULL OUTER, CROSS, SELF), GROUP BY, HAVING, ORDER BY (with ASC/DESC, NULLS FIRST/LAST), UNION and UNION ALL, subqueries (inline views), Common Table Expressions (CTEs with WITH), CASE/WHEN/THEN/END expressions, INSERT INTO, UPDATE SET, DELETE FROM, CREATE TABLE, ALTER TABLE, and stored procedure blocks.

Does it support MySQL, PostgreSQL, SQL Server, and BigQuery dialects?

The formatter handles standard ANSI SQL syntax that works across all major relational databases. Dialect-specific functions and syntax (like PostgreSQL's :: type casting, MySQL's backtick identifiers, SQL Server's [] brackets, or BigQuery's STRUCT and ARRAY types) are preserved as-is in the output without modification. The formatting applies to the structural SQL (clauses, indentation, whitespace) while leaving database-specific syntax untouched.

Should I use UPPERCASE or lowercase for SQL keywords?

Both styles are valid—it comes down to team preference and style guide. UPPERCASE keywords (SELECT, FROM, WHERE) is the traditional SQL convention, makes keywords visually distinct from identifiers and function names, and is the style used in most SQL textbooks and documentation. Lowercase keywords are preferred by some modern development teams who find all-caps harder to read. What matters most is consistency within your project. Use this tool to enforce whichever convention your team has adopted.

Can I format SQL that is embedded in a string inside JavaScript or Python code?

Yes. Copy just the SQL string content (without the surrounding quotes and string concatenation) and paste it into the formatter. After formatting, carefully re-embed it into your code, paying attention to line continuation syntax (backslash in Python, template literals in JavaScript) and escaping any single quotes that appear in the SQL. Many developers prefer using a dedicated query builder or ORM for complex dynamic SQL instead of string concatenation.

Why does my formatted SQL look different from what my IDE produces?

Different SQL formatters apply different style rules—there is no single universally agreed-upon SQL formatting standard. Your IDE's SQL plugin, database client (DBeaver, DataGrip, pgAdmin), and this online formatter may each apply different indentation levels, line break positions, and comma placement (leading vs. trailing commas). For team consistency, agree on a formatter and its settings, then apply it uniformly. The important thing is consistency, not which specific style is chosen.