Remove empty canvas without changing the vector artwork
Foldout recalculates the SVG bounds around the visible paths, previews the trimmed result, and writes a separately named vector file by default.
Trim SVG recalculates the vector canvas around the visible artwork and previews the rendered result before it becomes the file you use. Keep the source by default, write a clearly named trimmed copy, and let unsupported SVGs fail safely instead of risking the original.
Start the 14-day trial in the app. No payment method is required to try Foldout.
Remove empty canvas around visible vector paths.
Preview the rendered result before relying on the new bounds.
Write a separately named trimmed SVG by default.
Require explicit confirmation before replacing a source.
Leave unsupported SVGs untouched when safe trimming is not possible.
Review the source-protection policy, stable output, and actual rendered SVG before using the new bounds.
Foldout recalculates the SVG bounds around the visible paths, previews the trimmed result, and writes a separately named vector file by default.
The real vector rendering stays visible after trimming, so a smaller viewBox never becomes a blind change to the artwork.
The practical details that make this job faster, clearer, or safer than doing it by hand.
Foldout changes the canvas bounds around the visible artwork instead of tracing or flattening the vector design.
A real rendering of the trimmed SVG makes clipped artwork or unexpected bounds visible before the file reaches a site or app.
The first run creates a -trimmed copy, while overwriting requires a separate, explicit acknowledgement.
Add the SVG.
Review the artwork and keep-originals policy.
Trim the canvas to visible bounds.
Inspect and reveal the separately named vector result.
No. It keeps the output as SVG.