Your Search Results


    Calls a function or executes a code snippet after a specified delay.


    var timeoutID = window.setTimeout(func, [delay, param1, param2, ...]);
    var timeoutID = window.setTimeout(code, [delay]);


    • timeoutID is the numerical ID of the timeout, which can be used later with window.clearTimeout().
    • func is the function you want to execute after delay milliseconds.
    • code in the alternate syntax is a string of code you want to execute after delay milliseconds (using this syntax is not recommended for the same reasons as using eval())
    • delay is the number of milliseconds (thousandths of a second) that the function call should be delayed by. If omitted, it defaults to 0. The actual delay may be longer; see Notes below.
    • param1, param2, and so forth are additional parameters which are passed through to the function specified by func.

    Note that passing additional parameters to the function in the first syntax does not work in Internet Explorer 9 and below. If you want to enable this functionality on that browser, you must use a polyfill (see the Callback arguments section).

    Important: Prior to Gecko 13 (Firefox 13.0 / Thunderbird 13.0 / SeaMonkey 2.10), Gecko passed an extra parameter to the callback routine, indicating the "actual lateness" of the timeout in milliseconds. This non-standard parameter is no longer passed.


    The following example sets up two simple buttons in a web page and hooks them to the setTimeout() and clearTimeout() routines. Pressing the first button will set a timeout which calls an alert dialog after two seconds and stores the timeout id for use by clearTimeout(). You may optionally cancel this timeout by pressing on the second button.

    HTML Content

    <p>Live Example</p>
    <button onclick="delayedAlert();">Show an alert box after two seconds</button>
    <button onclick="clearAlert();">Cancel alert before it happens</button>

    JavaScript Content

    var timeoutID;
    function delayedAlert() {
      timeoutID = window.setTimeout(slowAlert, 2000);
    function slowAlert() {
      alert("That was really slow!");
    function clearAlert() {

    See also clearTimeout() example.

    Callback arguments

    If you need to pass one or more arguments to your callback function, but need it to work in Internet Explorer 9 and below, which don't support sending additional parameters using either setTimeout() or setInterval()), you can include this IE-specific polyfill which enables the HTML5 standard parameter-passing functionality. Just add this code to the top of your script:

    |*|  IE-specific polyfill which enables the passage of arbitrary arguments to the
    |*|  callback functions of JavaScript timers (HTML5 standard syntax).
    |*|  Syntax:
    |*|  var timeoutID = window.setTimeout(func, delay, [param1, param2, ...]);
    |*|  var timeoutID = window.setTimeout(code, delay);
    |*|  var intervalID = window.setInterval(func, delay[, param1, param2, ...]);
    |*|  var intervalID = window.setInterval(code, delay);
    if (document.all && !window.setTimeout.isPolyfill) {
      var __nativeST__ = window.setTimeout;
      window.setTimeout = function (vCallback, nDelay /*, argumentToPass1, argumentToPass2, etc. */) {
        var aArgs =, 2);
        return __nativeST__(vCallback instanceof Function ? function () {
          vCallback.apply(null, aArgs);
        } : vCallback, nDelay);
      window.setTimeout.isPolyfill = true;
    if (document.all && !window.setInterval.isPolyfill) {
      var __nativeSI__ = window.setInterval;
      window.setInterval = function (vCallback, nDelay /*, argumentToPass1, argumentToPass2, etc. */) {
        var aArgs =, 2);
        return __nativeSI__(vCallback instanceof Function ? function () {
          vCallback.apply(null, aArgs);
        } : vCallback, nDelay);
      window.setInterval.isPolyfill = true;

    IE only fix

    If you want a completely unobtrusive hack for every other mobile or desktop browser, including IE 9 and below, you can either use JavaScript conditional comments:

      // conditional IE < 9 only fix
      @if (@_jscript_version <= 9)
         window.setTimeout =f(window.setTimeout);
         window.setInterval =f(window.setInterval);
      })(function(f){return function(c,t){var a=[],2);return f(function(){c.apply(this,a)},t)}});

    Or go for a very clean approach based on the IE HTML conditional feature:

    <!--[if lte IE 9]><script>
    window.setTimeout =f(window.setTimeout);
    window.setInterval =f(window.setInterval);
    })(function(f){return function(c,t){
    var a=[],2);return f(function(){c.apply(this,a)},t)}

    Another possibility is to use an anonymous function to call your callback, but this solution is a bit more expensive. Example:

    var intervalID = setTimeout(function() { myFunc("one", "two", "three"); }, 1000);

    Yet another possibility is to use function's bind. Example:

    setTimeout(function(arg1){}.bind(undefined, 10), 1000);

    The "this" problem

    When you pass a method to setTimeout() (or any other function, for that matter), it will be invoked with a wrong this value. This problem is explained in detail in the JavaScript reference.


    Code executed by setTimeout() is run in a separate execution context to the function from which it was called. As a consequence, the this keyword for the called function will be set to the window (or global) object; it will not be the same as the this value for the function that called setTimeout. See the following example:

    myArray = ["zero", "one", "two"];
    myArray.myMethod = function (sProperty) {
        alert(arguments.length > 0 ? this[sProperty] : this);
    myArray.myMethod(); // prints "zero,one,two"
    myArray.myMethod(1); // prints "one"
    setTimeout(myArray.myMethod, 1000); // prints "[object Window]" after 1 second
    setTimeout(myArray.myMethod, 1500, "1"); // prints "undefined" after 1.5 seconds
    // let's try to pass the 'this' object, myArray.myMethod, 2000); // error: "NS_ERROR_XPC_BAD_OP_ON_WN_PROTO: Illegal operation on WrappedNative prototype object", myArray.myMethod, 2500, 2); // same error

    As you can see there are no ways to pass the this object to the callback function.

    A possible solution

    A possible way to solve the "this" problem is to replace the two native setTimeout() or setInterval() global functions with two non-native ones which will enable their invocation through the method. The following example shows a possible replacement:

    // Enable the passage of the 'this' object through the JavaScript timers
    var __nativeST__ = window.setTimeout, __nativeSI__ = window.setInterval;
    window.setTimeout = function (vCallback, nDelay /*, argumentToPass1, argumentToPass2, etc. */) {
      var oThis = this, aArgs =, 2);
      return __nativeST__(vCallback instanceof Function ? function () {
        vCallback.apply(oThis, aArgs);
      } : vCallback, nDelay);
    window.setInterval = function (vCallback, nDelay /*, argumentToPass1, argumentToPass2, etc. */) {
      var oThis = this, aArgs =, 2);
      return __nativeSI__(vCallback instanceof Function ? function () {
        vCallback.apply(oThis, aArgs);
      } : vCallback, nDelay);
    Note: These two replacements will also enable the HTML5 standard passage of arbitrary arguments to the callback functions of timers in IE. So they can be used as polyfills also. See the Callback arguments paragraph.

    New feature test:

    myArray = ["zero", "one", "two"];
    myArray.myMethod = function (sProperty) {
        alert(arguments.length > 0 ? this[sProperty] : this);
    setTimeout(alert, 1500, "Hello world!"); // the standard use of setTimeout and setInterval is preserved, but..., myArray.myMethod, 2000); // prints "zero,one,two" after 2 seconds, myArray.myMethod, 2500, 2); // prints "two" after 2.5 seconds

    There are not native solutions ad hoc to this problem.

    Note: JavaScript 1.8.5 introduces the Function.prototype.bind() method, which lets you specify the value that should be used as this for all calls to a given function. This lets you easily bypass problems where it's unclear what this will be, depending on the context from which your function was called.


    You can cancel the timeout using window.clearTimeout(). If you wish to have your function called repeatedly (e.g., every N milliseconds), consider using window.setInterval().

    It's important to note that the function or code snippet cannot be executed until the thread that called setTimeout() has terminated.

    Passing string literals

    Passing a string instead of a function to setTimeout() suffers from the same hazards as using eval.

    // Correct
    window.setTimeout(function() {
        alert("Hello World!");
    }, 500);
    // Incorrect
    window.setTimeout("alert(\"Hello World!\");", 500);

    String literals are evaluated in the global context, so local symbols in the context where setTimeout() was called will not be available when the string is evaluated as code.

    Minimum/maximum delay and timeout nesting

    Historically browsers implement setTimeout() "clamping": successive setTimeout() calls with delay smaller than the "minimum delay" limit are forced to use at least the minimum delay. The minimum delay, DOM_MIN_TIMEOUT_VALUE, is 4 ms (stored in a preference in Firefox: dom.min_timeout_value), with a DOM_CLAMP_TIMEOUT_NESTING_LEVEL of 5.

    In fact, 4 ms is specified by the HTML5 spec and is consistent across browsers released in 2010 and onward. Prior to (Firefox 5.0 / Thunderbird 5.0 / SeaMonkey 2.2), the minimum timeout value for nested timeouts was 10 ms.

    In addition to "clamping", the timeout can also fire later when the page (or the OS/browser itself) is busy with other tasks.

    To implement a 0 ms timeout in a modern browser, you can use window.postMessage() as described here.

    Browsers including Internet Explorer, Chrome, Safari, and Firefox store the delay as a 32-bit signed Integer internally. This causes an Integer overflow when using delays larger than 2147483647, resulting in the timeout being executed immediately.

    Inactive tabs

    In (Firefox 5.0 / Thunderbird 5.0 / SeaMonkey 2.2) and Chrome 11, timeouts are clamped to firing no more often than once per second (1000 ms) in inactive tabs; see bug 633421 for more information about this in Mozilla or for details about this in Chrome.

    Browser compatibility

    Feature Chrome Firefox (Gecko) Internet Explorer Opera Safari
    Basic support 1.0 1.0 (1.7 or earlier) 4.0 4.0 1.0
    Supports parameters for callback*1 (Yes) (Yes) 10.0 (Yes) ?
    Feature Android Chrome for Android Firefox Mobile (Gecko) IE Mobile Opera Mobile Safari Mobile
    Basic support 1.0 1.0 1.0 (1) 6.0 6.0 1.0
    Supports parameters for callback*1 ? ? ? ? ? ?

    *1 Whether it supports the optional parameters when in its first form or not.


    Part of DOM level 0, as specified in HTML5.

    See also

    Hide Sidebar