Content · Web Development · HTML

HTML afterprint DOM Event: Reference and Examples

Learn when the afterprint DOM event fires and how to handle it with JavaScript using a practical HTML example.

1 views Published Oct 19, 2026 Updated Oct 19, 2026 Admin

When someone interacts with a webpage, the browser sends events to the relevant JavaScript code. The afterprint event happens when the browser leaves its print flow.

When afterprint happens


The browser leaves its print flow.

You can listen for it using addEventListener(). That keeps event handling separate from HTML attributes such as onclick and works well with modern code organization.

A small working example


<p>Try the relevant browser action described below.</p>
<p id="event-status" role="status">Waiting for afterprint...</p>
<script>
    const eventTarget = window;
    const eventStatus = document.getElementById("event-status");

    if (eventTarget) {
        eventTarget.addEventListener("afterprint", (eventDetails) => {
            eventStatus.textContent = "afterprint event received";
            console.log(eventDetails.type, eventDetails.target);
        });
    }
</script>

Reading the code


The browser listens for afterprint on the relevant target. When the event occurs, the callback receives eventDetails, updates the status message and logs the event name and target in Developer Tools.

Open Print, then close the dialog or finish printing; browser print behavior varies.

Some events need a specific browser condition, another tab or window, or a Web Component to reproduce. Read the trigger steps carefully before deciding that an event handler is not working.

Try it in your browser


Open the page, show the Console panel, and follow this test: Open Print, then close the dialog or finish printing; browser print behavior varies. Then change one thing in the example and observe whether the event still fires.

Common Beginner Mistakes


  • Expecting afterprint to fire without its required user action or browser condition.
  • Open Print, then close the dialog or finish printing; browser print behavior varies.
  • Adding repeated event listeners without considering cleanup or unwanted side effects.

Key Takeaways


  • afterprint reports the browser leaves its print flow.
  • addEventListener("afterprint", ...) listens for the event on the appropriate target.
  • Open Print, then close the dialog or finish printing; browser print behavior varies.
Share this resourceSend this page to someone who may find it useful.