Use a browser-based SQL formatter that indents and re-cases the query entirely on your device. Safety is the point: real queries expose your table names, schema and often literal values from WHERE clauses, so a formatter that never uploads the query is the sane default.
A production SQL statement reveals table and column names, join structure, and frequently literal data: emails in WHERE clauses, ids, date ranges. Pasting that into a site that processes it server-side shares a slice of your schema and data with a third party. A client-side formatter parses and reprints the query in your browser, so none of it is transmitted.
A formatter normalizes indentation, line breaks and keyword casing so a 400-character one-liner from a log or an ORM becomes readable. It does not alter the semantics of the query, which is what makes it safe to run on anything from a quick SELECT to a machine-generated monster before a code review.
No. Formatting happens entirely in your browser, so schema and data in the query stay on your machine.
No. It only changes whitespace, line breaks and keyword casing. The logic is untouched.
Standard SQL formats cleanly, and common dialect syntax from PostgreSQL, MySQL and similar databases is handled for everyday queries.