# Reusing a design: layouts vs components

URL: https://kywi-docs-production.up.railway.app/authoring/reusing-a-design-layouts-vs-components
Type: docPage

Placing a saved layout copies its sections once; placing a saved component keeps it live-linked, so editing the component updates every page that uses it.

Saving a design for reuse means one of two different things, and the picker you insert it from tells you which: a saved **layout** is a one-time copy, and a saved **component** stays linked to where it came from. Both start the same way — select a section, save it under a name — so the distinction is in what happens next, not in how you make one.

## A layout is a blueprint

Placing a saved layout drops its sections into the page as ordinary, independent sections. From that moment they have nothing to do with the layout you placed them from — editing the saved layout later never reaches back into a page that already used it, and editing the page never touches the layout. Think of it as a starting point you copy, not a thing you keep pointing at.

## A component stays live

Placing a saved component is different: the section on your page keeps a link to the component it came from, and what renders there is whichever definition the component currently has — on every page that placed it, published pages included. Edit the component once and every placement shows the edit on its next request, with nothing to republish. The insert picker marks this explicitly, tagging components and containers **Linked · stays in sync with the source**; a saved layout carries no such tag.

## A component nested inside a layout stays linked

Save a section that contains a component, and place it as a layout: the outer section copies the way any layout does, but the component nested inside it doesn’t — it’s still the same live link. Editing or deleting that component later reaches every page you’ve since stamped from the layout, even though the layout itself never changes. If a saved layout contains a component, treat every page it’s placed on as a holder of that component, not as an independent copy.

## What a layout drops

Only ordinary sections come along when a layout is applied. If the section you saved included a personalized or split-tested container — its own A/B or audience variants — those variants aren’t part of the copy: the layout applies as if the container had never branched.

For what happens when you edit a linked component after placing it, see [Living with linked components](/authoring/living-with-linked-components/). For saving a component from inside the front-of-site editor rather than the admin layout editor, see [Saving a section as a reusable component](/editing/saving-a-section-as-a-reusable-component/).
