Run this tool instantly in your browser. No signup and no server-side processing.

JavaScript Minifier

Minify JavaScript code by removing whitespace, comments, and redundant bytes.

Drag and drop a JavaScript file here, or choose a file to import.

Input

Output

JavaScript Minifier: complete usage guide

Minify JavaScript safely with a review-first workflow so you can reduce payload size while preserving runtime behavior across bundlers, browsers, and CI pipelines.

What this tool does

It compresses JavaScript by removing non-essential whitespace and comments, producing compact output suitable for shipping assets, snippets, and embedded scripts.

It provides a controlled, local minification step for quick validation when you need to compare before-and-after code during bug triage, release review, or partner handoff.

It helps expose syntax and transformation assumptions early, so teams can catch malformed input, unsupported constructs, or accidental copy artifacts before deployment.

Typical use cases

Prepare a pre-release minified snippet for static embed scenarios where you need compact output without waiting for full bundler pipelines.
Compare minified output from this tool with CI/build output to investigate environment mismatch or plugin-order regressions.
Trim helper scripts used in dashboards, browser extensions, or internal admin tools where fast delivery and predictable behavior both matter.
Generate lightweight script fixtures for documentation, test cases, or postmortems that must show realistic compressed payloads.

Input examples

Utility function snippet

function normalize(v) { return Array.isArray(v) ? v.filter(Boolean) : [v].filter(Boolean) }

Module-like code

const cache = new Map(); export function get(id){ if(cache.has(id)) return cache.get(id); }

Incident repro sample

/* repro */ const flag = true; if(flag){ console.log('deploy-check') }

Output examples

Minified result

function normalize(v){return Array.isArray(v)?v.filter(Boolean):[v].filter(Boolean)}

Semicolon-preserved style

const cache=new Map;export function get(id){if(cache.has(id))return cache.get(id)}

Before/after verification note

Run the same input through CI minifier and compare diffs to confirm parity.

Common errors and fixes

Input contains non-JavaScript text

Confirm the pasted payload is plain JS and remove shell prompts, HTML wrappers, or markdown fences.

Minified output differs from bundler output

Check bundler plugins/transforms (Babel, SWC, terser config) and compare feature flags between environments.

Unexpected runtime error after minification

Validate syntax first, then isolate the smallest failing snippet and test strict-mode/module differences.

Source maps expected from this step

Use your build pipeline for source maps; this tool is intended for quick payload and syntax validation.

Security and privacy notes

All transformations run locally in the browser, so proprietary scripts and internal snippets are not uploaded by default.
Redact secrets, access tokens, and environment constants before sharing minified output in tickets or chats.
Treat generated output as build artifact material and keep production-grade auditing/signing in CI.

Step-by-step workflow

Start with a minimal input for JavaScript Minifier and verify baseline behavior first.
Make assumptions explicit: encoding, delimiter strategy, and timezone.
Change one variable at a time and compare output diffs.
Keep one verified output snapshot as a team reference.

Quality checklist before sharing output

Confirm JavaScript Minifier output is deterministic across repeated runs with identical input.
Check boundary inputs (empty values, long fields, invalid characters).
Remove sensitive data before sharing output externally.
Verify final rendering on both desktop and mobile viewports.