---
title: "Loss Aversion"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Loss-aversion"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Loss-aversion"
source_slug: "Loss-aversion"
track: "Persuasive Design Patterns"
group: "Cognition"
subgroup: "Loss Aversion"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Thaler’s 4 principles"
  - "How to apply loss aversion to your product"
  - "Rationale"
  - "Example: Discounts and trial periods"
  - "Discussion"
  - "Example: Lazy registration"
  - "Background"
example_count: 2
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Loss Aversion

> Catalog pointer for the UI Patterns source page: [Loss Aversion](https://ui-patterns.com/patterns/Loss-aversion).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Cognition
- Subgroup: Loss Aversion
- Source breadcrumb: Design Patterns > Cognition > Loss Aversion > Loss Aversion

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Loss-aversion
- Page title: Loss Aversion design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Thaler’s 4 principles, How to apply loss aversion to your product, Rationale, Example: Discounts and trial periods, Discussion, Example: Lazy registration, Background
- Example screenshots detected at source: 2
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 16 words on source page
- Example: 72 words on source page
- Usage: 33 words on source page
- Solution: 586 words on source page
- Thaler’s 4 principles: 282 words on source page
- How to apply loss aversion to your product: 177 words on source page
- Rationale: 360 words on source page
- Example: Discounts and trial periods: 122 words on source page
- Discussion: 347 words on source page
- Example: Lazy registration: 117 words on source page
- Background: 68 words on source page

## Source Navigation

- Previous source navigation: Storytelling
- Next source navigation: Peak-end rule