VECTOFOX FIELD NOTES
Too many SVG nodes? Simplify a trace without losing detail
A large path count and a large node count are different problems. Fewer paths can make a trace easier to work with, but a low count is not proof that the important contours survived. Compare the geometry, the file and the artwork together.
VectoFox documentation · Updated
Count paths and endpoints separately
One path can contain a long curve or many disconnected subpaths. A file with ten paths can still contain many editable points. Conversely, a large number of small, simple paths can be difficult to select and recolor even when each one has only a few points.
The published table counts visible path elements separately from an estimated count of their segment endpoints. That estimate excludes control handles, close commands and clip definitions. It is not a promise to match the node total shown by every editor; the complete measurement method is provided with the JSON.
Compare settings on the same source
The fox is a flat illustration, the JPEG fixture has deliberate compression artifacts, and the continuous-tone texture has many local color changes. Each input was traced with three published presets. The comparison changes both palette and detail; it is a practical preset comparison, not an experiment that isolates the effect of a single slider.
Compact uses a four-color limit and detail 1, balanced uses eight colors and detail 3, and detailed uses twelve colors and detail 5. Download the actual SVGs before deciding that one preset is better. A smaller file may have removed a useful edge or a soft effect.


| Sample | Preset | Input bytes | SVG bytes | Visible paths | Est. endpoints | Median ms | RGB error |
|---|---|---|---|---|---|---|---|
| Flat fox illustration | compact | 46,979 | 15,346 | 31 | 535 | 119.7 | 5.59 |
| Flat fox illustration | balanced | 46,979 | 19,211 | 40 | 654 | 90 | 4.2 |
| Flat fox illustration | detailed | 46,979 | 27,930 | 54 | 944 | 99.6 | 4.1 |
| Low-quality JPEG edges | compact | 1,981 | 3,220 | 13 | 138 | 29.7 | 3.61 |
| Low-quality JPEG edges | balanced | 1,981 | 10,721 | 40 | 481 | 41.4 | 2.47 |
| Low-quality JPEG edges | detailed | 1,981 | 19,366 | 82 | 843 | 50.9 | 2.25 |
| Continuous-tone texture (synthetic) | compact | 18,122 | 154,096 | 106 | 7,545 | 136.9 | 18.25 |
| Continuous-tone texture (synthetic) | balanced | 18,122 | 494,492 | 1,339 | 23,504 | 192.9 | 12.97 |
| Continuous-tone texture (synthetic) | detailed | 18,122 | 828,775 | 2,826 | 38,799 | 250.9 | 11.6 |
Estimated endpoints count path-segment endpoints, not curve handles, and exclude close commands and clip definitions. RGB error is the average channel difference on white (0–255), not a perceptual ranking. Lower counts and smaller files can hide lost features.
Fix noise before asking for more detail
Repeated JPEG compression can create small color variations around an otherwise simple logo. A larger palette can keep these variations as separate regions. Reducing colors or returning to the original PNG can be more useful than trying to simplify thousands of already-generated paths.
Use path detail to keep necessary corners, not to maximize a score. Start with a compact palette, compare small letters and gaps, then increase detail when a specific feature disappears. If the edge is wavy because the source is noisy, clean that source first. Adding detail can faithfully preserve the noise.
Simplify only the parts that need it
In a vector editor, work on a copy and select the troublesome path rather than simplifying the entire document immediately. Inkscape provides a Path > Simplify operation. Use a small change, inspect the curve and undo it if an opening closes or a corner moves. Repeated simplification can alter the design, even while reducing points.
Do not assume every small shape is a speckle. A tiny opening inside a letter or a narrow joining stroke may be part of the mark. Do not count removal as an improvement until you have checked the result at the intended display or production size.
Use a visual acceptance checklist
Check sharp corners, letter counters, separated islands and thin joining lines. Zoom out again to the intended use size. A minor geometric difference can be irrelevant for a small icon, while a closed letter counter can change a logo at any scale.
For machine workflows, also inspect duplicate paths, overlaps and the expected units in the downstream software. Neither a low endpoint estimate nor a small file certifies a cut-ready result. Keep a clean editable master and make a separate production copy when needed.
- Compare the same source and use case, not unrelated images.
- Record both path count and file bytes.
- Inspect corners, holes and thin strokes after every change.
- Keep the smallest result that still preserves the required artwork.