I debug time bugs at 2 AM more than I want to admit. An epoch that is off by a factor of 1000, a cron that fires on the wrong day, a meeting booked across three zones. These nine tools answer the question fast, in plain words, so I can get back to the deploy.
I paste a Unix timestamp and get a real date back, in UTC and in my local time. Or I pick a date and get the epoch back. Seconds and milliseconds both work.
I type a time in one zone and see it in another. DST is handled by the browser clock data, not by my guesswork.
I pick minute, hour, day, month, and weekday from dropdowns and get a five-field cron expression plus what it means in plain words. No more guessing field order at deploy time.
I paste a cron expression I found in a repo and get it back in plain words, plus the next five times it will run. That is how I check a schedule before I trust it.
I pick a start and end date and count the working days between them. Monday to Friday count. Saturday and Sunday do not. Both dates count if they are weekdays.
I pick a date and get its ISO week number and ISO year. Week 1 is the week with the first Thursday of the year. That rule trips people up every January, so I check it here.
I type a year and get a straight answer. Divisible by 4 is a leap year, unless it is divisible by 100, unless it is also divisible by 400. That is why 2000 was a leap year and 1900 was not.
I paste a list of timestamps, one per line, and get a date for each one. Logs hand me dozens at a time, and converting them one by one is a waste of an on-call hour.
I pick a meeting time in one zone and see it in every zone my team sits in. I check this before I send the invite, not after someone joins at 3 AM.