Skip to main content
View Zag.js on Github
Join the Discord server


A dialog is a window overlaid on either the primary window or another dialog window. Content behind a modal dialog is inert, meaning that users cannot interact with it.



  • Supports modal and non-modal modes.
  • Focus is trapped and scrolling is blocked in the modal mode.
  • Provides screen reader announcements via rendered title and description.
  • Pressing Esc closes the dialog.


To use the dialog machine in your project, run the following command in your command line:

npm install @zag-js/dialog @zag-js/react # or yarn add @zag-js/dialog @zag-js/react

This command will install the framework agnostic dialog logic and the reactive utilities for your framework of choice.


To use the dialog component correctly, you'll need to understand its anatomy and how we name its parts.

Each part includes a data-part attribute to help identify them in the DOM.


First, import the dialog package into your project

import * as dialog from "@zag-js/dialog"

The dialog package exports two key functions:

  • machine — The state machine logic for the dialog widget as described in WAI-ARIA specification.
  • connect — The function that translates the machine's state to JSX attributes and event handlers.

You'll need to provide a unique id to the useMachine hook. This is used to ensure that every part has a unique identifier.

Next, import the required hooks and functions for your framework and use the dialog machine in your project 🔥

import * as dialog from "@zag-js/dialog" import { useMachine, normalizeProps, Portal } from "@zag-js/react" export function Dialog() { const [state, send] = useMachine(dialog.machine({ id: "1" })) const api = dialog.connect(state, send, normalizeProps) return ( <> <button {...api.getTriggerProps()}>Open Dialog</button> { && ( <Portal> <div {...api.getBackdropProps()} /> <div {...api.getPositionerProps()}> <div {...api.getContentProps()}> <h2 {...api.getTitleProps()}>Edit profile</h2> <p {...api.getDescriptionProps()}> Make changes to your profile here. Click save when you are done. </p> <div> <input placeholder="Enter name..." /> <button>Save</button> </div> <button {...api.getCloseTriggerProps()}>Close</button> </div> </div> </Portal> )} </> ) }

Managing focus within the dialog

When the dialog opens, it automatically sets focus on the first focusable elements and traps focus within it, so that tabbing is constrained to it.

To control the element that should receive focus on open, pass the initialFocusEl context (which can be an element or a function that returns an element)

export function Dialog() { // initial focused element ref const inputRef = useRef(null) const [state, send] = useMachine( dialog.machine({ initialFocusEl: () => inputRef.current, }), ) // ... return ( //... <input ref={inputRef} /> // ... ) }

To set the element that receives focus when the dialog closes, pass the finalFocusEl in the similar fashion as shown above.

Closing the dialog on interaction outside

By default, the dialog closes when you click its overlay. You can set closeOnInteractOutside to false if you want the modal to stay visible.

const [state, send] = useMachine( dialog.machine({ closeOnInteractOutside: false, }), )

You can also customize the behavior by passing a function to the onInteractOutside context and calling event.preventDefault()

const [state, send] = useMachine( dialog.machine({ onInteractOutside(event) { const target = if (target?.closest("<selector>")) { return event.preventDefault() } }, }), )

Listening for open state changes

When the dialog is opened or closed, the onOpenChange callback is invoked.

const [state, send] = useMachine( dialog.machine({ onOpenChange(details) { // details => { open: boolean } console.log("open:", }, }), )

Controlling the scroll behavior

When the dialog is open, it prevents scrolling on the body element. To disable this behavior, set the preventScroll context to false.

const [state, send] = useMachine( dialog.machine({ preventScroll: false, }), )

Creating an alert dialog

The dialog has support for dialog and alert dialog roles. It's set to dialog by default. To change it's role, pass the role: alertdialog property to the machine's context.

That's it! Now you have an alert dialog.

const [state, send] = useMachine( dialog.machine({ role: "alertdialog", }), )

By definition, an alert dialog will contain two or more action buttons. We recommended setting focus to the least destructive action via initialFocusEl

Styling guide

Earlier, we mentioned that each accordion part has a data-part attribute added to them to select and style them in the DOM.

[data-part="trigger"] { /* styles for the trigger element */ } [data-part="backdrop"] { /* styles for the backdrop element */ } [data-part="positioner"] { /* styles for the positioner element */ } [data-part="content"] { /* styles for the content element */ } [data-part="title"] { /* styles for the title element */ } [data-part="description"] { /* styles for the description element */ } [data-part="close-trigger"] { /* styles for the close trigger element */ }

Open and closed state

The dialog has two states: open and closed. You can use the data-state attribute to style the dialog or trigger based on its state.

[data-part="content"][data-state="open|closed"] { /* styles for the open state */ } [data-part="trigger"][data-state="open|closed"] { /* styles for the open state */ }

Methods and Properties

Machine Context

The dialog machine exposes the following context properties:

  • idsPartial<{ trigger: string; positioner: string; backdrop: string; content: string; closeTrigger: string; title: string; description: string; }>The ids of the elements in the dialog. Useful for composition.
  • trapFocusbooleanWhether to trap focus inside the dialog when it's opened
  • preventScrollbooleanWhether to prevent scrolling behind the dialog when it's opened
  • modalbooleanWhether to prevent pointer interaction outside the element and hide all content below it
  • initialFocusEl() => HTMLElementElement to receive focus when the dialog is opened
  • finalFocusEl() => HTMLElementElement to receive focus when the dialog is closed
  • restoreFocusbooleanWhether to restore focus to the element that had focus before the dialog was opened
  • onOpenChange(details: OpenChangeDetails) => voidCallback to be invoked when the dialog is opened or closed
  • closeOnInteractOutsidebooleanWhether to close the dialog when the outside is clicked
  • closeOnEscapebooleanWhether to close the dialog when the escape key is pressed
  • aria-labelstringHuman readable label for the dialog, in event the dialog title is not rendered
  • role"dialog" | "alertdialog"The dialog's role
  • openbooleanWhether the dialog is open
  • open.controlledbooleanWhether the dialog is controlled by the user
  • dir"ltr" | "rtl"The document's text/writing direction.
  • idstringThe unique identifier of the machine.
  • getRootNode() => Node | ShadowRoot | DocumentA root node to correctly resolve document in custom environments. E.x.: Iframes, Electron.
  • onEscapeKeyDown(event: KeyboardEvent) => voidFunction called when the escape key is pressed
  • onPointerDownOutside(event: PointerDownOutsideEvent) => voidFunction called when the pointer is pressed down outside the component
  • onFocusOutside(event: FocusOutsideEvent) => voidFunction called when the focus is moved outside the component
  • onInteractOutside(event: InteractOutsideEvent) => voidFunction called when an interaction happens outside the component
  • persistentElements(() => Element)[]Returns the persistent elements that: - should not have pointer-events disabled - should not trigger the dismiss event

Machine API

The dialog api exposes the following methods:

  • openbooleanWhether the dialog is open
  • setOpen(open: boolean) => voidFunction to open or close the dialog

Data Attributes

"open" | "closed"
"open" | "closed"
"open" | "closed"


Adheres to the Alert and Message Dialogs WAI-ARIA design pattern.

Keyboard Interactions

  • Enter
    When focus is on the trigger, opens the dialog.
  • Tab
    Moves focus to the next focusable element within the content. Focus is trapped within the dialog.
  • Shift + Tab
    Moves focus to the previous focusable element. Focus is trapped within the dialog.
  • Esc
    Closes the dialog and moves focus to trigger or the defined final focus element

Edit this page on GitHub

Proudly made in🇳🇬by Segun Adebayo

Copyright © 2024
On this page