Minify
GraphQL Minifier
Paste GraphQL on the left, hit Run, copy a smaller file that is harder to read and quicker to download. No Node, no pip, no Docker for a five-minute job. That is the graphql minifier.
Drop a file on the left. Drafts stay in this browser. Shortcut: Ctrl or Cmd + Enter to run.
How this graphql minifier works
- Paste or drop a .graphql file into the input on the left.
- Flip options if you see them (comments, indent, case). Defaults are the safe ones.
- Hit Run, or Ctrl / Cmd + Enter. Leave “Process on server” off unless you mean it.
- Read the status line, then copy, download, or jump to a related tool.
What this graphql minifier is for
The file is already in front of you. You need to minify it without opening a whole IDE profile. Paste, run, copy. Typical timing: right before a static deploy, an email snippet, or an inline SVG — not while you are still designing the component.
You walk away with a smaller file that is harder to read and quicker to download.
What it will not pretend to be
This is not a replacement for gzip/Brotli, tree-shaking, or a real bundler. Those still matter more at scale. Selection sets minify by collapsing space. Field arguments and aliases remain; this is not a query planner.
By default nothing leaves the tab. Tick “Process on server” only if you want to compare results or use gzip numbers that match the server library.
A practical way to use it
Drop a .graphql file onto the input or paste. Flip options if they are there. Run. Read the status line. Copy or download. Drafts stay on this device so a refresh does not punish you.
When you are done, hop a related tool instead of starting over: minify and beautify toss the file back and forth, format and validate often share a parser, convert wants valid input first.
The small print that saves a round-trip
Selection sets minify by collapsing space. Field arguments and aliases remain; this is not a query planner.
You searched “graphql minifier online.” You got an editor, not a login wall. That is the deal.
Frequently asked questions
What does a GraphQL minifier actually remove?
It deletes the bytes humans needed while writing: comments, extra spaces, extra line breaks. Meaning should stay. A tiny pass looks like query {\n tool { name }\n} becoming query { tool { name } }. If the output changes layout or throws a syntax error, you collapsed something that was not decoration.
Is minifying GraphQL the same as compressing with gzip?
No. Minify/beautify/format change the source you can still read in a tab. Gzip and Brotli change how that source travels on the wire. query { tool { name } } still gzips — usually better, because comments are gone. You want both on a real site. A 10 KB stylesheet might become 3 KB on the wire after gzip even before you obsess over one more space.
Can minifying GraphQL break what I already put live?
Selection sets minify by collapsing space. Field arguments and aliases remain; this is not a query planner. Glance at the output once. A 20-second read beats a 20-minute “why did production go weird” thread.
Got a simple before-and-after for graphql minifier?
Sure. Before: query {\n tool { name }\n} After: query { tool { name } }. That is the whole mood of the tool — same job, different clothing. If your real file is huge, try a representative slice first so you can see the rule, not a wall of text.
What about comments, strings, and data that look like code?
Strings are data. 'a + b' is not math. Comments are notes — minify may drop them, beautify should keep them if the engine sees them. GraphQL has its own trap: Selection sets minify by collapsing space. Field arguments and aliases remain; this is not a query planner.
Any fun GraphQL fact worth remembering?
Fun fact: GraphQL ignores commas. tool { name, slug } and tool { name slug } are the same query. Minify can drop the commas; the server does not miss them.
Do I still need a bundler, Prettier, or a schema tool?
For an app in git: yes — keep the project formatter and the bundler. This graphql minifier is for the five-minute paste: a log line, a vendor dump, an email template, an API body. Different altitude, same mountain.
When should I not use a graphql minifier?
Skip it when the file is a binary, when you need a full language compiler, or when a single sample cannot represent the format (Excel workbooks, YAML with anchors, HTML that is really a React tree). Also skip minify as your only copy of source. Keep a readable original.