SQL Beautifier

A SQL beautifier (also called a SQL formatter or SQL prettifier) reformats raw SQL queries into a clean, consistently indented structure with uppercase keywords and one clause per line. This makes queries dramatically easier to read, review, and debug — especially for long queries with multiple JOINs, WHERE conditions, and subqueries. Using a consistent format also helps teams collaborate on shared SQL without style debates.

No. This SQL beautifier runs entirely in your browser using JavaScript. Your query never leaves your machine. That means it works offline, is instant regardless of your connection speed, and is safe to use with proprietary or sensitive SQL that you wouldn't want sent to a third-party API.

The formatter supports Standard SQL, MySQL, PostgreSQL, and SQLite. The dialect selector primarily affects how dialect-specific keywords and functions are recognized and uppercased — for example AUTO_INCREMENT (MySQL) versus SERIAL (PostgreSQL). Core formatting behavior (clause layout, indentation, operator spacing) is identical across all dialects.

In comma-first formatting, the comma that separates column names or expressions is placed at the beginning of the new line rather than the end of the previous line. For example: ' col1 / , col2 / , col3' instead of 'col1, / col2, / col3'. This style makes it easier to spot missing or extra commas when reviewing a diff, since the comma is always in column 2 of each continuation line.

When the formatter detects a subquery — a SELECT statement inside parentheses — it formats the inner query with increased indentation relative to the outer query. The opening parenthesis appears on its own line, the inner clauses are indented one additional level, and the closing parenthesis returns to the outer indentation level. This makes it clear where subqueries begin and end, even when they are deeply nested.

Yes. Both single-line comments (-- comment) and multi-line block comments (/* comment */) are preserved exactly as written. The formatter identifies them during a tokenization pass before any keyword uppercasing or clause splitting occurs, so their content is never modified. This is important for queries that contain documentation, parameter hints, or query optimizer hints inside comments.