JavaScript Worker terminate() Method

What You’ll Learn

The terminate() method of Worker immediately stops the worker from the main thread. It does not let the worker finish or clean up. Learn when to use it, how it differs from self.close(), and how to free blob URLs—with five examples and try-it labs.

Introduction

A dedicated worker started with new Worker() keeps running until you stop it or the page goes away. When the job is done—or you must cancel heavy work—call worker.terminate() from the main thread.

MDN is clear: the worker is stopped at once. There is no chance to flush files, send a final message, or tidy up. Prefer a cooperative “please stop” message plus self.close() inside the worker when you need a graceful exit.

Understanding Worker.terminate()

An instance method that immediately terminates the dedicated Worker.

• No parameters — call worker.terminate().
• Return value — none (undefined).
• Immediate — no opportunity for the worker to finish operations.
• One-shot — that Worker object cannot be restarted; create a new one.
• Baseline Widely available on MDN (since July 2015); available in Web Workers except Service Workers.

📝 Syntax

terminate()

Parameters

None.

Return value

None (undefined).

Typical pattern

const myWorker = new Worker("worker.js");
// … use postMessage / onmessage …
myWorker.terminate();

⚖️ terminate() vs Related Ideas

Examples Gallery

Examples follow MDN Worker: terminate(). Labs use blob workers so they run in one HTML file.

const myWorker = new Worker(url);
myWorker.terminate();
console.log("Worker terminated");

Worker terminated

worker.onmessage = (e) => {
  console.log(e.data);
  worker.terminate();
  URL.revokeObjectURL(url);
};
worker.postMessage("ping");

pong
(terminated)

worker.terminate();
worker.postMessage("too late");
// onmessage will not fire for a healthy reply

terminated — no reply expected

// worker spins counting until terminated
cancelBtn.onclick = () => {
  worker.terminate();
  out.textContent = "Canceled";
};

Canceled

// inside worker:
self.onmessage = (e) => {
  const result = doWork(e.data);
  self.postMessage(result);
  self.close(); // worker stops itself after sending
};

result ready
(worker closed itself)

🚀 Common Use Cases

• Cancel a background job when the user navigates away or presses Cancel.
• Tear down one-shot demo workers after a single reply.
• Free CPU when a page no longer needs a pool worker.
• Recover from a stuck worker by terminating and creating a new one.
• Pair with revokeObjectURL for blob-based workers.

🔧 How It Works

📝 Notes

• MDN: Baseline Widely available (since July 2015) — no Deprecated / Experimental / Non-standard banner.
• Available in Web Workers except Service Workers.
• DedicatedWorkers can also stop via DedicatedWorkerGlobalScope.close().
• SharedWorkers have SharedWorkerGlobalScope.close() (different API surface).
• Related learning: postMessage(), Worker(), JavaScript hub.

💡 Best Practices