UX Patterns Guide
Back to compare picker

Destructive action confirmation vs Confirmation dialog vs Undo vs Warning text

Choose destructive action confirmation when the user has invoked Delete, Remove, Cancel subscription, Deactivate account, Reset keys, or a similar destructive command and the UI must stop final commitment until the object, scope, and loss are reviewed.

Destructive action confirmation live exampleConfirmation dialog live exampleUndo live exampleWarning text live example

Decision dimensions

Dimension Destructive action confirmationConfirmation dialogUndoWarning text
UI or UX UI + UX - Final destructive commit reviewUI + UX - Consequential alert decisionUX - Post-action recovery behaviorUI + UX - Severe-consequence warning copy before an action
UI guidance Render a destructive confirmation after the user invokes a destructive command, with a title and final action button that repeat the destructive verb and target, such as Delete workspace or Cancel subscription.Render an alert-style modal decision with a specific title, consequence description, safe cancellation, and a destructive action label that names the object or scope.Show a named recovery affordance after the completed action, such as Undo delete for a specific task, near the result or in a consistent status region.Render warning text as a short high-emphasis statement with a warning icon, visible or hidden warning label, and explicit consequence copy placed before the relevant action, declaration, or instruction.
UX guidance Use destructive action confirmation to create one informed stop before permanent or externally visible loss, not to slow every routine cleanup action.Interrupt users only when the action has a meaningful consequence that cannot be safely recovered afterward.Let users move quickly through frequent reversible actions, then recover from mistakes after seeing the result.Use warning text when users must understand a serious consequence before acting or failing to act, such as a fine, loss of access, permanent deletion, eligibility impact, or legal responsibility.
Good UI Delete Payments project? lists 4 dashboards, 12 saved views, 3 webhooks, and 8 shared links, offers Keep project, and labels the danger action Delete Payments project.Delete Research archive? explains that 14 notes and shared links will be permanently removed, offers Keep archive, and labels the danger action Delete archive.Deleting Quarterly report removes it from the list and shows a recovery panel saying Quarterly report deleted with an Undo task button.Before Submit declaration, a warning with an exclamation icon says the user may be fined if they provide false information.
Bad UI A modal says Are you sure? with OK and Cancel after the user clicks Delete, without naming the project or what disappears.A popup says Are you sure? with OK and Cancel but does not name the project, notes, or irreversible outcome.A tiny x removes an item with no object-specific recovery label.A red sentence says Important below the submit button after the user has already acted.
Good UX A user opens Delete workspace, reviews the object count and webhooks, cancels, and returns to the same workspace with nothing changed.Cancel, Escape, and Keep archive leave the archive unchanged and return focus to Delete archive.Undo restores the deleted task to the list and reports Quarterly report restored.Users see the fine or eligibility consequence before checking the declaration and can pause to verify their answer.
Bad UX A user confirms deletion because OK looks like the primary next step, then discovers shared links and child reports were lost.Every archive, filter, and dismiss action opens the same confirmation until users click through automatically.A second delete overwrites the first recoverable item without explaining which action Undo affects.A benefit-loss warning appears only after submission, so users cannot change the decision it warns about.
Best fit A user has initiated a destructive command that can permanently remove, revoke, reset, deactivate, or cancel something valuable.The action is destructive, irreversible, costly, security-sensitive, privacy-affecting, or externally visible.The action is common and mistakes are likely.A user must understand a serious consequence before taking or skipping an action.
Avoid when The action is a routine reversible archive, hide, dismiss, move, reorder, or trash move.The action is routine and easily reversible.The action has external side effects that cannot be recalled.The message is a dynamic task status that must be announced when it appears.
Required state Idle state where the destructive command is visible but not committed.Pre-action state with an explicit consequential trigger.Normal state before the user action.No-warning state where the action has no severe consequence.
Accessibility burden Use alertdialog semantics or platform equivalent when the destructive decision requires an immediate response.Use alertdialog semantics or platform equivalent when the decision is urgent and requires a response.Make the undo control keyboard reachable and programmatically identifiable.Do not rely on color alone; include visible or programmatic warning wording and a non-color cue such as an icon.
Common misuse Using a vague Are you sure prompt that does not name the object, count, or consequence.Asking users to confirm every routine action until they stop reading.Offering undo for an action that cannot actually be reversed.Using warning text for routine hints, explanations, or mild reminders.

Destructive action confirmation

UI or UX
UI + UX - Final destructive commit review
UI guidance
Render a destructive confirmation after the user invokes a destructive command, with a title and final action button that repeat the destructive verb and target, such as Delete workspace or Cancel subscription.
UX guidance
Use destructive action confirmation to create one informed stop before permanent or externally visible loss, not to slow every routine cleanup action.
Good UI
Delete Payments project? lists 4 dashboards, 12 saved views, 3 webhooks, and 8 shared links, offers Keep project, and labels the danger action Delete Payments project.
Bad UI
A modal says Are you sure? with OK and Cancel after the user clicks Delete, without naming the project or what disappears.
Good UX
A user opens Delete workspace, reviews the object count and webhooks, cancels, and returns to the same workspace with nothing changed.
Bad UX
A user confirms deletion because OK looks like the primary next step, then discovers shared links and child reports were lost.
Best fit
A user has initiated a destructive command that can permanently remove, revoke, reset, deactivate, or cancel something valuable.
Avoid when
The action is a routine reversible archive, hide, dismiss, move, reorder, or trash move.
Required state
Idle state where the destructive command is visible but not committed.
Accessibility burden
Use alertdialog semantics or platform equivalent when the destructive decision requires an immediate response.
Common misuse
Using a vague Are you sure prompt that does not name the object, count, or consequence.

