⌘ K
sql · minify · single-line · live

Minify SQL queries

Strips line and block comments, collapses whitespace, and tightens punctuation so multi-line queries compress onto one transport-ready line. Runs locally.

SQL Minifier
Input
112 B
6 lines
Output
108 B
1 lines
Status
ready
live
Ratio
0.96×
out/in
input · sql
output · minified sql
SELECT id,name,email FROM users WHERE active = true AND created_at > '2024-01-01' ORDER BY id DESC LIMIT 10;
Quick Start

How to minify SQL

Strip --line and /* block */ comments, then squash all whitespace runs and tighten the space around ( ) , and ; .

  1. 01

    Paste your query

    Any SELECT, INSERT, UPDATE, DDL — multi-line is fine.

    Parsing runs through Prettier’s standalone bundle (or the language-specific equivalent) loaded lazily — no parser ships until the tool is opened.

    sqlPrettierASTstandalonelazy
    input · sourceraw · AST
    SELECT id
FROM users;
    loaded · parsedAST · ready
  2. 02

    Comments stripped

    -- inline notes and /* block ... */ headers vanish from output.

    Indent width, tab style, and print-width re-format through a memoised pass — switching 2 → 4 spaces never re-parses, only re-prints.

    cleanindentprint-widthmemoisedlive
    kill · optionscomments · live
    -- note
→ gone
    options applied · livelive
  3. 03

    Whitespace tightened

    All space runs become a single space, then trimmed around ( ) , and ;.

    The formatter is deterministic and idempotent: running it twice produces byte-identical output, which keeps diffs and git noise to a minimum.

    packidempotentdeterministicdiff-cleanstable
    ws · formattedtight · ready
    a , b → a,b
    formatted · liveidempotent
  4. 04

    Copy or save

    Single-line SQL goes to clipboard or .sql file — your query never leaves the tab.

    Download writes a Blob with the language-appropriate extension; copy uses navigator.clipboard.writeText so the output preserves all whitespace exactly.

    exportclipboardbloblanguage MIMEclient-side
    ok · copiedready · done
    ✓ Copied
    shipped · ready to shipsuccess
Pro tips

Formatting tips that keep diffs sane

Pick one config and pin it

Inconsistent formatting causes diff churn. Commit .prettierrc / .editorconfig and enforce in CI.

Format on save

Editor integration is faster feedback than a pre-commit hook. Use both for belt-and-braces.

Idempotency matters

Running the formatter twice should produce identical output. Test this on a representative file.

Match the language community

Default to community conventions: 2 spaces for JS/CSS, 4 for Python, tabs for Go. Fights over indent are a productivity tax.

Print-width drives wrapping

80, 100, and 120 are the common targets. Wider lines parse fast but review slower side-by-side.

Don’t mix formatters and linters

Prettier handles whitespace; ESLint handles correctness. Disable overlapping rules to avoid fight-club configs.

Related toolsSQL FormatterGraphQL MinifierXML MinifierJSON MinifierYAML FormatterHTML Minifier
Use Cases

When to minify SQL

Embedding, logs, transport efficiency.

Embed in code

Drop the query into a single Python or Go string literal. Idempotent: running the formatter twice produces byte-identical output, which is the foundation of a clean CI gate. Pair with a pre-commit hook so PRs arrive already formatted, focusing review on logic.

idempotent

Log lines

One-line queries play nice with grep and log shippers. Pairs with EditorConfig + .prettierrc for end-to-end consistency. Whitespace-only changes vanish so reviewers see real diffs, and git blame stays honest about who wrote what.

CI-ready

URL params

Pass a query through a GET param without newline escapes. Output respects your indent width, tab style, and print-width — settings carry over for repeat runs. Switching 2-space to 4-space costs nothing in CPU but standardises an entire codebase.

diff-clean

JSON payload

Compact a query before stuffing into a JSON request body. Format-on-save is the fastest feedback loop; CI is the safety net. Together they make inconsistent indentation a thing of the past and free up review cycles for genuine concerns.

PR-friendly

Cron jobs

Pipe a one-line query straight to psql / mysql. Whitespace-only changes don't trigger downstream content-hash invalidations, so CDN cache keys and CI cache layers stay warm. Real changes get all the rebuild budget.

review-ready

Snippet docs

Show the query compact-form in a row next to a description. Pairs with linters (ESLint, Stylelint, pylint) that catch what formatting alone can't — bugs, unused imports, dead code. Each tool stays in its lane, and the codebase stays clean.

deterministic
FAQ

Frequently asked questions

Only if your query relies on whitespace inside string literals being preserved verbatim. Most SQL parses identically.
No. Case is left alone — use the SQL Formatter for canonical casing.
Whitespace inside single-quoted strings is collapsed too. Be cautious with literal whitespace in column data.
Yes — Postgres, MySQL, SQLite, T-SQL all minify the same; punctuation rules are universal.
No — the minifier runs locally in your browser tab.
Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

Sent straight to the maintainers · no account needed
47 in queue·8 shipped this month
Request queued. Thanks!