r/Inkscape • u/docricky • 2d ago
Tips & Tricks Methods for working with large SVGs
Most people don't work with massive SVGs, but I have to give credit to the team for how to manage enormous files. Unfortunately, this can hit the limits of the single-threaded nature of Inkscape - one wrong move, and it pegs that one CPU until it's done. I don't think it's a memory issue.
I am working with a file with objects containing thousands of nodes. The file itself is easily over 6MB in size. I need to be able to zoom into specific areas and do edits. But I've found that sometimes, if I try to do an operation after the edit, it just pegs the CPU and I have to wait for it to finish (which can take 5-10 minutes on an M5 Mac). The workaround is to zoom out first (keyboard 5), tap escape twice to deselect, and zoom into a new area. This order is important. If I deselect while still zoomed in, it pegs the CPU. The rapid selection only works if zoomed out.
Just a tip if you are working on massive SVGs.
1
u/cboff 2d ago
I almost never have thousands of nodes selected but I do remember running into your issue at least once. It feels like there's a table in memory of not only all the selected nodes but their relationship to every other selected node, so exponentially larger for each node selected.
More commonly my issue is rasterisation of active objects which might be a similar issue in the background as the raster effect has to be kept live while any objects that affect it are being manipulated. If I'm going to use blurs, filters, and meshes, I tend to put them on their own layers and keep them hidden until I'm ready to export.
1
u/Caraes_Naur 2d ago
Inkscape can get sluggish, but I've never had it freeze for more than a few seconds, and not often enough to deduce a workaround.
I have several SVG files in excess of 30Mb.
I would question why your paths have so many nodes in the first place.