Product Adoption

Modal UI design: 19 examples, best practices, and when to use a modal

Katryna Balboni

November 10, 2026

In-App Experience Patterns

Product Tours & Walkthroughs

Checklists, Tooltips & Modals

User Engagement

Product Tours & Walkthroughs

TL;DR

A modal UI is a window that opens on top of an app's main screen and blocks interaction with the page behind it until the user responds. The page behind usually dims. Modals (also called modal windows, modal dialogs, overlays or lightboxes) work best for important decisions and must-know messages—confirming a deletion, welcoming a new user, introducing a major feature, or handling legal, security, or other irreversible actions.

If you’re on a product, product marketing, growth, or lifecycle team—especially at a product-led SaaS company—this guide will help you decide when a modal earns that interruption and when a lighter pattern is the better move. We’ll cover what modals are, modal UI best practices, examples, when to use them and when not to, mobile modal patterns, how AI is changing modal use, and how to measure whether your modals actually improve onboarding, feature adoption, and retention instead of getting in the way.

Key takeaways

  • Modals interrupt on purpose. That makes them right for high-stakes moments (onboarding choices, big announcements, irreversible actions, legal or security steps) and wrong for almost everything else.
  • Lighter patterns usually win. Slideouts, banners, tooltips and inline messages handle routine updates without blocking the page.
  • Good modal UI is small and clear. It has a scannable title, one or two sentences of copy, a CTA that names the outcome, and an obvious way out.
  • Accessibility isn't optional. Move focus into the modal, let Escape close it, return focus when it closes, and label it for screen readers.
  • AI raises the stakes. Modals now introduce AI features, ask whether an AI result was right, and confirm actions an agent is about to take for a user.

Modal UI examples: a gallery of 19 modals

Here are 19 modal windows from web and mobile products, grouped by the job each one does. Four are example designs we built to show newer patterns, like introducing an AI feature or approving an agent's work, that haven't settled into a classic real-world example yet. Use the filters to jump to a use case.

What the best examples have in common:

  • They show up at a moment that makes sense. Skyscanner asks about price alerts right after a search. Duolingo pitches its paid plan to people who already use the app a lot. Neither would work as a first-login popup.
  • They ask for one thing. Calendly announces one feature. InVision asks one question. Each modal has one primary button.
  • They make the stakes clear. InVision's deletion warning and the agent-approval example both say exactly what will happen before the user commits.
  • They're easy to leave. Every example has a visible secondary action or close button.

What is a modal?

A modal is a UI element that sits on top of an application's main window. It usually has a semi-transparent layer behind it, called a scrim, that dims the page underneath.

The name comes from the "mode" it creates. While a modal is open, the main interface is disabled. To get back to it, users have to act inside the modal: complete a task, make a choice, or dismiss it. That's what makes a modal useful, and it's also why it shouldn't be used lightly.

Modals go by several names. Developers often say modal dialog or dialog box. Designers say overlay or lightbox. Marketers often say popup. The terms overlap, but they aren't quite the same.

Modal vs. popup

"Popup" is the broader term. A pop up can describe anything that appears over the main interface, including non-blocking elements like toasts and chat widgets. A modal is the specific kind of popup that blocks the page until the user deals with it. All modals are popups, but not all popups are modals.

Modal vs. non-modal dialog

A modal dialog must be resolved before the user can return to the page. Think of a "Delete this file?" confirmation. A non-modal (modeless) dialog stays open while the user keeps working, like a find-and-replace panel in a text editor while they continue editing the document. Use a modal dialog when you need a definite answer. Use a non-modal dialog when the content is supporting the task rather than gating it.

Modal vs. slideout, banner, and tooltip

A modal is the only one of these patterns that stops the user until they respond. Pick the lightest one that does the job.
Pattern Blocks the page? Best for Example
Modal Yes Decisions, must-know news, irreversible actions “Delete this project?”
Slideout No Announcements and tips that can wait A new-feature card in the corner
Banner No System notices, gentle nudges A maintenance window at the top of the page
Tooltip No Explaining one control where it lives A pointer on a new button
Bottom sheetMobile Sometimes Options and short tasks on small screens A share menu that slides up

When to use modal windows

