Antoine Beyeler vpype (Free)

Every generative art tool — p5.js, Processing, Inkscape, any of them — produces SVGs that are efficient for the screen but wasteful for a plotter. Paths are ordered by when they were drawn, not by where they are on the page. A plotter following that order lifts the pen hundreds of times to cross the bed for a nearby stroke. vpype fixes that.

What it actually does

At its core, vpype does two things: line merging (connects paths that share an endpoint into one continuous stroke, eliminating pen lifts) and stroke reordering (sorts the remaining strokes using a nearest-neighbor algorithm so the pen travels the shortest possible path between them).

On a complex generative plot, these two steps alone can cut plot time in half and reduce pen wear substantially.

The pipeline model

vpype works as a command pipeline. Each command reads the current state, transforms it, and passes it on:

vpype read art.svg \
  linemerge --tolerance 0.5mm \
  reorder \
  crop 0 0 297mm 420mm \
  write optimized.svg

You build up complex processing steps from simple, composable commands. The community has published plugins for everything from Gaussian noise to hatching fills to text rendering using Hershey fonts — all chainable in the same pipeline.

Why it’s the missing step

Most plotter tutorials cover generative art tools and plotter software but skip the middle. vpype is that middle: the translation layer between “SVG that looks right on screen” and “SVG that plots efficiently and cleanly.” Once you run a complex plot before and after vpype optimization, you won’t skip it again.

Install with pip install vpype[all] and start with vpype --help. The official documentation is thorough.