CSS Comment Remover

Comments earn their place in source code and rarely earn it in shipped assets. The useful cases for removing them are specific: you are pasting CSS into a platform field where a long file is unwieldy, you are handing a stylesheet to someone and the notes are stale or internal, a build tool has injected sourcemap and annotation comments you do not want, or you are measuring how much of a file is documentation. In each case you want the rules preserved and readable, which is exactly what this does and what a minifier does not.

Comments are the only place a stylesheet can explain itself — why a magic number exists, which browser bug a workaround targets, what a non-obvious selector is for. That context is genuinely expensive to reconstruct once it is gone, and no formatter can bring it back. Treat the commented file as your source of truth in version control and the stripped file as output. If you find yourself stripping comments from the only copy you have, copy it somewhere first.

Minifying removes comments and also collapses every newline and indent, producing one dense line. This tool removes only the comments and leaves your formatting exactly as it was, so the file stays readable. That is what you want when the goal is tidying rather than compressing — for example stripping a build tool's annotations, removing stale notes and commented-out experiments before a handover, or preparing a snippet for documentation where the original comments would be noise.

Yes. Unlike server-side languages, CSS comments are part of the file the browser downloads, so anything you write in one is public and costs bandwidth. This matters more than people expect: a commented-out block explaining an unreleased feature, a client name, or an internal ticket URL is visible to anyone who opens the stylesheet. Strip comments from anything you serve publicly if they contain information you would not put in a public repository.

Comment removal is string-aware, so sequences that merely look like comment markers inside a quoted string or a url() value are left alone. This matters most for base64 data URIs, which can contain almost any character sequence. If you are working with a file full of embedded images, run it through and check the output — the byte-size difference will tell you immediately if more was removed than expected.

If the CSS came from a third party, check its licence first. Permissive licences such as MIT still require the copyright notice to be preserved in distributed copies, and for a stylesheet that notice is usually a comment at the top of the file. Removing it is a licence violation even though nothing will visibly break. Strip comments freely from CSS you wrote; be careful with CSS you did not.

No. Every one of these tools runs entirely in your browser using JavaScript. Your stylesheet is never uploaded, never logged, and never sent to any server — you can confirm this by opening your browser devtools Network tab while you work, or by disconnecting from the internet after the page loads and watching everything continue to function. That makes it safe to paste proprietary or client CSS.