About this javascript minifier
Minify JavaScript by parsing its syntax and printing a compact representation with UglifyJS. Paste a script to remove redundant spacing and ordinary comments without using regular-expression replacements that could damage strings, regular expressions or division operators. A function such as function square(n) { return n * n; } becomes function square(n){return n*n}. The output is presented as text and is never executed by this tool.
Compression transformations and variable-name mangling are disabled. This conservative setting focuses on formatting while preserving identifiers and avoiding assumptions about side effects. Syntax errors produce a diagnostic instead of a partial result. Important licence comments supported by the parser may remain. The locally packaged parser accepts its supported JavaScript grammar; TypeScript annotations, JSX and unsupported future syntax need their own compiler step first.
Keep the readable source under version control and test the minified result in its target environment. This page does not bundle modules, resolve imports, transpile language features or generate source maps. Smaller formatting cannot make a slow algorithm faster.
Which controls should I check first?
The JavaScript Minifier form labels its controls as Input; Result. Use those labels to keep the source and settings separate. A sample argument that selects a mode is not additional source text. Choose the setting matching your intended operation before copying a result, and change it explicitly when comparing another mode. The labels describe what this form accepts; the worked examples below demonstrate only the stated supplied values.
How should I interpret this specific operation?
Compression and identifier mangling are disabled in the bundled minifier. The important comparison is therefore between meaningful source tokens, not a promised rewrite of your algorithm. A compact function can still have the same slow operation or error. Syntax outside the supported JavaScript grammar, such as TypeScript annotations, needs its compilation step before this parser can format it.
Worked helper values
These values come from the reproducible calculation examples supplied with this tool. Each row identifies the complete supplied arguments and the returned value. A visible ↵ denotes a line break and ⇥ denotes a tab in text examples. Settings appear alongside source data so that a different mode is not mistaken for an identical input. These are helper calculations, not observations of a live device, fetched target, image decoder, browser preview or downloaded file. Use the stated method above to relate the returned fields to the actual operation.
| Supplied values | Calculated return value |
|---|---|
| function square(n) { return n * n; } | function square(n){return n*n} |
What does formatting preserve?
Formatting changes the representation of structured source while using the parser's supported syntax. It is useful for inspection, but a readable result does not prove that an application accepts its data or that a program does what you intend. Check the selected dialect and supported language before converting. Keep a readable source copy when minifying, and keep the original compact input when investigating a formatter mismatch. The output is text on this page. Rendering it or executing it elsewhere introduces a separate step whose behavior depends on that environment, its libraries and its policy.
How should I investigate a parser error?
Reduce the input to a small complete example that still triggers the error. Check matching brackets, quotation marks, escaping, commas and the syntax specific to the selected format. Then add the removed portions back gradually. A parser can reject incomplete source that is valid only when combined with another file, or language extensions that require a compiler first. A successful parse establishes agreement with this parser's grammar. It cannot confirm table names in a database, resolve imported modules, or check a document against an application-specific schema. Those checks require the destination's own validation step.
Why do strings and escaping need special attention?
Quotation and escape rules belong to a particular format. A newline inside a quoted CSV field can be data, while a newline between records ends a row. A JSON string must escape its internal quotes; an HTML attribute has its own escaping requirements. Inspect strings containing separators or quotation marks after conversion rather than relying only on simple examples. A formatter should preserve their interpreted values even when their source spelling changes. Copy the generated source without the visual line-wrap characters an editor may add. Text that resembles markup remains data until another application chooses to interpret it.
How can I compare the result with the source?
For a formatter, compare the parsed structure or meaningful tokens rather than demanding identical whitespace. For a conservative minifier, inspect the specific changes the tool promises, such as comment removal or compact formatting. Reparse the output with the receiving application's parser if possible. For format conversion, compare field names, array order and value types: a number and a numeric-looking string are different values. Conversion may intentionally choose one representation, so note that decision when exporting a sample. A small representative record with punctuation and an empty value is more informative than a large file containing only simple numbers.
What belongs in an integration check?
Check the converted sample in the application that will use it. For source code, run the project's relevant tests after replacing a file. For markup, inspect generated elements and link targets before rendering untrusted content. For structured data, verify required fields and types against the receiving schema. This tool does not perform those application-specific checks. Keep relative paths and encoding conventions consistent with the destination, especially when copying generated source into a different directory. A smaller or prettier representation does not imply improved runtime performance, correct permissions, or compatibility with every version of the receiving software.
Does this rename variables?
No. Mangling and compressor transformations are disabled.
Does it execute the script?
No. Input is parsed and printed, never evaluated.
Can it compile TypeScript or JSX?
No. Convert those syntaxes to supported JavaScript first.