Use a modal when the message is important enough to stop what the user is doing. Because modals aren't attached to any one element on the page, modal windows work best for broad, important messages or tasks that merit interrupting the user, not for help with one specific control.

1. Onboarding and personalization

A welcome modal is the first impression of your product. The best ones do more than say hello. They ask one question that shapes what comes next.

Zapier welcome to Teams modal window with animated confetti

Zapier welcomes new Teams users with one line of copy, one button and a burst of confetti.

Ask a new user's role on first login and you can give a paralegal and a managing partner different home screens, checklists and tours. This matters most when your users aren't tech-savvy, like the service advisor at a car dealership or the office manager at a contracting firm. They're good at their jobs, and they shouldn't have to be good at your software too.

For longer introductions, a short series of modals with progress dots (like Grammarly's, in the gallery) keeps people moving. Keep it to three or four steps. Beyond that, use a checklist or a product tour instead. See our user onboarding guide for the full playbook.

Grammarly multi-step user onboarding modal flow

Grammarly introduces core features in a short series of modals and repeats the product's value along the way.

2. Feature and product announcements

Big news, like a redesign or a long-awaited feature, earns a modal. Small news doesn't.

Calendly gave one long-awaited feature, automated follow-up emails, a single bright modal with a screenshot of the feature.

Redesigns are a good reason for a modal, because any change to the interface can unsettle people. The best redesign modals make the change feel like an upgrade the user controls.

Gmail announced its redesign by letting users pick one of three layouts, so the change felt like their choice.
Sephora used a short, plain modal to explain that the menu bar had moved.

On mobile, a partial overlay can carry an announcement without taking over the whole screen.

Spotify promotes a new release with a partial-screen overlay that feels lighter than a full takeover.

Deciding what earns a modal is getting harder, because teams ship so much more. In our State of Product Launches 2026 survey of 60 marketers, 75% said their teams ship faster than a year ago, and only 7% said their launch process is keeping up. The most common gap, named by 60%, was educating customers about new features.

When everything ships faster, it's tempting to give every release a modal, but users then learn to close them all without reading. A better rule: give a modal to the one or two launches each quarter that change how people work. Send the rest to a slideout, a banner or a "What's new" panel users can open when they want.

📊 State of Product Launches 2026. See how 60 marketers are handling faster release cycles, where launches break down, and what the teams that keep up do differently. Get the report →

3. Confirmations and irreversible actions

This is the strongest use case for a modal. If an action deletes data, spends money, sends something to customers or can't be undone, a short interruption prevents an expensive mistake.

Make the title restate the action ("Delete 'Q3 roadmap'?") and the button repeat the verb ("Delete"), using clear, specific button text rather than vague labels. Never use "OK."

InVision asks for an explicit yes before deleting a prototype. Here, the interruption is the point.

High-stakes steps also deserve a clear "it worked" afterward.

Acorns confirms a linked bank account with a full-screen success modal.

4. Approving work an AI agent did

This is a newer kind of confirmation. As products add assistants that act for users, like drafting invoices, updating records or messaging customers, people need a checkpoint before the work goes live. A good approval modal shows:

  • What the agent is about to do, in plain words
  • What's at stake (how many records, how much money, who gets notified)
  • Anything that needs a human look first, with a way to review it

See the "Approving an agent action" example in the gallery.

5. Security, legal and compliance steps

Accepting updated terms, confirming a password change, or completing a step-up verification are moments where blocking behavior is the point. The user has to act before continuing.

6. Short, self-contained tasks

Modals work for quick forms that don't deserve their own page, like renaming a file, inviting a teammate or setting working hours (see Google Calendar in the gallery). If the task needs scrolling, multiple sections, or more than three or four steps, give it a page.

Google Calendar confirms working hours in a modal with a clear title, a branded illustration, short copy and an easy way out.

Full-screen takeovers

Some modals cover the whole screen. We call this a full-screen takeover, but on desktop it still shouldn’t feel like a new page. On desktop, save it for critical information or required setup. On mobile, full-screen modals are more common, because a partial overlay already covers most of the screen.

When not to use a modal

Every modal forces a context switch. The user stops, reads, decides and then tries to remember what they were doing. When modals show up too often or for low-value content, people learn to close them without reading, and then they close the important ones too.

Skip the modal when:

  • The message is about one element on the page. Use a tooltip.
  • The user doesn't need to act right now. Use a slideout, banner or notification center.
  • The user is in the middle of a critical task, like checkout, a form or a live call.
  • Another modal is already open. Never stack modals.
  • You're showing it on page load to every visitor across the website. That's a popup ad, not product communication.

Better alternatives:

  • Slideouts: routine announcements and non-critical updates.
  • Tooltips: contextual help tied to a specific control.
  • Banners and toasts: status messages and low-priority alerts.
  • Inline content and embeds: guidance that should feel like part of the product, such as a setup card on a dashboard.

For messages tied to one part of the page, like this HubSpot new-feature callout, a tooltip does the job without blocking anything.

Modal design best practices

1. Write a title that works at a glance

The modal title should tell users what the modal is about and make the modal's purpose clear at a glance before they read anything else.

  • Onboarding: "Welcome to {product}" or "Welcome, {first name}"
  • Announcements: start with "New" or "Introducing"
  • Confirmations: restate the action as a question, like "Delete photo?"

2. Keep body copy to one or two sentences

If your modal content needs three paragraphs, you need a page, not a modal. Say what changed, why it helps, and what to do next.

3. Name the outcome on the button

Use "Delete file," "Save changes" or "Try it on this order," not "OK," "Yes" or "Submit." The button label should still make sense if it's the only thing the user reads. For more on writing in-product copy, see our user onboarding best practices.

4. Make the secondary action a real exit

"Not now" and "Maybe later" are fine. "No thanks, I don't like saving money" is not. Guilt-trip copy (sometimes called confirmshaming) makes people trust the next modal less.

5. Make it easy to dismiss

Don't hold users hostage or make it hard to close the modal. For non-critical modals, support all three exits: a visible close (×) button in a top corner, plus other methods like the Escape key and a click on the scrim. For critical modals, like a destructive confirmation, it's fine to require an explicit choice, but give "Cancel" the same weight as the main action.

6. Show, don't just tell

Modals have room for visuals that smaller patterns don't, including images—Airbnb showcases property images using modal windows. A product screenshot shows what's new better than a sentence can. A short GIF can show a feature in action. Branded illustrations make the modal feel like part of your product rather than an ad.

7. Size it to the content

Most modals should not fill the entire screen on desktop: big enough for a visual, a title, a sentence and two buttons, and small enough that users can still see where they are. Center modals that need focus, and keep background content visible with a dimmed background so users keep their context. Use the dimmed scrim so it's obvious the page behind is paused, though a strong shadow can create the same effect.

8. Show progress in multi-step flows

For a series of modals, show how many steps remain: dots, a fraction like "2 of 3," or a bar. Most people will finish something short if they can see the end.

9. Target and cap it

The same modal shouldn't reach every user. Target by role, plan, account and behavior, and trigger on what someone just did (or hasn't done), not on a calendar. Be deliberate about when a modal appears: as a starting point, show no more than one per session, and never two at once.

