Minification is the process of removing all unnecessary characters from CSS, JavaScript, and HTML source files without changing their functionality, resulting in smaller file sizes that load faster in the browser. This includes stripping out whitespace, line breaks, comments, and redundant formatting that developers use to keep code readable but that the browser does not need to execute it correctly.
When a developer writes CSS or JavaScript, the source code is intentionally formatted for human readability. Variable names are descriptive, indentation is consistent, and comments explain the logic. None of this formatting carries any meaning for the browser's rendering engine or JavaScript interpreter. Minification removes all of it, and in the case of JavaScript, tools can also shorten variable and function names to single characters, a technique sometimes called mangling. The result is a compact file that is functionally identical to the original but can be a fraction of the size.
The practical benefit is a direct reduction in the amount of data transferred between the server and the user's browser. Smaller files are downloaded more quickly, which reduces page load times. This matters because page speed is a measurable factor in user experience and is directly tied to Core Web Vitals, the set of metrics Google uses to evaluate loading performance, interactivity, and visual stability. Faster-loading pages tend to rank better in search results and retain more visitors.
Minification is almost always handled automatically as part of a build process rather than performed by hand. Tools such as Terser for JavaScript and cssnano for CSS are widely used to produce minified output files, typically named with a .min.js or .min.css suffix to distinguish them from the original source. These tools are often integrated into a bundler like webpack or Vite, which combines and optimizes assets as part of the deployment pipeline.
Minification is closely related to, but distinct from, other optimization techniques. Tree shaking removes unused code entirely before bundling, while minification compresses only the code that remains. Compression at the network level, such as Gzip or Brotli encoding applied by the web server, works alongside minification and reduces file sizes further still. The two approaches are complementary: minification reduces the raw file size, and network compression reduces the size of the data actually transmitted.
For any website where performance is a priority, minifying CSS and JavaScript assets is considered a foundational step. Most modern frameworks and deployment platforms apply minification automatically in production builds, meaning developers can write readable, well-commented code during development while serving optimized assets to end users.