JS Minifier Online: Free JavaScript Compressor

A JS minifier shrinks JavaScript by removing comments and extra whitespace so the file downloads faster. This free JS minifier online lets web developers and site owners paste code or upload up to five .js files, then see the original size, the compressed size and the percentage saved before copying or downloading the result.

What Is JavaScript Minification?

JavaScript minification is the process of rewriting a script into a smaller file that behaves the same way. The browser does not need your comments, indentation or blank lines to run the code, so a minifier strips what the machine ignores and keeps what it executes.

File size is measured in bytes, and the saving is the difference between the original and the minified version. If a script drops from 20 KB to 14 KB, you have saved 30%. Smaller scripts download and parse sooner, which helps pages become usable faster, especially on slow mobile connections. Google's Search Central documentation points to page experience and loading performance as things worth optimizing, and trimming script weight is one of the simplest ways to contribute.

Minifying vs. compressing vs. obfuscating

These three terms get mixed up. Minification changes the source text itself. Server compression such as gzip or Brotli packs the file again while it travels over the network, and the two work well together. Obfuscation deliberately makes code hard to read, which is a different goal. Minified code can look hard to read, but it is not a security measure, so never rely on it to hide secrets.

How to Use the JS Minifier

You can minify JavaScript in two ways: paste code into the box, or upload files. Both take under a minute.

1. Choose a tab at the top of the tool: Copy & Paste JS Code for a snippet, or Upload JS Files for files from your computer.
2. For pasted code, type or paste your script into the box labeled Enter your JS code to compress, then press the submit button.
3. For uploads, choose a .js file. Press Add Another JS File to add more, up to 5 files. A counter such as 1 / 5 shows how many slots you have used, and the remove button beside an extra file takes it off the list.
4. Press Compress Files to process the whole batch.
5. For pasted code, read the Optimized and Compressed JS Code box. Use the Copy button to put it on your clipboard or the download button to save it as output.js.
6. For uploads, read the results table with the columns #, File Name, Compression and Download, and save each minified file with its own download button.
7. Select Try New JS Document (or Upload New JS Files after a batch) to start again.

Worked Example: From 12.4 KB to 7.9 KB

Suppose you paste a 12.4 KB script with a license header, JSDoc comments above each function and four-space indentation. After you submit it, the tool shows the original size as 12.400 KB and the compressed size as 7.900 KB, followed by a line such as 36.3% size reduced. These figures are an illustration, not a promise for your code.

The math is simple: 7.9 divided by 12.4 is about 63.7% of the original, so the saving is 100 minus 63.7, or 36.3%. Most of that weight came from comments and indentation, which the browser never needed. If the same script were already written without comments and with tight spacing, the saving would be much smaller.

In an upload batch, you would see one row per file. A row for app.js might show 40.200 KB and 27.500 KB, while a row for a small helper file might barely change. Each row has its own download button, so you can save only the files you plan to deploy.

How Do You Read the Results?

The results show the original size, the compressed size and the percentage reduced, all in kilobytes. Compare the first two numbers to confirm the output is smaller, then check the percentage to judge how much you gained.

What a good result looks like

A script full of comments, documentation blocks and generous spacing often shrinks by a third or more. Well-trimmed code that already has few comments may shrink by a much smaller amount. Both outcomes are normal. The saving depends on how your file was written, not on whether the tool worked.

What a small saving means

This minifier uses conservative compression, so it focuses on safe changes and does not rewrite your logic. If you see a saving under 10%, your file probably has little removable text. The bigger wins then come from removing unused libraries, splitting code so each page loads only what it needs, and enabling server compression.

What to do with the output

• Save the download as a separate file such as app.min.js and keep your readable original in version control.
• Upload the minified file to your site and point your script tag at it.
• Reload the page, open the browser console and confirm there are no new errors.

If you need to inspect minified code later, run it through the code beautifier to restore readable formatting. To verify what changed between two versions, the code diff tool shows the differences line by line.

Who Should Use a JavaScript Minifier?

Anyone who ships JavaScript to a browser can benefit, particularly when there is no build step handling it automatically.

• Site owners and bloggers who add a custom script to WordPress, Shopify or a static page and want to keep it light.
• Front-end developers who need a quick check of how much a file can shrink without setting up a bundler.
• SEO specialists working through a page speed audit that flags unminified JavaScript.
• Students and freelancers preparing a small project for hosting.
• Agencies who receive a client's commented scripts and need a production-ready copy fast.

For a full page-weight cleanup, pair it with the CSS minifier and the HTML minifier, so your scripts, styles and markup are all trimmed.

Best Practices and Common Mistakes

Minify at the end of your workflow, test the output and keep your readable source. Most problems come from skipping one of those habits.

Keep the original file

Never overwrite your readable script with the minified version. Minified code is painful to edit, and you will want the commented source for future changes. A common convention is to name the output with a .min.js suffix.

Test before you deploy

Load the page with the minified file, click through the features that rely on that script and check the console for errors. Treat this as a normal release check, even though the tool is designed not to change behavior.

Fix errors in the source first

If the tool shows a message, the fix is usually simple:

• Enter source text first: the box was empty. Paste your code and submit again.
• Input exceeds the 500 KB limit: split the script into smaller parts, or minify it in sections.
• Choose a JS source file: only files ending in .js are accepted for upload. Rename or export the file correctly.
• A batch that fails: you can add at most 5 files, each up to 500 KB, and 2 MB across the whole upload. Remove a file or run two batches.
• A file that did not finish uploading: select it again and resubmit.

Do not minify twice

Running an already minified file through the tool gains almost nothing. If a library such as a vendor bundle already ends in .min.js, leave it alone.

Combine it with caching and compression

Minification is one layer. Serve the file with gzip or Brotli, set long cache lifetimes for versioned filenames, and load non-critical scripts with the defer attribute. If you handle redirects while renaming files, the htaccess redirect generator can help you avoid broken old URLs.

Limitations and Accuracy Notes

This tool is built for plain JavaScript text up to 500 KB per input, and it is deliberately cautious. Regular expressions and template strings stay unchanged, and your input is never executed, so pasting a script cannot run it. That cautious approach keeps behavior intact but means the savings may be smaller than an aggressive optimizer that rewrites names and structure.

A few other points to keep in mind:

• The tool minifies; it does not bundle modules, transpile newer syntax for older browsers or remove unused code.
• Upload mode accepts .js files only. If you searched for how to minify JSON, this page is aimed at JavaScript, so use it for script files rather than data files.
• Minified output is not protection. Anyone can reformat it, so keep API keys and secrets out of front-end code.
• Source maps are not produced, so debugging a minified file is harder. Debug with your original source.

Next Steps

Minifying your scripts is a quick, low-risk way to cut page weight and give browsers less to download. Paste your code or upload up to five files in the tool above, check the percentage saved, and download the result. For more utilities like this, browse the web developer tools collection.