Is there a more accurate way to create a Javascript timer than setTimeout?

Something that has always bugged me is how unpredictable the setTimeout() method in Javascript is.

In my experience, the timer is horribly inaccurate in a lot of situations. By inaccurate, I mean the actual delay time seems to vary by 250-500ms more or less. Although this isn’t a huge amount of time, when using it to hide/show UI elements the time can be visibly noticeable.

Are there any tricks that can be done to ensure that setTimeout() performs accurately (without resorting to an external API) or is this a lost cause?

57 thoughts on “Is there a more accurate way to create a Javascript timer than setTimeout?”

  1. Dan, from my experience (that includes implementation of SMIL2.1 language in JavaScript, where time management is in subject) I can assure you that you actually never need high precision of setTimeout or setInterval.

    What does however matter is the order in which setTimeout/setInterval gets executed when queued – and that always works perfectly.

  2. To my experience it is lost effort, even as the smallest reasonable amount of time I ever recognized js act in is around 32-33 ms. …

  3. There is definitely a limitation here. To give you some perspective, the Chrome browser Google just released is fast enough that it can execute setTimeout(function() {}, 0) in 15-20 ms whereas older Javascript engines took hundreds of milliseconds to execute that function. Although setTimeout uses milliseconds, no javascript virtual machine at this point in time can execute code with that precision.

  4. Are there any tricks that can be done
    to ensure that setTimeout() performs
    accurately (without resorting to an
    external API) or is this a lost cause?

    No and no. You’re not going to get anything close to a perfectly accurate timer with setTimeout() – browsers aren’t set up for that. However, you don’t need to rely on it for timing things either. Most animation libraries figured this out years ago: you set up a callback with setTimeout(), but determine what needs to be done based on the value of (new Date()).milliseconds (or equivalent). This allows you to take advantage of more reliable timer support in newer browsers, while still behaving appropriately on older browsers.

    It also allows you to avoid using too many timers! This is important: each timer is a callback. Each callback executes JS code. While JS code is executing, browser events – including other callbacks – are delayed or dropped. When the callback finishes, additional callbacks must compete with other browser events for a chance to execute. Therefore, one timer that handles all pending tasks for that interval will perform better than two timers with coinciding intervals, and (for short timeouts) better than two timers with overlapping timeouts!

    Summary: stop using setTimeout() to implement “one timer / one task” designs, and use the real-time clock to smooth out UI actions.

  5. Hate to say it, but I don’t think there is a way to alleviate this. I do think that it depends on the client system, though, so a faster javascript engine or machine may make it slightly more accurate.

  6. You need to “creep up” on the target time. Some trial and error will be necessary but in essence.

    Set a timeout to complete arround 100ms before the required time

    make the timeout handler function like this:

    if remaining_time > 20ms // maybe as much as 50
      re-queue the handler for 10ms time
      while( remaining_time > 0 ) calculate_remaining_time;
      re-queue the handler for 100ms before the next required time

    But your while loop can still get interrupted by other processes so it’s still not perfect.

  7. If you need to get an accurate callback on a given interval, this gist may help you:

    function interval(duration, fn){
      var _this = this
      this.baseline = undefined
    = function(){
        if(_this.baseline === undefined){
          _this.baseline = new Date().getTime()
        var end = new Date().getTime()
        _this.baseline += duration
        var nextTick = duration - (end - _this.baseline)
          nextTick = 0
        _this.timer = setTimeout(function(){

        }, nextTick)
      this.stop = function(){
  8. .


    This site bailed me out on a major scale.

    You can use the system clock to compensate for timer inaccuracy. If you run a timing function as a series of setTimeout calls — each instance calling the next — then all you have to do to keep it accurate is work out exactly how inaccurate it is, and subtract that difference from the next iteration:

    var start = new Date().getTime(),  
        time = 0,  
        elapsed = '0.0';  
    function instance()  
        time += 100;  
        elapsed = Math.floor(time / 100) / 10;  
        if(Math.round(elapsed) == elapsed) { elapsed += '.0'; }  
        document.title = elapsed;  
        var diff = (new Date().getTime() - start) - time;  
        window.setTimeout(instance, (100 - diff));  
    window.setTimeout(instance, 100);  

    This method will minimize drift and reduce the inaccuracies by more than 90%.

    It fixed my issues, hope it helps

  9. Here’s an example demoing Shog9’s suggestion. This fills a jquery progress bar smoothly over 6 seconds, then redirects to a different page once it’s filled:

    var TOTAL_SEC = 6;
    var FRAMES_PER_SEC = 60;
    var percent = 0;
    var startTime = new Date().getTime();
    setTimeout(updateProgress, 1000 / FRAMES_PER_SEC);
    function updateProgress() {
        var currentTime = new Date().getTime();
        // 1000 to convert to milliseconds, and 100 to convert to percentage
        percent = (currentTime - startTime) / (TOTAL_SEC * 1000) * 100;
        $("#progressbar").progressbar({ value: percent });
        if (percent >= 100) {
            window.location = "newLocation.html";
        } else {
            setTimeout(updateProgress, 1000 / FRAMES_PER_SEC);
  10. I had a similar problem not long ago and came up with an approach which combines requestAnimationFrame with which works very effectively.

    Im now able to make timers accurate to approx 12 decimal places:

        window.performance = window.performance || {}; = (function() {
            return       ||
                performance.mozNow    ||
                performance.msNow     ||
                performance.oNow      ||
                performance.webkitNow ||
                    function() {
                        //Doh! Crap browser!
                        return new Date().getTime(); 

  11. This is a timer I made for a music project of mine which does this thing. Timer that is accurate on all devices.

    var Timer = function(){
      var framebuffer = 0,
      var msSinceInitialized = 0,
      var timer = this;
      var timeAtLastInterval = new Date().getTime();
        var frametime = new Date().getTime();
        var timeElapsed = frametime - timeAtLastInterval;
        msSinceInitialized += timeElapsed;
        timeAtLastInterval = frametime;
      this.setInterval = function(callback,timeout,arguments) {
        var timeStarted = msSinceInitialized;
        var interval = setInterval(function(){
          var totaltimepassed = msSinceInitialized - timeStarted;
          if (totaltimepassed >= timeout) {
            timeStarted = msSinceInitialized;
        return interval;
    var timer = new Timer();
    timer.setInterval(function(){console.log("This timer will not drift."),1000}
  12. If you’re using setTimeout() to yield quickly to the browser so it’s UI thread can catch up with any tasks it needs to do (such as updating a tab, or to not show the Long Running Script dialog), there is a new API called Efficient Script Yielding, aka, setImmediate() that may work a bit better for you.

    setImmediate() operates very similarly to setTimeout(), yet it may run immediately if the browser has nothing else to do. In many situations where you are using setTimeout(..., 16) or setTimeout(..., 4) or setTimeout(..., 0) (i.e. you want the browser to run any outstanding UI thread tasks and not show a Long Running Script dialog), you can simply replace your setTimeout() with setImmediate(), dropping the second (millisecond) argument.

    The difference with setImmediate() is that it is basically a yield; if the browser has sometime to do on the UI thread (e.g., update a tab), it will do so before returning to your callback. However, if the browser is already all caught up with its work, the callback specified in setImmediate() will essentially run without delay.

    Unfortunately it is only currently supported in IE9+, as there is some push back from the other browser vendors.

    There is a good polyfill available though, if you want to use it and hope the other browsers implement it at some point.

    If you are using setTimeout() for animation, requestAnimationFrame is your best bet as your code will run in-sync with the monitor’s refresh rate.

    If you are using setTimeout() on a slower cadence, e.g. once every 300 milliseconds, you could use a solution similar to what user1213320 suggests, where you monitor how long it was from the last timestamp your timer ran and compensate for any delay. One improvement is that you could use the new High Resolution Time interface (aka instead of to get greater-than-millisecond resolution for the current time.

  13. JavaScript timeouts have a defacto limit of 10-15ms (I’m not sure what you’re doing to get 200ms, unless you’re doing 185ms of actual js execution). This is due to windows having a standard timer resolution of 15ms, the only way to do better is to use Windows’ higher resolution timers which is a system wide setting so can screw with other applications on the system and also chews battery life (Chrome has a bug from Intel on this issue).

    The defacto standard of 10-15ms is due to people using 0ms timeouts on websites but then coding in a way that assumes that assumes a 10-15ms timeout (eg. js games which assume 60fps but ask 0ms/frame with no delta logic so the game/site/animation goes a few orders of magnitude faster than intended). To account for that, even on platforms that don’t have windows’ timer problems, the browsers limit timer resolution to 10ms.

  14. shog9’s answer is pretty much what I’d say, although I’d add the following about UI animation/events:

    If you’ve got a box that’s supposed to slide onto the screen, expand downwards, then fade in its contents, don’t try to make all three events separate with delays timed to make them fire one after another – use callbacks, so once the first event is done sliding it calls the expander, once that’s done it calls the fader. jQuery can do it easily, and I’m sure other libraries can as well.

  15. Here are what I use. Since it’s JavaScript, I will post both my Frontend and node.js solutions:

    For both, I use the same decimal rounding function that I highly recommend you keep at arms length because reasons:

    const round = (places, number) => +(Math.round(number + `e+${places}`) + `e-${places}`)

    places – Number of decimal places at which to round, this should be safe and should avoid any issues with floats (some numbers like 1.0000000000005~ can be problematic). I Spent time researching the best way to round decimals provided by high-resolution timers converted to milliseconds.

    that + symbol – It is a unary operator that converts an operand into a number, virtually identical to Number()


    const start =
    // I wonder how long this comment takes to parse
    const end =
    const result = (end - start) + ' ms'
    const adjusted = round(2, result) // see above rounding function


    // Start timer
    const startTimer = () => process.hrtime()
    // End timer
    const endTimer = (time) => {
        const diff = process.hrtime(time)
        const NS_PER_SEC = 1e9
        const result = (diff[0] * NS_PER_SEC + diff[1])
        const elapsed = Math.round((result * 0.0000010))
        return elapsed
    // This end timer converts the number from nanoseconds into milliseconds;
    // you can find the nanosecond version if you need some seriously high-resolution timers.
    const start = startTimer()
    // I wonder how long this comment takes to parse
    const end = endTimer(start)
    console.log(end + ' ms')

Leave a Comment