How Long Until Sunday? Days, Hours and Minutes Left

The count above runs to 00:00 on the next Sunday in your own time zone, which is midnight at the end of Saturday.

Sunday is the day the calendars disagree about most. Under ISO 8601 it is day 7, the last day of the week, which is what almost every database, spreadsheet function and programming library assumes. On an American, Canadian or Japanese wall calendar it is the first day, sitting in the leftmost column. So "the end of the week" and "the start of the week" can both mean this Sunday, depending on who is speaking, and a weekly report that lands on a boundary can be a day out for exactly this reason.

The count sidesteps all of it by counting to the next Sunday to arrive, which is the same moment under either convention.

Note that the working days figure will usually be the same for Sunday as for the Saturday before it, since neither is a working day and the count stops at the Friday. For any other date, use the countdown.

How to use it

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

Questions

Is Sunday the first day of the week or the last?

Both, depending on the convention. ISO 8601 makes it day 7 and the last, which is what most software uses; calendars in the United States, Canada and Japan put it first. The count above is the same either way, because it counts to the next Sunday to arrive rather than to a position in a grid.

Does it count to Sunday morning or Sunday night?

To the start of Sunday, midnight at the end of Saturday. If you mean a particular hour on Sunday, put that time in the box: the count then runs to the moment itself rather than to the beginning of the day.

Why is the working days figure the same as for Saturday?

Because working days are counted Monday to Friday, and neither Saturday nor Sunday adds to the total. A count ending on either weekend day includes the same weekdays and stops at the Friday before, which is what makes a Friday deadline and a Sunday one so much closer together than they look.

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.