Remove unnecessary JavaScript whitespace and comments. Reduce source size while keeping variable names and avoiding compression rewrites.
How to use
Paste JavaScript and generate the minified result. Keep your readable source separately and test the output in the application before publishing.
Example
A function with indentation and comments becomes a compact line. Its identifiers remain recognizable because name mangling is disabled.
FAQ
Is this a production bundler?
No. It does not resolve imports, combine modules, or remove unused dependencies. Use your build pipeline for those tasks.
Related tools
A practical task
Test the compact output in the same runtime as the source. A browser script and a server module can have different available globals even when both parse. Keep a readable original and any required notices alongside the build process.
Another useful question
Will shorter code hide its logic?
No. Minification is not a secrecy boundary. Never put credentials in a delivered script, and do not use compact source as access control.
Details for interpreting the result
| Detail | Explanation |
|---|---|
| Formatting and behavior | A formatter changes presentation of source code. It does not prove that a program calculates the right value or that a page looks correct. Keep behavior checks separate from indentation and spacing checks. |
| Readable and compact source | Minification produces a compact delivery copy. Keep the readable source for maintenance and rebuilding. Editing only a compressed copy makes reviews harder and loses the useful context removed with comments. |
| Comments in source files | Comments can contain licenses, build notes, and explanations as well as disposable text. Before removing them, check the obligations of bundled assets and keep important notices in the appropriate source or distribution file. |
| Regex engine | Regular expression syntax belongs to an engine. A pattern accepted by JavaScript can differ from a pattern in another language. Test the exact engine and flags used in the application that will run it. |
| Strict JSON syntax | JSON needs double quotes around keys and string values. Objects use braces and arrays use square brackets. Comments and trailing commas belong to other formats, so remove them before treating a source as JSON. |
| Syntax and schema | A document can be syntactically valid yet contain the wrong fields or types for an application. Syntax checks confirm the format; schema and business rules determine if the receiving system can use the data. |
| Source boundaries | A summary or rewrite works from the material you provide. A URL alone does not supply the full article in this interface. Include the relevant passage and keep citations attached to the claims they support. |