Minify and beautify CSS, JavaScript and HTML
Paste code, drop a file, or open one — then minify it or turn a minified file back into something you can read.
Your code is processed on our server and is neither stored nor written to a log.
Requests left
What this is
A CSS minifier, a JavaScript minifier and an HTML minifier in one page — and the same three in reverse, when you need to read a file that was already minified. Paste the code, drop a file on the page, or point a script at the API.
CSS and JavaScript minifiers are conservative: they drop the whitespace and comments that can go and keep what cannot, so a value like calc(100% + 5px) comes back intact. Everything, minifying and beautifying alike, runs on our server.
Why this one
-
Safe by default
No aggressive rewriting to argue with afterwards. The output is the same code, smaller — not a guess at what you meant.
-
Both directions
Minify for production, beautify to read a minified file back. Two, four spaces or a tab, whichever your project uses.
-
An API, not only a page
One POST formats a file. No key, no account, no signature — put it in a build script and forget about it.
-
Nothing is kept
Your code lives in memory for the length of the request and is dropped. It is not written to disk and never reaches a log.
Common questions
Do I need a key?
No. The service is open and limited by IP address instead.
Is my code sent anywhere?
Only to our own server. Everything is processed there, in memory, and the code is neither stored nor logged.
Can I use it in a build script?
Yes, that is what the raw endpoints are for. Keep within the limits.
Why is my minified JavaScript renamed?
The minifier shortens local variable names, which is safe and is where most of the saving comes from. Beautifying will not bring the original names back — nothing can.
What is the largest file I can send?
2 MB in one request. Larger files are refused with 413 rather than truncated.
Endpoints, response shapes, error codes and the rate limits.