SVG optimiser
Smaller.
And checked.
Drop an SVG and get a smaller one. Then look at the second panel, which is the part other optimisers leave out: this page draws both versions in your browser and counts the pixels that moved.
Drop an SVG here
SVG, up to 2.0 MB
What happened to the picture
Both versions were drawn by this browser and compared pixel by pixel. Nothing was uploaded to do it.
Nothing has been compared yet. Drop a file and this is where the answer goes.
This compares one rendering at one size. A change that only shows at a different size would not appear here.
The file is read, optimised and drawn in this tab. Nothing is sent anywhere.
Once the file is smaller
An SVG is the best thing to hand a favicon generator, because one vector file becomes every size a browser asks for. If this was your logo, the icon set is the next step.
Turn it into a favicon setQuestions
How do I know the picture did not change?
Because both versions are drawn by your own browser and compared pixel by pixel. The panel never says “unchanged” — it says how many pixels it compared and at what size, because that is the claim it can stand behind.
Why does it say it does not know?
An SVG that references something outside itself cannot be checked this way. Both renders draw the same absence, so they would match for the wrong reason — and a match that proves nothing is worse than no match. The page says it does not know instead.
Why does it stop at 2 MB?
Because the cost is superlinear and it was measured rather than guessed: 100 kB optimises in 91 ms, 2 MB in 5.8 seconds, and 6.1 MB in 46. Two megabytes is the last size that still finishes in seconds. Those readings are from a desktop, so this is not a promise about how long 2 MB takes on a phone.