JavaScript Window confirm() Method

What You’ll Learn

The confirm() method asks the user to approve or cancel an action. This tutorial covers syntax, the boolean return value, five beginner-friendly examples, how it differs from alert() and prompt(), and when to prefer custom modal UI.

Introduction

When your app is about to do something irreversible—delete a record, submit a form, or navigate away from unsaved work—you should ask the user first. The window.confirm() method is the built-in browser way to show a short question with OK and Cancel buttons and get a yes-or-no answer back as a boolean.

Like alert(), confirm() is synchronous: JavaScript stops until the user picks a button. That makes the API easy for beginners, but most production sites eventually replace it with styled in-page modals for better design and accessibility.

Understanding the confirm() Method

Pass a string (or value that converts to a string) as the message. The browser shows a modal dialog. If the user clicks OK, the method returns true. If they click Cancel or dismiss the dialog, it returns false.

The usual pattern is to store the result and branch: if (confirm("Delete?")) { /* proceed */ }. Because the dialog blocks the main thread, tie confirms to explicit user actions (button clicks) rather than firing them automatically when the page loads.

📝 Syntax

General form of Window.confirm():

const ok = window.confirm(message);
// shorthand (same in browsers):
const ok = confirm(message);

Parameters

• message (optional) — text shown in the dialog. Non-string values are converted with ToString.

Return value

• true — user clicked OK.
• false — user clicked Cancel or dismissed the dialog.

Common patterns

• if (confirm("Delete item?")) { deleteItem(); } — guard destructive actions.
• const ok = confirm("Submit form?"); if (ok) form.submit(); — explicit variable for readability.
• button.onclick = () => { if (!confirm("Leave?")) return; navigate(); } — cancel early when user says no.

Examples Gallery

Each snippet opens a native OK/Cancel dialog. Use the Try-it links to run them behind a button. Dialog text and possible outcomes are shown below as “View Output” for reference.

const userConfirmed = confirm("Are you sure you want to delete this item?");

if (userConfirmed) {
  console.log("Item deleted successfully.");
} else {
  console.log("Deletion canceled by the user.");
}

Are you sure you want to delete this item?

If OK → Item deleted successfully.
If Cancel → Deletion canceled by the user.

if (confirm("Do you want to proceed?")) {
  console.log("User confirmed — running next step.");
} else {
  console.log("User canceled — nothing changed.");
}

Do you want to proceed?

If OK → User confirmed — running next step.
If Cancel → User canceled — nothing changed.

const submitForm = confirm("Do you want to submit the form?");

if (submitForm) {
  document.getElementById("myForm").submit();
  console.log("Form submitted.");
} else {
  console.log("Form submission canceled by the user.");
}

Do you want to submit the form?

If OK → Form submitted.
If Cancel → Form submission canceled by the user.

const leavePage = confirm("You have unsaved changes. Leave this page?");

if (leavePage) {
  window.location.href = "dashboard.html";
  console.log("Navigating away…");
} else {
  console.log("Navigation canceled by the user.");
}

You have unsaved changes. Leave this page?

If OK → Navigating away…
If Cancel → Navigation canceled by the user.

<button id="logoutBtn" type="button">Log out</button>
<p id="status"></p>

<script>
  document.getElementById("logoutBtn").addEventListener("click", function () {
    const ok = confirm("Log out of your account?");
    document.getElementById("status").textContent = ok
      ? "Logged out."
      : "Logout canceled.";
  });
</script>

Log out of your account?

If OK → Logged out.
If Cancel → Logout canceled.

🚀 Common Use Cases

• Delete confirmations — prevent accidental removal of rows, files, or accounts.
• Form submission — last chance before sending payment or registration data.
• Navigation guards — warn before leaving a page with unsaved edits.
• Logout flows — confirm the user wants to end their session.
• Bulk actions — “Apply changes to 50 items?” before running batch updates.
• Learning demos — teach boolean logic and branching with visible OK/Cancel results.

📝 Notes

• confirm() is not available in Node.js without a browser—use CLI prompts or libraries on the server.
• Button labels may read “OK” / “Cancel” or localized equivalents depending on the browser language.
• Dismissing via Escape or the dialog close control typically returns false, same as Cancel.
• Do not nest multiple confirms in a row—it frustrates users and feels like spam.
• For accessibility, native dialogs are announced, but custom modals with ARIA give you finer control.
• Mobile browsers show the same API but with platform-native styling you cannot customize.

💡 Best Practices