SQL Formatter

Because real SQL diverges from the standard exactly where queries get interesting: PostgreSQL's :: casts and jsonb operators, SQL Server's [bracketed identifiers] and TOP, MySQL/BigQuery backticks, SQLite's pragmas. Under the wrong dialect these tokens can misparse and format strangely. Pick the database you actually run; 'Standard SQL' is the fallback for textbook queries.

No — the formatter re-arranges whitespace, line breaks, and keyword casing only; identifiers, literals, operators, and clause order pass through untouched. Keyword casing doesn't affect execution in any mainstream database (identifier casing can, and those aren't touched). The formatted query is byte-for-byte semantically identical, which is what makes format-before-code-review safe.

Yes, and that's the point of this tool existing: the formatting engine runs locally in your browser, so queries containing real schema — table names, column names, the shape of your business logic — never leave your machine. Verify it yourself: load the page, disconnect from the internet, and formatting still works.

Uppercase is the traditional convention and still dominates documentation — keywords pop against lowercase identifiers, useful without syntax highlighting. Lowercase has grown fashionable in modern codebases where editors highlight anyway. Databases don't care; teams should just pick one, and a formatter is precisely how you enforce it cheaply.