10. Design for accessibility

Accessible modals work for everyone, including keyboard and screen reader users.

  • Use the native < dialog> element when you can. Opened with showModal(), it renders above the page, makes the rest of the page inert, and closes on Escape by default.
  • Move focus into the modal when it opens, usually to the first interactive element or the title, and return focus to the trigger when it closes.
  • Keep focus inside the modal while it's open, so Tab doesn't wander into the dimmed page.
  • Label it. Use role="dialog" on the container (or alertdialog for urgent confirmations), add aria-modal="true", point aria-labelledby at the title, and use role="document" inside when the content needs more structure.
  • Check contrast and zoom. Text and buttons should meet WCAG contrast ratios, and the modal should still work at 200% zoom and on small screens. Responsive modals matter on desktop and mobile, not just phones.

Mobile modals on mobile devices

On a phone, the line between a modal, a slideout and a large tooltip blurs. A partial overlay already fills most of the screen. That makes every modal feel more disruptive, and on small screens the content may need to scroll independently of the page, so timing matters more than on desktop. On phones, limit modals because screen real estate is tight and the interruption cost is higher.

Mobile modals come in three common shapes:

  • Pop-ups: small, centered dialogs, like system permission requests and review prompts
  • Partial overlays and bottom sheets: cover part of the screen and are good for announcements and options
  • Full-screen modals: for onboarding, milestones and critical confirmations

