Baseline Widely available

This feature is well established and works across many devices and browser versions. It’s been available across browsers since March 2019.

Note: This feature is available in Web Workers.

The AbortSignal interface represents a signal object that allows you to communicate with an asynchronous operation (such as a fetch request) and abort it if required via an AbortController object.

EventTarget AbortSignal

Instance properties

Also inherits properties from its parent interface, EventTarget.

AbortSignal.aborted Read only

A Boolean that indicates whether the request(s) the signal is communicating with is/are aborted (true) or not (false).

AbortSignal.reason Read only

A JavaScript value providing the abort reason, once the signal has aborted.

Static methods

Also inherits methods from its parent interface, EventTarget.


Returns an AbortSignal instance that is already set as aborted.


Returns an AbortSignal that aborts when any of the given abort signals abort.


Returns an AbortSignal instance that will automatically abort after a specified time.

Instance methods

Also inherits methods from its parent interface, EventTarget.


Throws the signal's abort reason if the signal has been aborted; otherwise it does nothing.


Also inherits events from its parent interface, EventTarget.

Listen to this event using addEventListener() or by assigning an event listener to the oneventname property of this interface.


Invoked when the asynchronous operations the signal is communicating with is/are aborted. Also available via the onabort property.


Aborting a fetch operation using an explicit signal

The following snippet shows how we might use a signal to abort downloading a video using the Fetch API.

We first create an abort controller using the AbortController() constructor, then grab a reference to its associated AbortSignal object using the AbortController.signal property.

When the fetch request is initiated, we pass in the AbortSignal as an option inside the request's options object (the {signal} below). This associates the signal and controller with the fetch request, and allows us to abort it by calling AbortController.abort(). Below you can see that the fetch operation is aborted in the second event listener, which triggered when the abort button (abortBtn) is clicked.

const controller = new AbortController();
const signal = controller.signal;

const url = "video.mp4";
const downloadBtn = document.querySelector(".download");
const abortBtn = document.querySelector(".abort");

downloadBtn.addEventListener("click", fetchVideo);

abortBtn.addEventListener("click", () => {
  console.log("Download aborted");

function fetchVideo() {
  fetch(url, { signal })
    .then((response) => {
      console.log("Download complete", response);
    .catch((err) => {
      console.error(`Download error: ${err.message}`);

Note: When abort() is called, the fetch() promise rejects with an "AbortError" DOMException.

You can find a full working example on GitHub; you can also see it running live.

Aborting a fetch operation with a timeout

If you need to abort the operation on timeout then you can use the static AbortSignal.timeout() method. This returns an AbortSignal that will automatically timeout after a certain number of milliseconds.

The code snippet below shows how you would either succeed in downloading a file, or handle a timeout error after 5 seconds. Note that when there is a timeout the fetch() promise rejects with a "TimeoutError" DOMException. This allows code to differentiate between timeouts (for which user notification is probably required), and user aborts.

const url = "video.mp4";

try {
  const res = await fetch(url, { signal: AbortSignal.timeout(5000) });
  const result = await res.blob();
  // …
} catch (err) {
  if (err.name === "TimeoutError") {
    console.error("Timeout: It took more than 5 seconds to get the result!");
  } else if (err.name === "AbortError") {
      "Fetch aborted by user action (browser stop button, closing tab, etc.",
  } else if (err.name === "TypeError") {
    console.error("AbortSignal.timeout() method is not supported");
  } else {
    // A network error, or some other problem.
    console.error(`Error: type: ${err.name}, message: ${err.message}`);

Aborting a fetch with timeout or explicit abort

If you want to abort from multiple signals, you can use AbortSignal.any() to combine them into a single signal. The following example shows this using fetch:

try {
  const controller = new AbortController();
  const timeoutSignal = AbortSignal.timeout(5000);
  const res = await fetch(url, {
    // This will abort the fetch when either signal is aborted
    signal: AbortSignal.any([controller.signal, timeoutSignal]),
  const body = await res.json();
} catch (e) {
  if (e.name === "AbortError") {
    // Notify the user of abort.
  } else if (e.name === "TimeoutError") {
    // Notify the user of timeout
  } else {
    // A network error, or some other problem.
    console.log(`Type: ${e.name}, Message: ${e.message}`);

Note: Unlike when using AbortSignal.timeout(), there is no way to tell whether the final abort was caused by a timeout.

Implementing an abortable API

An API that needs to support aborting can accept an AbortSignal object, and use its state to trigger abort signal handling when needed.

A Promise-based API should respond to the abort signal by rejecting any unsettled promise with the AbortSignal abort reason. For example, consider the following myCoolPromiseAPI, which takes a signal and returns a promise. The promise is rejected immediately if the signal is already aborted, or if the abort event is detected. Otherwise it completes normally and then resolves the promise.

function myCoolPromiseAPI(/* …, */ { signal }) {
  return new Promise((resolve, reject) => {
    // If the signal is already aborted, immediately throw in order to reject the promise.
    if (signal.aborted) {

    // Perform the main purpose of the API
    // Call resolve(result) when done.

    // Watch for 'abort' signals
    signal.addEventListener("abort", () => {
      // Stop the main operation
      // Reject the promise with the abort reason.

The API might then be used as shown. Note that AbortController.abort() is called to abort the operation.

const controller = new AbortController();
const signal = controller.signal;


myCoolPromiseAPI({ /* …, */ signal })
  .then((result) => {})
  .catch((err) => {
    if (err.name === "AbortError") return;
  .then(() => stopSpinner());


APIs that do not return promises might react in a similar manner. In some cases it may make sense to absorb the signal.


DOM Standard
# interface-AbortSignal

Browser compatibility

BCD tables only load in the browser

See also