What this workspace does
A cleaned SVG download and an explicit before/after byte count.
SVG workspace · browser local
Optimize an SVG without sending it away.
Choose an SVG up to 2 MiB to remove comments, metadata blocks, scripts, external references, and unnecessary whitespace from a separate local copy. Structural-complexity limits apply before preview.
Use it accurately
This conservative optimizer does not rewrite paths or promise the smallest possible SVG. Review the output before production use.
Private browser processing
Selected files are processed in the current browser session. Aftermath has no account, cloud file storage, or server-side file-processing job.
How to use this tool
Clean supported SVG markup locally when you want a separate SVG copy with inactive or unnecessary content removed and before-and-after byte counts shown. The route does not promise that every renderer, font, script, or destination will behave the same way. Open the cleaned result in the target environment before treating it as ready for use.
What to choose and what you get
What to choose
- one SVG file up to the route's displayed size and complexity limits
Result
- a separately downloaded cleaned SVG with before-and-after byte counts
Supported formats
- Accepted formats: SVG.
- Output formats: SVG.
Browser support and permissions
- Modern browser with JavaScript, DOMParser, SVG rendering, and the route's displayed element, attribute, and nesting limits.
- No camera, microphone, or screen permission is needed.
Worked example
A generated SVG contains editor metadata and redundant markup and needs a smaller sanitized copy for review.
Starting facts
- The source stays below displayed size and complexity limits.
- Active and external references are not permitted in the output.
Observed operation: Parse and sanitize the SVG, remove allowed redundant content and report before-and-after bytes for the separate copy.
Review the result: Compare the rendered cleaned SVG with the source and inspect the reported byte difference before replacing any use.
Boundary: Cleanup can change unsupported SVG features and cannot guarantee identical fonts, animation, filters or rendering everywhere.
Choose another tool when
- Choose another route when the task needs a format other than SVG preview, cleanup, or PNG export.
Check your result
- This conservative optimizer does not rewrite paths or promise the smallest possible SVG. Review the output before production use.
Things to know
- Review the result on the intended device before relying on it.
Privacy boundary
The selected SVG stays in the current browser session and is not sent to an Aftermath processing service. How local processing is verified.
What this tool verifies
Checks the displayed limits and reports or creates a separately downloaded cleaned SVG with before-and-after byte counts from one SVG file up to the route's displayed size and complexity limits.
Check before sharing
A sanitized preview or export does not prove that every renderer, font, script, or destination will treat the SVG identically.