The tool removes XML comment blocks such as export notes and editor annotations, then validates the remaining SVG.
Why remove comments
Comments can add unnecessary bytes or reveal workflow notes. Removing them is a safe cleanup step before optimization or embedding.
Remove SVG Comments applies rendering-safe rules and reports the byte delta so the size-versus-risk trade stays explicit.A pipeline from a 41.2 KB input through a safe pass to a 15.8 KB output, illustrating how Remove SVG Comments reports the byte delta.
What gets removed
Editor metadata, comments, empty and hidden elements, redundant group nesting, default attribute values, and excess decimal precision make up most SVG waste. These are the first targets because removing them rarely changes rendering.
Safety defaults
Rendering-safe options come first: the viewBox, referenced IDs, gradients, filters, and masks survive, while active content such as scripts is removed. Stronger passes exist but deserve a visual check.
How to verify nothing broke
Compare the original and the result at small and large sizes, and confirm anything CSS selectors or animation targets reference still resolves. The byte delta is reported so the size-versus-risk trade stays explicit.
Expected savings
Designer-exported files commonly shrink 20-60%. Hand-written or previously optimized files shrink far less, which is expected rather than a sign the tool missed something.
How to use
•Paste SVG. Paste SVG markup that may contain comments.
•Remove comments. The tool strips XML comment blocks from the source.
•Copy output. Copy the comment-free SVG from the output panel.
Frequently asked questions
Does it remove metadata?
No. This tool only removes comments. Use Remove SVG Metadata for metadata blocks.
Does it change visible artwork?
It should not. Comments are not rendered SVG content.
Does it validate after removal?
Yes. The cleaned SVG is parsed before it is shown.
Is Remove SVG Comments free?
Yes. SVGKit tools are free to use with no account required.
Does Remove SVG Comments upload my files?
No. The tool runs entirely in your browser, so your files never leave your device.
Will Remove SVG Comments change how my SVG looks?
With safe defaults it should render identically. Aggressive options can subtly affect edges, so compare renders for important artwork.
Are scripts removed?
Yes. Active content is stripped, which is also the safer choice for SVG from unknown sources.
Can I run it twice?
Yes, but the second pass rarely finds more waste. A file that has already been optimized shrinks very little.
Remove SVG Comments
Strip XML comments from SVG markup while preserving visible SVG elements.
Result
Choose an SVG file, paste SVG markup, or load the sample to begin.
Remove SVG Comments
OptimizeStrip XML comments from SVG markup while preserving visible SVG elements.
Loading...
Page context
Where Remove SVG Comments fits
Remove SVG Comments strips XML comments from SVG markup while preserving visible SVG elements.
Related guides
What it removes
The tool removes XML comment blocks such as export notes and editor annotations, then validates the remaining SVG.
Why remove comments
Comments can add unnecessary bytes or reveal workflow notes. Removing them is a safe cleanup step before optimization or embedding.
What gets removed
Editor metadata, comments, empty and hidden elements, redundant group nesting, default attribute values, and excess decimal precision make up most SVG waste. These are the first targets because removing them rarely changes rendering.
Safety defaults
Rendering-safe options come first: the viewBox, referenced IDs, gradients, filters, and masks survive, while active content such as scripts is removed. Stronger passes exist but deserve a visual check.
How to verify nothing broke
Compare the original and the result at small and large sizes, and confirm anything CSS selectors or animation targets reference still resolves. The byte delta is reported so the size-versus-risk trade stays explicit.
Expected savings
Designer-exported files commonly shrink 20-60%. Hand-written or previously optimized files shrink far less, which is expected rather than a sign the tool missed something.
How to use
Frequently asked questions