Content · Web Development · HTML

HTML canplaythrough DOM Event: Reference and Examples

Learn when the canplaythrough 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 canplaythrough event happens when the browser estimates media may play through without further buffering.

When canplaythrough happens


The browser estimates media may play through without further buffering.

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


<video id="demo-target" controls preload="metadata" width="320">
    <source src="sample-video.mp4" type="video/mp4">
</video>
<p id="event-status" role="status">Waiting for canplaythrough...</p>
<script>
    const eventTarget = document.getElementById("demo-target");
    const eventStatus = document.getElementById("event-status");

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

Reading the code


The browser listens for canplaythrough 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.

Load a supported file; the estimate is not a download guarantee.

To test this example, put a real supported media file at the shown path. Events tied to buffering or download behavior may not fire in the same order on every connection. An unavailable sample file is not proof that your event listener is broken.

Try it in your browser


Open the page, show the Console panel, and follow this test: Load a supported file; the estimate is not a download guarantee. Then change one thing in the example and observe whether the event still fires.

Common Beginner Mistakes


  • Expecting canplaythrough to fire without its required user action or browser condition.
  • Load a supported file; the estimate is not a download guarantee.
  • Adding repeated event listeners without considering cleanup or unwanted side effects.

Key Takeaways


  • canplaythrough reports the browser estimates media may play through without further buffering.
  • addEventListener("canplaythrough", ...) listens for the event on the appropriate target.
  • Load a supported file; the estimate is not a download guarantee.
Share this resourceSend this page to someone who may find it useful.