Meridian shows the cities you coordinate with as a stack of bands. Each row draws its own day as a continuous run of colour, from deep indigo at night through dawn rose and amber to the warm paper of midday. Hours outside the working day fall into shadow, so a workable meeting time appears as a bright vertical channel through every row.
Every column is one absolute hour. Moving down a column shows the same instant in every city on the board, which is why the clock numbers differ while the colour stays consistent. The band tells you what that instant feels like where the other person is sitting. A pale cell is the middle of their afternoon and a dark one is the middle of their night. The rose and amber edges are the hour or two around dawn and dusk when a call is possible but inconsiderate.
Above the rows, the overlap meter counts how many places are inside working hours in each column, and the bar fills completely when everyone is. Click or drag across the board to pin a column. The readout underneath gives the exact local time and date in every city, ready to copy, open in Google Calendar, or download as an .ics invite. The coral hairline marks the current moment.
On the day a region moves onto summer time its civil day is 23 hours long, and on the day it moves off, 25. Meridian draws the day that actually exists, so the grid renders 23 columns, 24, or 25, with the repeated hour shown twice where the clocks go back and a marker on the column where the offset changes. A converter that assumes a fixed 24 hour grid will drop or duplicate an hour twice a year, at exactly the moment a scheduling mistake costs the most.
Across much of the Gulf and parts of North Africa the working week runs Sunday to Thursday, so Friday and Saturday are shaded as the weekend and Sunday counts as a working day. The weekend in Iran is Friday. In Nepal it is Saturday. The United Arab Emirates moved to a Saturday and Sunday weekend in January 2022 and is treated accordingly. This affects more than the shading, because a weekend day is excluded from the overlap count and therefore changes which window the board recommends.
Adding MST gives you a row pinned to UTC-7 that never moves. Adding Denver gives you a row that observes daylight saving time and shifts to UTC-6 in summer. Both behaviours are useful and Meridian keeps them distinct, so a row added by abbreviation stays where you put it and is labelled as fixed. The same applies to a bare offset such as UTC+5 or +5:30.
Meridian is made by Ray Grieselhuber and is also referred to as Meridian Scheduler. Several unrelated products share the name, so if you are looking for the browser-based time zone board, this is it. More about Meridian.
Meridian is a single HTML file with no server component, no account, no cookies, and no analytics. Time zone conversion uses the database built into your browser, which updates with your operating system. The board you build is saved locally on your device. See the privacy policy for the detail.
Meridian has a page for the current time in each city it knows about, with the daylight saving dates that apply and the working week in that country. Browse local times by city, see every conversion pair, or check upcoming daylight saving clock changes worldwide.
Yes. There is no account, no paid tier, and no advertising.
From the IANA time zone database built into your browser, by way of
Intl.DateTimeFormat. It updates when your operating system updates, so half
hour and quarter hour zones such as Kolkata, Kathmandu, and Chatham are handled
correctly.
Yes. Once the page has loaded it makes no network requests, so it keeps working without a connection.
Move to the date with the day navigation. The board redraws for that day, including a 23 or 25 hour day, and marks the column where the offset changes.
MST is a fixed UTC-7 row that never moves. Denver observes daylight saving time and shifts to UTC-6 in summer.