SQL Formatter

A SQL Formatter takes a tangled query and lays it out with clean line breaks, indenting and keyword case, so you can read it, review it and share it. Pick from eight dialects, set the keyword case, and the formatted SQL appears on the same screen. It is free, runs in your browser, and nothing you paste is uploaded.

How the SQL Formatter works

Paste a query in whatever state it arrived in: one long line from a log file, a nested block copied out of application code, or a wall of lowercase keywords. Pick the dialect that matches your database, set the keyword case, and the query is laid out again with line breaks and indenting that follow its structure.

1. Paste your SQL into the box.
2. Pick the dialect that matches your database, from Standard SQL and MySQL to PostgreSQL, BigQuery and PL/SQL.
3. Choose the keyword case: upper case, lower case, or preserve the case you typed.
4. Read the formatted query, then copy it back into your editor, console or ticket.

The dialect choice is more than a label. A # character starts a comment in MySQL and means something else in PostgreSQL, and a backslash inside a string is an escape in MySQL but a plain character in PostgreSQL and SQLite. Formatting with the wrong dialect can lay a query out in a way that misleads the reader, so the picker sits at the top for a reason. Placeholders such as ? and $1 are left exactly where you put them, because pasted production queries carry them all the time.

When a SQL Formatter helps most

Most SQL worth formatting was never typed by a person. Queries generated by an ORM, pulled from a slow query log, or copied out of an error message arrive as one dense line with the joins buried in the middle. Ten seconds of formatting turns that line into a shape you can scan, and the filter you were hunting for stops hiding.

Code review is the second home of this tool. A teammate drops a query into a pull request or a ticket, and everyone on the thread has to judge it fast. Formatted, the joins line up, the conditions group themselves, and the missing filter or the wrong join shows itself in a way a single line never allows.

Documentation and support threads ask for the same thing. A query pasted into a wiki page, a runbook or a message to a database admin gets read by people who did not write it. A query nobody can read is a query nobody can review, and formatting is the cheapest review aid there is.

SQL Formatter limits, stated plainly

This tool formats. It does not run your query, and it cannot check it against a real database. Table names, column names and permissions live in your database, not on this page, so a neatly formatted query can still be plain wrong.

Some vendor specific syntax may not parse. When that happens you get an error rather than a quietly wrong layout, and the usual cause is a dialect mismatch, so check the picker first. Formatting changes layout only. It does not fix logic, speed up a slow query, or rewrite anything you pasted.

The library that does the formatting loads on demand when you open the page, which keeps the page itself light. On a slow connection the first format can pause briefly while that library arrives. After that, formatting is as fast as you can paste.

Your SQL stays in your browser

The formatting runs on your device. Your queries are not sent to a server, not logged and not stored by ToolPeko. There is no daily allowance, no account and no sign-up prompt waiting at the end. Paste one query or fifty, and the only copy of each one is the one in your tab.