Contact SQLFormat

Email: [email protected]

SQLFormat is operated by a single person in the United States. There is no support team, no contact form, and no CRM — a human mailbox receives every message.

The bug report that actually gets fixed fast

Paste the exact query that came out mangled and name the engine it was written for (PostgreSQL, MySQL, SQLite, BigQuery) plus which mode the dialect box was on — the layout pass is engine-agnostic, so the engine and the mode are what tell me which construct to expect. If you can, include the input both before and after formatting — a diff of the two tells me whether the tokenizer or the layout pass broke. The usual suspects are quoted identifiers, window functions, and dialect-specific operators like PostgreSQL's :: casts and @> containment; a one-line query that reproduces the issue beats a 200-line view.

Anything that changes query meaning rather than just whitespace — moved predicates, collapsed CTEs, dropped comments in an executable position — is a severity-one bug and jumps the queue.

Response time

Business hours are optimistic, but replies inside two business days is the promise. Meaning-changing format bugs get a fix within the week.