CSS obfuscation is the process of renaming class names and IDs in your stylesheets to short, meaningless identifiers (e.g., .main-navigation → ._a). This serves two main purposes: reducing file size by shortening verbose class names, and making your CSS harder to read for anyone inspecting your code — a lightweight layer of intellectual property protection. It's commonly used in production builds alongside minification to ship leaner, less readable stylesheets.

Not if done correctly. The key is consistency — all references to a class name must be updated simultaneously. This tool handles CSS class selectors, ID selectors, and can optionally synchronize your HTML markup. However, class names referenced in JavaScript (e.g., document.querySelector('.my-class')) also need updating. Use the Exclude field to protect class names that JavaScript relies on, or integrate this tool into a build pipeline that also processes JS files. We recommend testing thoroughly after obfuscation.

The mapping table shows exactly how each original class name or ID was renamed. It's a lookup reference — essential for debugging or if you need to reverse the process. The tool generates short names sequentially (e.g., _a, _b, _c, ..., _z, _a0, _a1, ...) with your chosen prefix. You can expand the mapping table panel above to inspect all renames after running obfuscation. This transparency ensures you're always in control of the transformation.

Minification removes unnecessary whitespace, comments, and redundant characters (like trailing semicolons) to reduce file size — the CSS logic stays identical. Obfuscation goes further by renaming identifiers (class names, IDs) to meaningless short tokens, changing the semantics while preserving functionality. Combined, they deliver maximum size reduction: minification strips formatting overhead, while obfuscation shortens the actual identifier strings. This tool can do both in one click.

Absolutely. Use the Exclude field in the options bar. Enter comma-separated class names or IDs to protect (e.g., active, open, icon-*, swiper-*). Wildcards with * are supported — icon-* will protect icon-home, icon-user, etc. This is crucial for state classes toggled by JavaScript or for third-party library prefixes that must remain intact. Excluded names appear unchanged in the output.

Not without the mapping table. Obfuscation is deterministic but lossy in terms of readability — the original names are discarded. However, if you save the mapping table (shown after obfuscation), you can manually reverse the process or use it for debugging. For production workflows, keep the mapping as part of your build artifacts. This tool does not store or transmit any of your data — everything runs client-side in your browser.