Formatted SQL is great for humans. But when you are embedding SQL in an API response, storing it in a log system that charges by the byte, or shipping it over a slow network, all that whitespace is just overhead.
A SQL minifier strips out every unnecessary space, line break, and indentation — producing a single-line query that is functionally identical but 40-60% smaller.
Minification is the opposite of formatting. You are trading readability for size. Here is when that trade makes sense:
The minifier applies several transformations:
-- single-line and /* block */ comments are removedIt does not touch string literals. If you have 'Hello World' in your SQL, the space between Hello and World is preserved.
If your pipeline sends SQL to a deployment API, minifying reduces network transfer time and API rate limit consumption. Over thousands of deployments, this adds up.
Minified migration files are smaller to store and faster to apply. Keep the formatted version in your repo, minify in the deployed artifact.
No. The minifier only removes whitespace and comments. All SQL logic, identifiers, and string literals are preserved exactly.
Typically 40-60% for formatted SQL. For heavily indented queries with comments, up to 70% reduction is common.