.png)
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

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:
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.
"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.
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.
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.
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 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 introduces core features in a short series of modals and repeats the product's value along the way.
Big news, like a redesign or a long-awaited feature, earns a modal. Small news doesn't.

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.


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

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 →
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."

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

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:
See the "Approving an agent action" example in the gallery.

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.
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.

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.
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:
Better alternatives:

For messages tied to one part of the page, like this HubSpot new-feature callout, a tooltip does the job without blocking anything.
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.
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.
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.
"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.
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.
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.
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.
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.
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.
Accessible modals work for everyone, including keyboard and screen reader users.
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:
Some uses that would feel pushy on desktop work well on mobile devices when the timing is right. Two of them:
.png)
.png)



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


For more, see 8 examples of great mobile 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.
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.
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.

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.
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?
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.
Track four numbers for every modal:
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.
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.
Product Adoption
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

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:
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.
"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.
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.
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.
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 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 introduces core features in a short series of modals and repeats the product's value along the way.
Big news, like a redesign or a long-awaited feature, earns a modal. Small news doesn't.

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.


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

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 →
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."

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

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:
See the "Approving an agent action" example in the gallery.

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.
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.

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.
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:
Better alternatives:

For messages tied to one part of the page, like this HubSpot new-feature callout, a tooltip does the job without blocking anything.
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.
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.
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.
"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.
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.
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.
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.
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.
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.
Accessible modals work for everyone, including keyboard and screen reader users.
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:
Some uses that would feel pushy on desktop work well on mobile devices when the timing is right. Two of them:
.png)
.png)



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


For more, see 8 examples of great mobile 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.
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.
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.

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.
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?
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.
Track four numbers for every modal:
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.
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.

Sign up for Quickcues and get our monthly updates!