Choose a popup type
The seven Divi Smart Popup types — modal, slide-in, bars, fullscreen and drawers — what each one costs the visitor, and the defaults each applies.
The seven types
Each type has a different weight. Heavier ones interrupt more and should be asked for less often.
- Modal — the default. A centred dialog with an overlay. Interrupts, so it needs a reason.
- Slide-in — a corner box; the page stays usable. Low weight, easy to ignore, good for a second ask.
- Top bar — a full-width strip at the top. Persistent and low weight. Good for notices.
- Bottom bar — the same, at the bottom, further from the navigation.
- Fullscreen — takes over the whole screen. Reserve it for something you actually need.
- Drawer (left) — a full-height side panel, with more room than a slide-in.
- Drawer (right) — the same, from the other edge.
What changing the type does
Changing the type applies matching defaults for position, overlay and scroll lock, which you can then adjust:
- Modal and fullscreen: centred, overlay on, page scrolling locked.
- Slide-in: bottom right, no overlay, page scrolls.
- Top bar and bottom bar: top or bottom centre, no overlay, page scrolls.
- Drawers: left or right edge, overlay on, page scrolling locked.
Only one modal-style popup (modal, fullscreen or drawer) is open at a time. Bars and slide-ins never make another popup wait and are never closed to make room for one.
The controls each one has
Size and position, overlay, close button and its placement, entrance and exit animation, scroll lock, close on Escape, and an automatic close after a number of seconds. Every option and its default is listed in The popup editor, step by step.
Because the popup is a Divi layout, its responsive behaviour is whatever you build in the Divi Builder. The popup width can be set separately for desktop, tablet and phone; there is no separate phone layout generated for you.
Turning it off on a device
Each popup can be limited to desktop, tablet or phone on its Targeting step. Device is decided in the visitor’s browser from the window width (phone below 768px, tablet below 981px, desktop above), which is why it keeps working behind a page cache.
Did this answer the question? No — open a support request