A design strategy that presents only the information and options users need for their current task, revealing advanced features or details only when requested. This reduces cognitive load and prevents beginner users from feeling overwhelmed by complexity.
Common contexts
- Hiding advanced export settings behind an 'Options' expander on a file export dialog that most users never need
- Designing a multi-step form that reveals shipping address fields only after the user confirms they want physical delivery
- Building a settings page with a visible 'General' section and a collapsed 'Advanced' section for power users
Use when
Use progressive disclosure when an interface must serve both novice and expert users simultaneously, or when a small percentage of users need options that would clutter or intimidate the majority if always shown.
Avoid when
Avoid hiding options that users frequently need behind extra clicks — when analytics show users consistently expanding a collapsed section, it's a sign that content belongs in the primary layer, not tucked away.
Progressive disclosure is only effective when users know more options exist — a collapsed section with no visible affordance doesn't reduce complexity, it just hides features until users give up and contact support.
Real-world examples
- Gmail's Compose window shows only To, Subject, and body by default; Cc, Bcc, formatting toolbar, and attachments are hidden behind disclosure controls, keeping the default experience uncluttered for simple emails.
- Turbo Tax walks users through one question per screen, progressively revealing tax complexity only when prior answers trigger it — an approach that reduced perceived complexity despite filing the same number of forms.
- Stripe's payment API documentation uses collapsible sections to show advanced parameters only to developers who expand them, keeping the quick-start path short while not hiding options from experts.