Sync Repeated Inkscape Elements with Linked Clones

One button, five artboards, and a change you forgot to make

You draw a rounded-corner button, copy it across three screens, and finalize the layout. Then the product team asks for a slightly larger corner radius. Without linked clones, you select each button, adjust the nodes, and hope you did not miss one. Manual synchronization is where drift starts: one instance keeps the old radius, another gets a different fill, and your icon set stops looking like a set.

The useful takeaway is simple: Inkscape linked clones let you edit one source object and have every instance update automatically, while each clone keeps its own position, scale, and rotation. This overview assumes Inkscape 1.x; because attribute-override behavior can vary by release, check your version if a clone does not respond as described.

What a linked clone does

A clone is not a duplicate. When you choose Object > Clone > Create Clone, Inkscape creates an instance that references the original object’s geometry, fill, and stroke. Editing the original’s path with the Node tool propagates to all clones. Moving, scaling, or rotating a clone affects only that clone; it does not change the original or the other instances.

Under the hood, Inkscape stores this relationship using SVG use elements that point to the original object’s ID. You can confirm this in the XML editor, which I cover below.

Worked example: keep a button component consistent

1. Draw a rounded rectangle on the first artboard. This is your source object.
2. Select it and choose Object > Clone > Create Clone. A clone is created from the selection.
3. Drag the clone to another artboard. You can scale or rotate it without affecting the source.
4. Repeat until every screen has an instance.
5. Select the original rectangle and edit its path with the Node tool—for example, increase the corner radius. The change propagates to all clones.

If one screen needs a one-off variation, select that clone and choose Object > Clone > Unlink Clone. This breaks the reference so you can edit that instance independently. Because unlinking changes the document state, use Edit > Undo if you want to restore the link immediately afterward.

Duplicate versus linked clone

Action	Plain duplicate	Linked clone
Edit source shape	Each copy must be edited manually	All instances update automatically
Move or scale one instance	Affects only that copy	Affects only that clone
File impact	Stores full path geometry per copy	References the source object

Limits and what to verify

• Transforms do not propagate. Resizing a clone does not resize the original or its siblings.
• Style overrides can diverge. Changing fill or stroke on a clone may separate that attribute from the source, and exact behavior varies by Inkscape release.
• Nested clones add complexity. Cloning a clone makes selection and z-order harder to manage in dense documents.
• Export rendering is not guaranteed everywhere. If clones interact with masks, filters, or clipped paths, check the exported SVG or PNG in the target consumer before assuming it matches the canvas.

Check the link in the XML editor

Open the XML editor and locate your clone. It should appear as an SVG use element referencing the original object’s id. If you unlink a clone, that reference disappears and the element becomes standalone geometry. This is the most reliable way to confirm a clone is actually linked rather than merely looking similar.

Use one source of truth for repeated elements

Linked clones are best suited for UI components, pattern tiles, and icon sets where the same shape appears in multiple places. They will not save you from manual work when every instance needs a different shape, and they are not a substitute for careful export testing when filters or masks are involved. For repeated vector elements, though, they turn a multi-object editing problem into a single-object edit.