SvgForge · optimize · JSX · data URI · PNG · zero upload

Smaller SVG.
Same picture.
Then out as JSX, CSS or PNG.

Drop an editor export and watch the bytes come off: comments, metadata, editor namespaces, empty groups and long decimals are removed with the browser's own parser. The original and the optimized file are weighed side by side, then the result leaves as SVG, a React component, a CSS data URI or five PNG sizes.

0 bytes uploaded 0 external requests precision 1–4 places 64 · 128 · 256 · 512 · 1024 PNG

1 · The SVG

load
Drop an .svg here or click to choose a file — it never leaves this tab
—
decimal precisionApplies to path data, points, transforms and geometry

2 · The result

measured
—original bytes
—optimized bytes
—saved
—nodes removed
Optimized SVG preview
—

What came off

counted
XML comments0
metadata blocks0
<title> · <desc>0
editor nodes · attributes0
empty groups0
numbers rounded0

Counts are of what this run actually removed — a switch that is off shows zero, and the preview beside it is the file that remains.

3 · One click out

from the optimized text
Attributes are camel-cased (stroke-width → strokeWidth), class → className, style becomes an object, and the root takes {...props}.

What comes off, and why

the same bytes a bundler weighs

Editor state, not artwork

An Inkscape or Sketch file carries layer names, guides, page colours and app state in its own namespace. A browser skips all of it. Removing those elements and their xmlns declarations is the biggest single win on an exported logo — and the picture does not change.

Decimals cost more than they show

Six decimals is 8 characters per number on a canvas that resolves to a pixel grid. Two places is under a thousandth of a pixel at icon size. The slider goes to one for files that must be small and to four when a path is fine enough that rounding would show.

Measured, not estimated

Both texts are encoded to UTF-8 with TextEncoder and counted byte for byte, then the preview and every export are built from the optimized text itself. If the parser rejects the file, the error is shown and nothing is replaced.

Questions

four honest answers
Does the optimized SVG look the same?
The same elements with the same fills, strokes and paths draw it. What goes is what a renderer ignores: comments, metadata, editor attributes and empty groups. Precision is the one setting that touches geometry, so it starts at two places and the preview is rendered from the result — compare the two before you ship.
Why keep <title> and <desc>?
Screen readers announce a <title> as the graphic's name, and <desc> as its description. They cost a few dozen bytes. The switch is off by default, and turning it on removes both when an icon is decorative and labelled in the surrounding markup.
Can I use the JSX output as it is?
Yes — it is a default-exported component with {...props} on the root, so <SvgForgeIcon className="h-5 w-5" /> works. Attributes are camel-cased, class becomes className, and a style attribute becomes a JSX object. Gradients keep their ids, so give the component a unique id if you render the same file twice on one page.
Where do my files go?
Nowhere. The file is read by the browser, parsed by DOMParser, and every download is a blob built in this tab. No server, no analytics, no storage — the external request counter below stays at zero, and the tab forgets everything when you close it.