SQL Formatter

Worked example: review a filtered customer list

Select PostgreSQL, UPPERCASE and 2 spaces. Paste the single-line input below and format it. The expected output separates the selected columns, table, condition and sorting rule. The quoted value 'Montréal' stays data; uppercasing keywords does not mean uppercasing every character in the query.

select id, name from customers where city = 'Montréal' order by name;

SELECT
  id,
  name
FROM
  customers
WHERE
  city = 'Montréal'
ORDER BY
  name;

Choose the dialect before changing the query

A query copied from a MySQL application may contain backtick-quoted identifiers, while a PostgreSQL query may use double quotes or a cast such as created_at::date. Select the matching database language first. The dialect selector helps the formatter recognize syntax; it does not translate a MySQL query into PostgreSQL or create missing tables.

Use two spaces for a compact review, four when that matches your project, or tabs when your editor expects them. Keyword case is a team convention rather than a performance setting. Keep the original query so you can compare literals, comments and database-specific clauses after formatting.

If the result still looks wrong

• Check for an unclosed quote or comment before the reported error position.
• Remove copied terminal prompts and log prefixes; they are not SQL.
• Try a smaller complete statement when a stored procedure or custom delimiter is unsupported.
• Use your database's own parser and a suitable test environment to validate behavior. An unknown table can format successfully because this tool has no database connection.

For a longer dialect comparison and a check-before-running workflow, read format SQL for the right dialect.