ptools.io

How Long Until Friday?

Down to the second, counting to midnight on Friday.

Runs entirely in your browser

Loading the tool…

Or pick one

The count above runs to 00:00 on the next Friday in your own time zone, which is the moment Friday begins.

Most people asking this mean something else, and it is worth being exact about the difference. Friday starting is midnight on Thursday night. Friday ending, in the sense of finishing work, is around 17:00 on Friday itself, roughly forty-one hours later. If the second is the one you want, put that time in the box and the count moves to it.

The working days figure beside the clock is the one that matters for anything due by the end of the week. Asked on a Monday it comes to five, which is the whole of the week you have, and that is a more useful number than the four calendar days the main count shows.

If what you are really counting to is the weekend rather than the day, the weekend countdown starts at Saturday instead. For any other date entirely, use the countdown.

How to use it

  1. Read the count at the top: days, hours, minutes and seconds, moving as you watch.
  2. Look below it for the same span as whole days, weeks and working days.
  3. Change the date in the box to count down to anything else instead.

Questions

Does this count to the start of Friday or the end of the working week?

To the start: midnight, when Friday begins. Finishing work on Friday is a different moment about forty-one hours later, and if that is the one you want, set the time in the box to 17:00 on the Friday and the count adjusts. The page cannot assume it, because the working day ends at a different hour in every job.

What if today is Friday?

The count runs the other way and tells you how long Friday has been going, rather than jumping to next week. A Friday you are already in is not six days away, and saying so would make the page wrong for one day in every seven.

Is this the same as counting to the weekend?

Not quite. Friday is a working day for most people, so the weekend starts about a day later than Friday does. The weekend countdown on this site counts to midnight at the start of Saturday for that reason.

How many hours is that, rather than days?

The count above is already in hours, minutes and seconds as well as days, and the figures below it give the whole span in each unit on its own. A day boundary is not a day of distance: at eight in the evening, tomorrow is four hours away rather than one day away, and it is the hours that decide whether something is worth starting tonight.

Which time zone is this counting in?

Yours, the one your device is set to. The target is midnight in your own local time rather than midnight UTC, because a question about a weekday is a question about the calendar on your wall. Someone reading this in another country sees their own answer, not a translation of anybody else's.

Does it keep counting while I leave the tab open?

Yes, it ticks once a second for as long as the page is open, and picks the count back up from the clock when you return to the tab. Nothing is stored between visits, so opening it again simply asks your clock what time it is now.

Is any of this sent anywhere?

No. The arithmetic runs in WebAssembly inside this tab, and the only thing it reads is your device clock. There is no account, no cookie of ours and no record of what you looked up. Load the page once and it keeps working with the network off.

The same question, other days

Each of these counts to the start of its own day, in your time zone, with the same live seconds and the same working days figure.

Your data stays on your device

Everything above runs inside your browser as WebAssembly compiled from Rust. Nothing you type is uploaded, logged or stored on a server. You can load this page once, go offline, and it still works.

This page makes no requests at all, to anywhere. That is not a promise in the copy: it is a Content-Security-Policy header your browser enforces, and connect-src on it is none. Open the network tab and watch nothing happen.