jQuery .ajaxStop() Method

What Is .ajaxStop()?

.ajaxStop(handler) is jQuery’s legacy shorthand (since 1.0) for binding a global Ajax “batch idle” handler on document. It runs when the last qualifying request finishes and none remain active. Internally it is sugar for .on("ajaxStop", handler).

// Deprecated (since 3.5)
$(document).ajaxStop(function () {
  // runs when no global Ajax requests remain active
});

// Modern replacement
$(document).on("ajaxStop", handler);

// Bind only — no no-arg .ajaxStop() trigger form
// Opt out: $.ajax({ url: "/x", global: false })

How to Use .ajaxStop()

Recognize the legacy call, know it has no handler args, and migrate to .on() / .off().

1. Attach the handler to document with .ajaxStop(handler) (legacy) or .on("ajaxStop", handler) (preferred).
2. Pair with ajaxStart if you show a spinner when activity begins.
3. Remember: the handler is function() — no jqXHR / settings.
4. Remove with .off("ajaxStop", handler) — not .unbind().
5. Use global: false on requests that must stay silent.

Pseudocode

call $(document).ajaxStop(handler)
    → internally: $(document).on("ajaxStop", handler)

when a jQuery Ajax request finishes:
    if request.global === false:
        do not count it / do not fire ajaxStop for it
        return

    decrement active global request count
    fire ajaxComplete for this request

    if active global request count === 0:
        fire ajaxStop
            for each registered handler:
                call handler()

to migrate:
    replace .ajaxStop(fn) with .on("ajaxStop", fn)
    remove with .off("ajaxStop", fn)

Cheat Sheet

Quick map from legacy shorthand to modern APIs.

Live Preview

Run a real $.get() and watch the legacy .ajaxStop() handler update the log.

Ready — pick an action and click Run.

jQuery Examples

Short, copy-ready snippets using the legacy shorthand. Prefer .on("ajaxStop") for new projects.

$(document).ajaxStop(function () {
  $(".log").text("Handler ran via .ajaxStop(function(){ ... }).");
});

$("#fetch").on("click", function () {
  $.get("https://jsonplaceholder.typicode.com/posts/1");
});

Click #fetch → $.get() runs
When request finishes (and none remain) → .log shows
"Handler ran via .ajaxStop(function(){ ... })."

$(document).ajaxStop(function () {
  $("#loading").hide();
});

Last Ajax request completes → #loading hides
Pair with .ajaxStart() / .on("ajaxStart") to show it

var stopCount = 0;

$(document).ajaxStop(function () {
  stopCount++;
  $("#stop-count").text(stopCount);
});

$("#run-two").on("click", function () {
  $.get("/api/a");
  $.get("/api/b");
});

// After both finish: stopCount === 1 (not 2)

Click #run-two → two parallel $.get()
stopCount increments by 1 (not 2)
ajaxComplete would fire twice

// Legacy — deprecated since jQuery 3.5
$(document).ajaxStop(function () {
  $("#out").text("Legacy: .ajaxStop(function(){ ... }).");
});

// Modern — use for new code
$(document).on("ajaxStop", function () {
  $("#out").text("Modern: .on('ajaxStop', function(){ ... }).");
});

Both handlers fire when the batch goes idle
Behavior is identical — only the API name differs
Prefer .on("ajaxStop") for new code

var count = 0;

function onStop() {
  count++;
  $(".log").text("Handler active — ajaxStop count: " + count);
}

$(document).ajaxStop(onStop);

$("#remove").on("click", function () {
  $(document).off("ajaxStop", onStop);
  $(".log").text("Handler removed — count stays " + count + ".");
});

Run $.get() → count increments when idle
Click Remove → .off("ajaxStop", onStop)
Next $.get() → handler no longer runs

Performance Notes

Legacy and modern binds have the same cost. Keep handlers light — toggle visibility only — and prefer ajaxComplete for per-request work.

Key Takeaways