# Saving a section as a reusable component

URL: https://kywi-docs-production.up.railway.app/editing/saving-a-section-as-a-reusable-component
Type: docPage

Editing a section that’s already a shared component forces a choice at save — keep the edit on this page, or push it live to every page placing the component.

A section, module, or container can be a *linked instance* of a saved component — the same block placed on several pages, kept in sync on purpose. Edit one and the editor stops your save to ask what you meant: keep the change here, or send it everywhere the component is placed. A section that isn’t shared saves the way anything else does — you’ll only see this if what you touched is linked.

## The two answers

**Save to this page only** detaches this instance into an ordinary, un-linked copy — your edit sticks here, and this section stops following the shared component from now on. **Save and update all instances** writes the change into the component itself, so every page that places it changes too.

## What “everywhere” means

## Updating everywhere is immediate, published pages included

“Save and update all instances” changes every page placing the component the moment you confirm it — a page that’s already live and public updates on its next request. There’s nothing to re-publish on those other pages; the change is already showing.

## Save Draft and Schedule don’t change this

## A component write is never drafted or scheduled

If the page you’re editing has its own Save Draft or Schedule button, the fork tells you plainly that it doesn’t apply here: choosing “update all instances” pushes the component live regardless of which button opened the dialog. There’s no drafted or scheduled form of a component edit — only saved, or not.

## If it fails partway

When you choose to update everywhere, the component itself is written first and the page you’re on second. If the page save then fails, the component change has already landed — the failure message says so rather than leaving you to guess, and saving again simply repeats the same write.

## Inside a personalized or split-tested section

A module living inside one variant of a personalized or A/B-tested section can’t be turned into a component (or deleted) from here. Letting it happen would mean an edit to a single variant leaking out through the shared component into every other page that places it — exactly what keeping variants separate is for.
