How Long Until Wednesday? Hours, Minutes and Days Left

The count above runs to 00:00 on the next Wednesday in your own time zone.

Wednesday is the middle of the working week without being the middle of the week itself, and the two get confused. Counting Monday to Friday, Wednesday is the third of five and the week tips at midday on it. Counting all seven days from Monday, it is the fourth of seven and the tipping point is midnight at the end of it. Neither is wrong; they are answers to different questions, and which one you want depends on whether weekends are part of your week.

That is why the figure to read here is often working days rather than days. A deadline on Wednesday afternoon leaves you the working days shown, not the calendar days, and the difference is what a weekend does to a plan.

For a Wednesday further out, or any other date, put it in the box or open the full 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 Wednesday the middle of the week?

Of the working week, yes: third of the five days from Monday to Friday, with the halfway point falling at lunchtime. Of the whole seven-day week starting Monday it is the fourth day, and the halfway point is midnight at its end. Calendars that start on Sunday put Wednesday in the middle column too, which is where the idea comes from.

Does the count include the weekend?

The main count is calendar time, so it includes every day and every hour, weekend included. The working days figure beside it is the one that leaves Saturday and Sunday out, and for anything with a deadline attached that is usually the number you actually want.

What happens on Wednesday itself?

The count reaches zero at midnight and then counts up, so through the day it reads as how long Wednesday has been going. Nothing resets and nothing jumps forward a week while you are still in the day you asked about.

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.