Reduce traced SVG nodes without losing the details you need
A shorter path is easier to edit only if it still represents the shape you need.
Save a copy, select the path and use Path → Simplify once. Compare the result with the original at the smallest important feature; undo if it rounds a corner, narrows a bridge or changes a hole. Repeated Simplify can reshape the drawing. The lowest node count is not the goal.
Decide what must survive
List the smallest hole, the thinnest connection, a sharp corner and the intended outside size. A logo may tolerate small contour changes that a fitted part cannot. Choose your acceptance limits for the actual use rather than treating one smoothing setting as universal.
Extra nodes can come from pixel steps, noisy JPG edges or an over-detailed trace. Improve a poor raster before tracing again. Simplifying an existing path cannot recover detail the source image never contained.
Simplify in Inkscape, then inspect
Keep an unchanged original
Save a separate SVG copy. Work on the copy, with the original open for comparison. The sample files below already separate the original and two modified outputs.
Select the vector path
Use the Node tool to confirm you have editable path nodes rather than an embedded bitmap. Select only the paths you intend to simplify; avoid unrelated large objects that can change the selection and simplification behavior.
Apply Path → Simplify once
Use the menu command once, then pause to inspect. The official tutorial describes stronger simplification when repeated rapidly. Our three-action sample runs consecutive native commands; it is not a recommended preset for your file.
Compare the critical features
Look at each hole and thin bridge with the Node tool and at the intended output size. Inspect corners and disconnected pieces. A path that is still closed can nevertheless have a very different contour.
Undo unwanted changes
If the result loses a needed feature, undo and keep the original or edit a smaller part manually. Repeatedly pressing Simplify to reach a target count can make the damage worse.
Measure and reopen the saved SVG
Measure the outline rather than the page. Save and reopen the SVG to inspect the result again. If you later export DXF, repeat the receiving-program checks; an SVG edit does not establish DXF or fabrication compatibility.
A real example: 2548 → 210 → 31 nodes
On 9 October 2026 we ran Inkscape 1.4.4’s native Simplify command on copies of the same traced Bootstrap gear, using an isolated profile with no simplification preference override. One run used one action; another used three consecutive actions in one process. The PNGs below are native renders of the downloadable SVGs.
The count here is expanded SVG move/segment endpoints, excluding Z closure commands and control points; it may differ from another editor’s displayed node count. All three files retain four explicitly closed subpaths. That does not prove preserved topology, narrow-feature width or absence of self-intersection. The three-action render visibly changes the shape even though the closure count is unchanged.
| Simplify actions | Nodes | Outline width × height |
|---|---|---|
| Original | 2548 | 100.000 × 100.000 mm |
| Once | 210 | 100.029 × 100.041 mm |
| Three consecutive actions | 31 | 99.889 × 100.052 mm |
If you are tracing a PNG in TraceDXF
Trace details → Reduce nodes can replace short pixel steps with straight segments. Compare the preview before and after, including holes and disconnected pieces. It is a different operation from Inkscape Simplify and does not fit smooth curves. The numerical comparison above describes Inkscape, not a TraceDXF setting.
TraceDXF starts from PNG/JPG and cannot import an existing SVG for this operation. Keep using Inkscape for editing an SVG you already have.
Sources and recorded scope
The command behavior follows Inkscape’s official tutorial; the gear metrics come from this project’s 1.4.4 native CLI run. Original art is Bootstrap Icons under MIT. No LightBurn, Cricut or fabrication test was performed on these simplified files.