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.
1 · The SVG
load2 · The result
measuredWhat came off
countedCounts 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 textThe SVG is percent-encoded, so #, < and " survive inside the url. Quotes, parentheses and apostrophes are escaped too, which keeps the rule valid in a style attribute.
Each size is drawn on a transparent square canvas, the artwork scaled to fit and centred — no white backdrop, no crop. 1024 is set as the largest because past that the file grows faster than the detail most icons carry.
What comes off, and why
the same bytes a bundler weighsEditor 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.