Format and beautify SQL queries for MySQL, PostgreSQL, SQLite, T-SQL, and Standard SQL. Keyword casing control. Runs 100% in your browser.
Share this tool
Found it useful? Help a fellow developer discover it.
Standard SQL
ANSI SQL syntax. Works for most common SELECT, INSERT, UPDATE, DELETE, and DDL statements.
MySQL
MySQL-specific functions, backtick identifiers, and LIMIT/OFFSET syntax.
PostgreSQL
PostgreSQL dollar-quoted strings, RETURNING clauses, and :: cast syntax.
SQLite
SQLite-compatible formatting. Handles PRAGMA statements and WITHOUT ROWID tables.
T-SQL (SQL Server)
Microsoft SQL Server syntax, TOP, NOLOCK hints, square-bracket identifiers, and GO separators.
Minified or machine-generated SQL is difficult to read and audit. Well-formatted SQL puts each clause on its own line, indents subqueries and JOIN conditions, and uses consistent keyword casing making it far easier to spot logical errors, missing conditions, or implicit cross joins. Formatted SQL is also easier to diff in code review and to copy into query editors that don't have built-in formatting. This tool formats SQL instantly in your browser, which means production query strings, credentials embedded in connection strings, and sensitive schema details never leave your device.
.sql file.Paste your SQL into the input panel, select the correct dialect from the dropdown (MySQL, PostgreSQL, T-SQL, SQLite, or Standard SQL), choose your preferred keyword casing, then click Format or press Ctrl+Enter. The formatted query appears in the output panel ready to copy.
Yes. The sql-formatter library handles SELECT statements with multiple JOINs, nested subqueries, common table expressions (WITH ... AS), window functions (OVER PARTITION BY), and most DML and DDL statements. Very long or highly nested procedural SQL with deeply nested BEGIN/END blocks may have occasional edge cases.
Every formatter applies its own style rules for line breaks, indentation width, and clause placement. There is no universal SQL formatting standard. The output follows the sql-formatter library conventions. The logical meaning of the query is always identical. Only whitespace changes.
No. Formatting only affects whitespace and keyword casing, which SQL parsers treat as insignificant. The logical meaning of a query is identical before and after formatting.
Each dialect has slightly different reserved words, function names, and syntax rules. Using the matching dialect produces more accurate keyword recognition and avoids false formatting errors on dialect-specific syntax like MySQL backticks or PostgreSQL :: casts.
Yes, for dialects that support them. Stored procedure bodies (CREATE PROCEDURE … BEGIN … END) are formatted correctly for MySQL, PostgreSQL, and T-SQL. Very complex procedural SQL with nested BEGIN/END blocks may have edge cases.
No. All formatting happens client-side using the sql-formatter npm package compiled for the browser. Your query strings, table names, and any embedded data values never leave your device.
Convention only. The SQL standard does not mandate keyword casing. Both SELECT and select are valid. UPPERCASE keywords are the traditional style and aid readability by visually distinguishing keywords from identifiers. Lowercase is preferred in some codebases. Preserve keeps whatever casing the original input used.
Text / Code Diff
Compare two text blocks and highlight line-by-line differences.
CSV to JSON Converter
Convert CSV to JSON or JSON to CSV in your browser. Supports custom delimiters, header rows, and dynamic typing.
XML Formatter
Format, beautify, and minify XML online. Validates XML structure and supports custom indentation.
Code to Image
Turn any code snippet into a beautiful screenshot. Pick a theme, font, and background, then download a shareable PNG. Runs fully in your browser.