Confirmation dialog

UI or UX
UI + UX - Consequential alert decision
UI guidance
Render an alert-style modal decision with a specific title, consequence description, safe cancellation, and a destructive action label that names the object or scope.
UX guidance
Interrupt users only when the action has a meaningful consequence that cannot be safely recovered afterward.
Good UI
Delete Research archive? explains that 14 notes and shared links will be permanently removed, offers Keep archive, and labels the danger action Delete archive.
Bad UI
A popup says Are you sure? with OK and Cancel but does not name the project, notes, or irreversible outcome.
Good UX
Cancel, Escape, and Keep archive leave the archive unchanged and return focus to Delete archive.
Bad UX
Every archive, filter, and dismiss action opens the same confirmation until users click through automatically.
Best fit
The action is destructive, irreversible, costly, security-sensitive, privacy-affecting, or externally visible.
Avoid when
The action is routine and easily reversible.
Required state
Pre-action state with an explicit consequential trigger.
Accessibility burden
Use alertdialog semantics or platform equivalent when the decision is urgent and requires a response.
Common misuse
Asking users to confirm every routine action until they stop reading.

Undo

UI or UX
UX - Post-action recovery behavior
UI guidance
Show a named recovery affordance after the completed action, such as Undo delete for a specific task, near the result or in a consistent status region.
UX guidance
Let users move quickly through frequent reversible actions, then recover from mistakes after seeing the result.
Good UI
Deleting Quarterly report removes it from the list and shows a recovery panel saying Quarterly report deleted with an Undo task button.
Bad UI
A tiny x removes an item with no object-specific recovery label.
Good UX
Undo restores the deleted task to the list and reports Quarterly report restored.
Bad UX
A second delete overwrites the first recoverable item without explaining which action Undo affects.
Best fit
The action is common and mistakes are likely.
Avoid when
The action has external side effects that cannot be recalled.
Required state
Normal state before the user action.
Accessibility burden
Make the undo control keyboard reachable and programmatically identifiable.
Common misuse
Offering undo for an action that cannot actually be reversed.

Warning text

UI or UX
UI + UX - Severe-consequence warning copy before an action
UI guidance
Render warning text as a short high-emphasis statement with a warning icon, visible or hidden warning label, and explicit consequence copy placed before the relevant action, declaration, or instruction.
UX guidance
Use warning text when users must understand a serious consequence before acting or failing to act, such as a fine, loss of access, permanent deletion, eligibility impact, or legal responsibility.
Good UI
Before Submit declaration, a warning with an exclamation icon says the user may be fined if they provide false information.
Bad UI
A red sentence says Important below the submit button after the user has already acted.
Good UX
Users see the fine or eligibility consequence before checking the declaration and can pause to verify their answer.
Bad UX
A benefit-loss warning appears only after submission, so users cannot change the decision it warns about.
Best fit
A user must understand a serious consequence before taking or skipping an action.
Avoid when
The message is a dynamic task status that must be announced when it appears.
Required state
No-warning state where the action has no severe consequence.
Accessibility burden
Do not rely on color alone; include visible or programmatic warning wording and a non-color cue such as an icon.
Common misuse
Using warning text for routine hints, explanations, or mild reminders.
Decision rules
  • Choose destructive action confirmation when the user has invoked Delete, Remove, Cancel subscription, Deactivate account, Reset keys, or a similar destructive command and the UI must stop final commitment until the object, scope, and loss are reviewed.
  • Choose confirmation dialog when the high-consequence decision is not primarily destructive, such as sending an irreversible invitation, changing a permission, making a purchase, or exposing private data.
  • Choose undo when the action can complete immediately and the exact prior object, membership, order, permissions, and visible counts can be restored before external effects occur.
  • Choose warning text when the user has not started the destructive command yet and only needs a concise severe-consequence warning near a button, declaration, or instruction.
  • A destructive action confirmation must name the destructive verb and target in the title and final button, such as Delete project or Cancel subscription, rather than using OK, Yes, Continue, or Confirm.
  • Use a loss inventory when deletion affects child records, shared links, members, automations, billing, integrations, audit logs, or external recipients.
  • Do not use destructive action confirmation for soft delete to trash when restore is prominent enough; use undo or restore-from-trash behavior instead.
  • Escalate from ordinary destructive confirmation to typed confirmation only for severe broad scope, production data, account closure, workspace deletion, or security-critical destruction.
Inspect live examples
Destructive action confirmationConfirmation dialogUndoWarning text
Failure modes
  • A delete command opens a vague Are you sure prompt with OK, so users cannot tell which object or data will be lost.
  • A destructive confirmation appears for every archive or dismiss action, making users click through automatically when a real deletion appears.
  • A reversible trash move is blocked by a severe modal instead of offering restore, slowing routine cleanup without adding safety.
  • Warning copy sits beside the Delete button but no final commit review appears before permanent deletion.
  • The dialog lists a count but omits child objects, shared links, automations, or billing effects that would have changed the user's decision.
  • The destructive button is enabled before required acknowledgement or scope review is complete.