SVG editing

Clean SVG

Remove scripts, event handlers, and editor metadata while aiming to preserve the artwork.

SVG → SVG · Server processing

The instrument

Convert with intent.

Drop a file and set your options. Review the result before downloading.

Checking conversion service availability…

Drop a file here

Accepts .svg — max 70 MB

Allowed formats: .svg. Maximum file size: 70 MB.

Conversion settings

What gets cleaned

✓
Scripts & handlers gone
<script>, onclick/onload, and javascript: URLs stripped
✓
Visual identity kept
Paths, fills, strokes, viewBox, gradients, and embeds unchanged
✓
Editor junk removed
Inkscape/Sodipodi metadata and comments dropped when safe
✓
Responsive when safe
Fixed width/height removed only when viewBox already exists

Before you convert

Inspect output before using it in a security-sensitive context. Cleaning is not a universal safety guarantee.

Clean SVG markup without promising universal safety

SVG files can contain more than visible paths: editor metadata, event handlers, scripts, references, and HTML-like content can all appear in the markup. This server tool aims to remove unsafe or unnecessary content while retaining drawing information.

Cleaning is different from aggressively optimizing path geometry. The engine aims to keep path data, fills, strokes, gradients, and the viewBox rather than merging shapes or rounding coordinates for the smallest possible file. Removing metadata alone may produce only a small size reduction.

Useful situations

Reduce editor-specific metadata in an exported SVG before reviewing it for use elsewhere.
Inspect how a simpler SVG behaves in a downstream application.
Prepare artwork for a controlled review workflow without treating the result as a security certification.

How to use Clean SVG

Select an SVG within the displayed upload limit. Keep an unchanged copy for visual comparison.
Run Clean SVG and inspect the preview for missing elements or changed layout.
Download and review the markup before placing it in a security-sensitive environment. Continue to apply the destination’s own sanitization and security controls.

What to expect

The cleaning route is server-side; it is not the same restrictive sanitizer used by the local customization studio.
Some fixed dimensions may be removed when a viewBox already exists, which can change how a host page sizes the SVG.
Parsing and sanitizer limitations remain possible. A successful response or matching preview is not proof that markup is safe to insert inline.

Frequently asked questions

Is Clean SVG a guarantee that an SVG cannot execute active content?

No. This tool is not a security certification. Do not bypass your application’s sanitizer, content security policy, or review process because a file has been cleaned.

Will SVG cleaning always reduce the download size?

No. The amount of metadata varies, and serialization can change markup length. If the source is already compact, size savings may be small or absent.

Does Clean SVG trace embedded photos into paths?

No. Cleaning reviews existing SVG markup; it does not vectorize raster content or reconstruct editing layers.