INPUTpaste SQL here
OUTPUT
40120
Format, beautify, and minify SQL instantly. Supports PostgreSQL, MySQL, T-SQL, PL/SQL, SQLite, BigQuery, and more — all client-side.
Paste any raw or minified SQL query into the input panel. Supports queries of any length.
Select your database dialect, indentation style, keyword case, and line width preferences.
Click Format (or press ⌘↵) to beautify, or Minify to produce compact single-line SQL.
| Dialect | Best For | Notable Features |
|---|---|---|
| PostgreSQL | Application backends, analytics | CTEs, JSON operators, window functions |
| MySQL | Web applications, LAMP stack | Backtick quoting, LIMIT/OFFSET syntax |
| T-SQL | SQL Server, Azure SQL | TOP clause, NOLOCK hints, square brackets |
| PL/SQL | Oracle databases | Package syntax, procedure bodies, dual table |
| BigQuery | Google Cloud analytics | Backtick identifiers, ARRAY/STRUCT types |
| SQLite | Embedded, mobile apps | Lightweight, type affinity system |
| Trino | Distributed query engines | Lambda expressions, connectors |
| Standard SQL | General / unknown dialect | ANSI-compatible across all databases |
No. This tool is 100% client-side. Your SQL queries are processed entirely in your browser using JavaScript and are never sent to any server. Nothing is logged or retained after you close the tab.
Format beautifies your SQL with consistent indentation, newlines, and keyword casing — ideal for readability and code review. Minify strips comments and collapses whitespace into a single line, which minimizes size for embedding in application code or config files.
Yes. Select the PL/SQL dialect for Oracle procedures and packages, or T-SQL for SQL Server stored procedures. The formatter understands BEGIN/END blocks, DECLARE sections, and procedural constructs.
Yes. Your chosen dialect, indentation, keyword case, and line width are saved to localStorage and automatically restored the next time you visit.
Line width controls how long a line can be before the formatter wraps a clause to the next line. A lower value (e.g., 40) produces more vertical SQL; a higher value (e.g., 120) allows longer lines and is better for wide monitors.