SQL Formatter.

SQL copied from application logs or a query builder often arrives as one long line. A SQL formatter, also called a SQL beautifier or SQL pretty printer, breaks that query into a readable structure. SELECT columns, JOIN conditions, filters and nested queries become easier to follow without manually adding every line break.

Paste a query into the input editor and choose your database dialect. Set two spaces, four spaces or tabs for indentation, then decide whether recognized keywords should be uppercase, lowercase or left as written. Select Format SQL to generate a separate result. The source remains available beside it for comparison.

For a quick workflow, press Ctrl+Enter on Windows or Linux, or Command+Enter on macOS. Copy the formatted SQL into your editor or download it as formatted.sql. If you edit the input or change an option, format again: the previous output is cleared so you cannot accidentally copy a result produced from different settings.

SQL dialects share a common vocabulary but differ in keywords, quoting and extensions. A PostgreSQL formatter needs to recognize constructs that may not be interpreted the same way in MySQL or T-SQL. Choosing the right dialect helps the formatting engine read those differences.

The dialect selector identifies the input language. It does not convert a MySQL query into PostgreSQL, replace unsupported functions or adapt a schema. Start with the dialect used by the database that will receive the query.

These fictional examples are available above the editor. Loading an example also chooses its dialect. The outputs below use uppercase keywords and two-space indentation, so you can see the formatting before trying your own query.

SELECT
  c.id,
  c.name,
  count(o.id) AS order_count,
  sum(o.total) AS revenue
FROM
  customers c
  JOIN orders o ON o.customer_id = c.id
WHERE
  o.status = 'paid'
GROUP BY
  c.id,
  c.name
HAVING
  sum(o.total) > 1000
ORDER BY
  revenue DESC;

WITH
  ranked_orders AS (
    SELECT
      id,
      customer_id,
      total,
      row_number() OVER (
        PARTITION BY
          customer_id
        ORDER BY
          created_at DESC
      ) AS position
    FROM
      orders
    WHERE
      created_at >= date '2024-01-01'
  )
SELECT
  customer_id,
  id,
  total
FROM
  ranked_orders
WHERE
  position = 1
ORDER BY
  customer_id;

-- Fictional seed data
INSERT INTO
  `products` (`sku`, `name`, `price`)
VALUES
  ('DEMO-01', 'Desk lamp; warm light', 29.95),
  ('DEMO-02', 'Reader''s notebook', 8.50);

Consistent indentation makes it easier to follow a subquery or CTE. Separating SELECT columns and JOIN conditions helps a reviewer compare related expressions. In an aggregate query, distinct WHERE and HAVING sections make the two conditions easier to locate. Formatting supports that reading process; it does not decide whether the query expresses the intended business rule.

Keyword case is a style choice. This tool changes recognized keywords only when requested, leaving identifier, function-name and data-type case as written. It does not fill in parameters, rewrite joins, remove filters or connect to your database. Comments are retained, though the formatter may adjust their layout.

A neatly formatted query can still refer to a missing table, contain a type error or return unexpected rows. Database extensions and procedural scripts also exceed what a general formatter can handle. Review the result in context and use database-specific tooling for validation and performance analysis.

The formatting engine is SQL Formatter. Its documentation describes supported dialects and limitations, including stored procedures and custom delimiters. This page runs the engine locally with an input limit and a cancellable worker; it is intended for queries and manageable script excerpts.