500+ fast, free tools. Most run in your browser only; Image & PDF tools upload files to the backend when you run them.
Minify SQL by removing comments and redundant whitespace safely.
When SQL needs to live inside source code — embedded in a Go string, packed into a JSON config, or sent over a URL parameter — multi-line formatted queries are awkward. The SQL minifier strips redundant whitespace, optionally removes comments, and produces a single logical line without changing query logic. Backend developers embedding SQL in Go, Rust, Java, or Python, ORM users storing queries in JSON configs, and SREs packing queries into URL parameters all use minification as a packaging step. The tool is string-literal safe: whitespace inside quoted values is preserved — only outside-quote whitespace is collapsed. Comment removal is optional so you can keep query hint directives the database reads. Pair with the SQL Formatter to reverse the operation with no information lost.
Removes line breaks, leading and trailing spaces, and consecutive spaces throughout the query — never alters keywords, identifiers, operator symbols, or string literals. The resulting query is logically identical to the original and produces the same execution plan.
Choose to strip -- and /* */ comments for lean production output, or keep them when your team logs annotated queries for debugging. MySQL and PostgreSQL /*+ HINT */ directives are preserved when comment stripping is disabled.
Whitespace inside single-quoted string values is preserved exactly — only whitespace outside quoted strings is collapsed. A WHERE clause like WHERE message = 'failed login attempt' keeps its internal spaces intact.
Even a 200-line formatted query becomes one logical line, ready for backtick embedding in Go, triple-quoted strings in Python, or escaped string literals in Java — no multi-line string workarounds needed.
Pair with the SQL Formatter to reverse the operation. Minify for source-code embedding and bulk loading, format for review and pull requests. No information is lost in either direction — the round-trip is lossless.
Production queries containing schema names, customer identifiers, and proprietary business logic stay in your browser tab. No data is sent to any server and no logs are written during minification.
Input: SELECT u.id, u.email FROM users u WHERE u.created_at > '2025-01-01' AND u.active = true ORDER BY u.id;
Output: SELECT u.id,u.email FROM users u WHERE u.created_at>'2025-01-01' AND u.active=true ORDER BY u.id;
Input: -- top customers SELECT id, name /* only paid */ FROM customers WHERE plan='pro';
Output: SELECT id,name FROM customers WHERE plan='pro';
Input: SELECT * FROM logs WHERE message = 'failed login attempt';
Output: SELECT * FROM logs WHERE message='failed login attempt';