Why we built this
Every remote engineering team has the same three conversations on repeat: what time is this in Berlin, is that too late for Sydney, and is anyone going to have to take this at midnight. The point of this tool is to make those conversations 30 seconds instead of 20 minutes. Add your team members' cities once, and every future meeting-time question is answered instantly.
How it works
Everything runs in your browser using the built-in IANA timezone database that ships with modern browsers. That means:
- Daylight-saving transitions are automatically handled — no manual offset math
- Your team's cities are saved to your local browser storage, not sent to a server
- The overlap strip shows a 24-hour view for each teammate so you can eyeball when a meeting works for everyone
- Times that fall outside typical working hours are flagged so you know when you're asking someone to join at 2am
When to use it
Distributed standups. Cross-timezone hiring interviews. Scheduling all-hands. Kicking off a project with contractors in different countries. Anything where the wrong meeting time silently eats an hour of someone's sleep.
Working remote-first?
Filter open engineering roles by remote-friendly culture — not just "remote" as a location tag.
Browse Remote-Friendly Jobs →Frequently asked
Does this account for daylight saving time?
Yes. Under the hood it uses the browser's IANA timezone database, which knows the historic and future DST rules for every named timezone. If a teammate's city changes offsets on March 30th, this tool will convert correctly on the 29th and the 30th.
Does my team data get stored anywhere?
Only in your own browser, in localStorage. Nothing is sent to our servers. Clearing your browser data clears your team list.
What if my teammate's city isn't in the dropdown?
The dropdown lists common cities, but you can also type any valid IANA timezone name (like America/Argentina/Buenos_Aires or Pacific/Auckland) into the timezone field. Any timezone supported by your browser will work.
How do you decide what counts as “working hours”?
The overlap strip uses 9–17 as core working hours (green), 7–9 and 17–20 as edge hours (yellow), and everything else as outside working hours (red). This is a rough default — individuals vary, but the visual gives you an honest picture of who is being asked to stretch.