Some uses that would feel pushy on desktop work well on mobile devices when the timing is right. Two of them:

  • Permission priming. Explain why you need notifications, location or the microphone in your own branded modal, then show the system prompt only to people who say yes. Babbel and Skyscanner do this in the gallery. More in our guide to mobile permission priming.
Skyscanner price alerts push notification priming modal
Skyscanner price alerts push notification priming modal
Babbel microphone access permission priming modal
  • Upgrade prompts. Duolingo and Venmo promote paid products to people who already use the app often.
Duolingo animated upgrade modal for its premium plan
Venmo card in-app promotion modal

Milestones and review prompts

Celebrate progress, and ask for a rating while the experience is still fresh.

Nike Run Club full-screen achievement modal
OpenTable in-app review prompt with star rating

For more, see 8 examples of great mobile modals.

How AI is changing modals

Most products today sit somewhere in the middle of the same shift: a traditional interface people click through, plus an AI assistant in a sidebar. Some users are starting to skip the interface entirely and ask an agent to do the work, inside your product or through tools like Claude and ChatGPT.

That changes modals in four ways.

1. AI features need an introduction

Shipping an AI feature is the easy part. Getting customers to trust it is harder. In a 2025 KPMG and University of Melbourne study of more than 48,000 people in 47 countries, 66% said they use AI regularly, but 54% said they're wary about trusting it.

A modal is a good place to close that gap, at the moment the feature first appears. Say what the feature does, what it doesn't do, and what stays under the user's control. Then let them try it on real work.

The "AI feature introduction" example in the gallery shows one way to do this.

2. AI results need a feedback loop

The first time someone uses an AI feature is the best moment to ask how it went. A one-question modal ("Did that summary get it right?") with an optional comment tells your product team more than a quarter of usage dashboards. Branch on the answer: thank the happy users, and route the unhappy ones to help or to a person.

3. Agents need human checkpoints

When an assistant is about to do something consequential for a user, the approval step is a modal. It's the same design job as any confirmation, only with more to explain: what the agent did, what happens next, and what needs a closer look.

4. Fewer clicks means you measure outcomes, not views

When an agent does the clicking, "did they see the modal?" stops being a useful question. The better one is: did the customers who saw it reach the outcome it was built for, like finishing setup, adopting the feature or renewing, faster than customers who didn't?

Building modals is getting faster too

AI now handles much of the first draft. Visual control over animations and modal components can reduce development time. Templates also speed up setup when teams need a draft modal UI quickly. In Appcues, you can hand Appcues AI a mockup, a page URL or an old Flow and get a draft experience back, or build one from Claude, ChatGPT or Cursor through the Appcues MCP Server. Appcues also watches live experiences and flags when one breaks. A person still reviews and publishes every draft.

Faster building isn't the same as better results, though. In the State of Product Launches survey, 93% of marketers already use AI to keep up with launch volume. Yet of the 30 who rely on it most, only 2 said they're keeping up fine. The more modals you can build, the more discipline you need about which ones should exist.

How to measure a modal

Track four numbers for every modal:

Track these four numbers for every modal. Comparing against users who didn't see it is what shows the modal caused the result.
Metric What it tells you
Completion or click-through rate Did people take the action you asked for?
Dismissal rate Is the modal unwanted, badly timed or shown to the wrong people?
Goal conversion vs. a control group Most useful Did people who saw it reach the outcome more often than people who didn't?
Time to outcome Did it help people get there faster?

Comparing against users who didn't see the modal is what tells you whether the modal caused the result. A high click rate on a modal nobody needed doesn't count.

Build modals that move customers forward

Modals are bold by design. Use them for the moments that matter, and make sure each one moves your customers toward something they came to your product to do.

Appcues lets product and marketing teams build modals that look native to your product, with a low-code builder and Appcues AI to draft them. You can target modals by role, account and behavior, and use the same audience across email, push and your own agents. Then you can see whether each modal moved the outcome it was built for, compared with customers who didn't see it.

Book a demo to see it in your product.

FAQs

What is a modal in UI design?
When should you use a modal?
What's the difference between a modal and a popup?
Are modals bad for UX?
How do you make a modal accessible?
What software can you use to build modal windows?

Stay connected with Appcues

Sign up for Quickcues and get our monthly updates!