# Inline Editing

Inline editing lets users switch content from a read state to an editable control in place, preserving the surrounding context.

- Type: practice
- Domain: Experience & interface
- Level: Intermediate
- Last reviewed: 2026-10-06
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/inline-editing/>)

## What it means

Inline editing changes a displayed value or object into an input at the same location rather than opening a separate form or page. The pattern defines how editing begins, how values are saved or canceled, how validation appears, and how the interface returns to its read state.

## Why it matters

Editing in context reduces navigation and helps users connect a change to its result. Without clear affordances and save behavior, however, people may not discover editability or may lose changes unintentionally.

## When to use it

Use inline editing for short, independent values that users occasionally adjust while reviewing a page or table. Use a dedicated form for complex dependencies, extensive guidance, many simultaneous fields, or tasks where review before submission is important.

## How it works

1. Choose fields that can be edited independently without hiding important context or dependencies.
2. Provide a visible, labeled edit affordance and preserve alignment when read content becomes an input.
3. Define explicit or automatic save, cancel, validation, loading, and conflict behavior.
4. Keep focus on a logical control during the transition and announce success or error without losing the value.
5. Test empty values, long text, keyboard-only use, concurrent updates, latency, and repeated edits.

## A practical example

A team settings page shows the team name with an Edit button. Activating it replaces the name with a focused text field plus Save and Cancel; a duplicate-name error stays beside the field, while a successful save returns to read view and announces the update.

## Where it breaks

Hidden edit affordances reduce discoverability, frequent transitions can feel unstable, and auto-save makes cancellation and error recovery harder. Independent inline fields can also conceal relationships that a structured form would make explicit.

## Common mistakes

- Making text editable only through an undiscoverable hover state or double-click.
- Saving on blur without explaining what happened or preserving invalid input.
- Moving the field or page layout substantially when edit mode starts.
- Using many inline editors where the main task is clearly form-based editing.

## Sources

1. [Inline editable text field](<https://atlassian.design/components/inline-edit/inline-editable-textfield/usage>) — Atlassian Design System · Institutional design system
2. [Forms](<https://www.carbondesignsystem.com/building-blocks/core/patterns/forms>) — Carbon Design System · Institutional design system

## Related topics

- [Form Validation](<https://wiki.soroush.uk/topic/form-validation/>)
- [Optimistic UI](<https://wiki.soroush.uk/topic/optimistic-ui/>)
- [Interaction State](<https://wiki.soroush.uk/topic/interaction-state/>)
