Chennai
India · IN
04:15:31
Timezone
Asia/Kolkata
Offset
GMT+5:30
Local date
Sun, May 31, 2026
Unix seconds
1780181131
Compare
Quick answer
San Jose: -12h 30m (Chennai). Confirm local times, UTC offsets, work-hour status, and date relation on this page. For meetings, start with the shared work window and then open the planner or calendar builder with the same cities and date.
India · IN
04:15:31
Timezone
Asia/Kolkata
Offset
GMT+5:30
Local date
Sun, May 31, 2026
Unix seconds
1780181131
United States · US
15:45:31
Timezone
America/Los_Angeles
Offset
GMT-7
Local date
Sat, May 30, 2026
Unix seconds
1780181131
| City | Local time | UTC offset | Work-hour status | Date relation |
|---|---|---|---|---|
| Chennai | 04:15:31 | GMT+5:30 | Off hours | same day |
| San Jose | 15:45:31 | GMT-7 | Work hours | San Jose is previous day |
Time difference
San Jose -12h 30m
Date relation
San Jose is previous day
Next shared work window
No shared work window in 48h
Workday rule
09:00–18:00 local time
San Jose: -12h 30m (Chennai). Check UTC offsets and date relation so midnight crossings are not missed.
Next shared work window: No shared work window in 48h. If it is inconvenient, compare fair alternatives in the meeting planner.
Plan meetingAt least one city observes daylight saving time, so future dates can have a different offset than today. Build the final invite after choosing the exact date.
Build calendar linkThe live clocks show local time, offset, date relation, and overlap first. Then hand the same pair to the planner, board, or invite builder.
Offsets are current GMT differences; timezones are named rules that can shift with DST. For future meetings, keep the city timezone and selected instant together.
Same/next/previous day is calculated from each city’s local date, so it catches midnight crossings that a simple hour difference can hide.
DST can change this pair’s offset on another date. Use the meeting planner or calendar builder with a fixed time before sharing.
Workflow handoff
Keep the same cities and selected instant as you move from comparison to planning, board review, and invite creation.
Offset and date relation: San Jose ⇄ Chennai, -12h 30m. Date relation.
Open timezone boardShared work window: No shared work window in 48h. Work-hour status.
Open timezone boardCarry both cities into the planner: Chennai / San Jose. Date relation.
Plan meetingGoogle Calendar, Outlook, and ICS with named IANA time zones.
Build calendar linkShare this pair with the same context: Chennai / San Jose.
Open timezone boardSan Jose: -12h 30m (Chennai). Current offset and date relation: San Jose is previous day.
Next shared work window: No shared work window in 48h. Use the shared work window first. If it does not fit, compare another instant in the meeting planner.
Chennai ↔ San Jose: -12h 30m. has daylight-saving risk on at least one side. Keep both IANA time zones and re-check transition weeks. Asia/Kolkata / America/Los_Angeles.
Verify the offset and date relation, open the same cities in the meeting planner, then publish Google Calendar, Outlook, and ICS links.