Clause focused
The cleaner splits common clauses such as SELECT, FROM, JOIN, WHERE, GROUP BY, HAVING, ORDER BY and LIMIT onto readable lines.
Query cleanup
Clean SQL snippets, split major clauses, normalize keyword casing and run basic query structure checks without sending SQL to a backend.
Reference notes
The cleaner splits common clauses such as SELECT, FROM, JOIN, WHERE, GROUP BY, HAVING, ORDER BY and LIMIT onto readable lines.
SQL text is handled by client-side JavaScript. Formalint does not execute, store or upload pasted queries.
The checker flags unbalanced parentheses, unclosed quotes, missing SELECT/FROM structure and destructive statements.
Frequently asked
The formatter handles standard SQL syntax common to PostgreSQL, MySQL, SQL Server, and Oracle. Dialect-specific syntax such as vendor-only functions is preserved as-is but not validated.
Consistent indentation of joins, subqueries, and CTEs makes it far easier to spot a missing join condition or an accidental cross join before it runs against a production database.
Compact mode collapses a formatted query onto fewer lines while keeping clause boundaries readable, which is useful when pasting a query into a chat message or a code comment.
It highlights patterns like SELECT * in production queries, missing WHERE clauses on UPDATE or DELETE statements, and unbalanced parentheses.
When Format, Compact or Check reports an error, the output displays the current input unchanged. Copy and Download refer to that input, not a previous successful result. An error does not mean the displayed query has been repaired.
SELECT (id FROM orders;: close the unmatched parenthesis before trying again.SELECT 'pending FROM orders;: correct the unclosed quote in the original query.DELETE FROM orders;: review the write operation and intended row set in your database workflow; formatting does not authorize execution.These are basic text checks, not database validation. The formatter uses whitespace and keyword rules: quoted text and comments require careful comparison against the original. Keep a source copy, review every change, and use a dialect-aware formatter for production queries. Follow the SQL cleanup review checklist before using the output.