⌘ K
graphql · minify · single-line · live

Minify GraphQL documents

Strips # comments, squashes whitespace, and tightens punctuation so queries and fragments fit on one transport line. Runs locally.

GraphQL Minifier
Input
190 B
16 lines
Output
118 B
1 lines
Status
ready
live
Ratio
0.62×
out/in
input · graphql
output · minified graphql
query GetUser($id:ID!){user(id:$id){id name email posts(first:5){...PostFields}}}fragment PostFields on Post{id title}
Quick Start

How to minify GraphQL

Comments go first (# to end-of-line), then whitespace runs collapse and punctuation tightens around { } ( ) , : and the spread ... operator.

  1. 01

    Paste a query

    Query, mutation, subscription, fragment — all are handled the same way.

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

    gqlPrettierASTstandalonelazy
    input · sourceraw · AST
    query { me { id } }
    loaded · parsedAST · ready
  2. 02

    Comments stripped

    # notes are removed completely — they have no runtime meaning anyway.

    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 · options# · live
    # note → gone
    options applied · livelive
  3. 03

    Punctuation tightens

    Braces, parens, colons and the spread operator lose their surrounding spaces.

    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,c}
    formatted · liveidempotent
  4. 04

    Copy or save

    Single-line GraphQL goes to clipboard or .graphql file. Local-only.

    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 toolsGraphQL FormatterJSON MinifierSQL MinifierXML MinifierJavaScript MinifierHTML Minifier
Use Cases

When to minify GraphQL

Persisted queries, transport, embedding.

Persisted queries

Hash a compact form so server and client agree byte-for-byte. 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

GET requests

Stuff a query into a URL parameter without newline escapes. 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

Embed in code

Drop the query into a JS / Python string literal cleanly. 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

Mobile apps

Smaller queries = less data on the wire on flaky connections. 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

Cache keys

Use the minified text as a stable cache key. 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

Docs snippets

Show the compact form alongside the pretty form in API docs. 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

No — GraphQL ignores whitespace between tokens. Only string literals preserve significant whitespace.
Whitespace inside triple-quoted strings will collapse. Inspect output if you rely on multi-line strings.
Variable references are tokens; their whitespace tightens like everything else. Names are preserved.
Preserved verbatim, just compacted (@include(if:$x) etc.).
No — minification 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!