SVG file size AI vs Affinity Designer

[topro]

Hi there, I'm thinking of switching from AI to Affinity Designer and am currently testing AD. I need AI primarily to customise logos for websites. Now I have the problem that the SVGs saved from Affinity always have at least twice the file size as the ones from AI (same logo, same size, procedure etc). I can't see any difference in quality. Is there perhaps a trick?
Thanks for any help!
Tobias

form Affinity.svg from Adobe.svg

[Komatös]

Hi @topro

As you can see, Adobe does away with all formatting and clarity.

[v_kyr]

Just use a SVG compressor/minifier to compact the Affinity SVG file output further ...

• https://compress-or-die.com/svg
• https://www.svgminify.com/en.html
• https://vecta.io/nano
• svgo
• SVGOMG
• https://image-shrinker.com/
• https://github.com/sonnyp/OhMySVG
• ... and so on ...

[topro]

15 minutes ago, Komatös said:

Hi @topro

As you can see, Adobe does away with all formatting and clarity.

 

20 minutes ago, v_kyr said:

Just use a SVG compressor/minifier to compact the Affinity SVG file output further ...

• https://compress-or-die.com/svg
• https://www.svgminify.com/en.html
• https://vecta.io/nano
• svgo
• SVGOMG
• https://image-shrinker.com/
• https://github.com/sonnyp/OhMySVG
• ... and so on ...

Thanks for that, but what I get from Adobe is already much smaller without further processing. And if I put the Adobe SVG into the compressor, it gets even smaller.

[Komatös]

@topro

Look at both files in a text editor that, if possible, shows a direct display of the differences.

[topro]

• SVGOMG

I did not know this optimiser yet. Here you can still make settings and see the result simultaneously, into which you can also zoom. I was able to save up to 75% file size without visible degradation. Excellent tip! I should be able to manage with that.

Many thanks to both of you. 

[v_kyr]

52 minutes ago, topro said:

... but what I get from Adobe is already much smaller without further processing. And if I put the Adobe SVG into the compressor, it gets even smaller.

Well, even Adobe's SVG generator outputs more compact SVG code, it's not that much manual readable inside a text editor and thus then as easy to edit & customize as the SVG output from the Affinity SVG code generator. Meaning here, that in order to make the Adobe SVG code output more manual readable/editable at all I would need to throw it's code through an "SVG Code Pretty Printer". In contrast the by Affinity generated SVG code is pretty good readable and editable in any text editor (I usually tend to use "Sublime Text" with some add-ons for such purposes).

However, if you throw the by Affinity generated SVG code through some SVG Obfuscator/-Compressor/-Minifier you will get much more compact und smaller/lower sized SVG file sizes (which in turn are just plain XML based texts). - The same applies of course also to Adobe's SVG output code, which can be even further compacted/minified by certain above listed SVG tools then!

[v_kyr]

7 minutes ago, LondonSquirrel said:

So it's fair to say that the SVG output from AD could be optimised.

The overall point that counts IMO more here is, at least for SVG code hackers like me, to get better manual readable, formated & editable SVG output code, which one then can manually more easily alter & adapt to specific own needs etc. vs. getting unreadable, partly obfuscated SVG code! - SVG code optimization, in terms of smaller file sizes (for faster website loadings) if needed, can be performed with/by a bunch of third-party SVG tools (...as I've referenced partly above in this thread).

So overall I don't see any needs to optimize/compact and obfuscate the by Affinity generated SVG output code that much further by Affinity's own SVG generators yet!

[lacerto]

Obsolete.

[v_kyr]

6 hours ago, LondonSquirrel said:

I would not count using styles as obfuscation. It's just shorthand.

Another term often used for "shortening code" (aka making text more compact by throwing out all newlines and other readability formating characters etc.) beside minifying/compacting/shortining is obfuscation, since an Obfuscator does operation wise -beside making the code overall more unreadable- pretty much the same here for text based code.

[lacerto]

Obsolete.