StreamWeekHow the conversion works
Your browser ships with the IANA time-zone database, the same rules your phone's clock uses. StreamWeek asks it two questions for every stream: “what exact moment is 8:00 PM on Monday 26 October in London?” and “what does that moment look like in New York, Los Angeles and Tokyo?”. Because the question includes the date, the answer accounts for whichever daylight-saving rules apply that day.
For the week of 26 October 2026, an 8:00 PM London stream converts to 4:00 PM EDT, 1:00 PM PDT, 5:00 AM JST +1. A week earlier New York is 3:00 PM EDT, and a week later 3:00 PM EST. A schedule with fixed offsets would have one of those weeks wrong.
The weeks that catch people out
- March: the US moves clocks forward on the second Sunday, Europe on the last Sunday. For two to three weeks, New York is 4 hours behind London instead of 5.
- Late October to early November: Europe moves back on the last Sunday of October, the US a week later. Again the gap is an hour smaller for one week.
- Southern hemisphere: Sydney moves forward in early October and back in early April, the opposite direction to Europe and the US. The gap between Sydney and London can change by two hours over a year.
- Japan, India and most of Asia don't use daylight saving, so the change always comes from the other side.
Spring-forward gaps
On the night clocks go forward, one hour doesn't exist; in London, 1:00 AM jumps straight to 2:00 AM. If you schedule a stream inside that gap, StreamWeek moves it forward by an hour (1:30 becomes 2:30) and warns you under the preview. When clocks go back and an hour happens twice, it uses the first one.
Reading +1 and −1
Every converted time stays under your day, with a mark when it's a different day for that viewer. “5:00 AM JST +1” under Monday means Tuesday morning in Japan. “6:00 PM PDT −1” under a Tokyo Tuesday means Monday evening in Los Angeles. One rule everywhere keeps the week readable as a single row of seven days.
Let Discord do the conversion too
No image can show every viewer's zone. For everyone else, Copy for Discord writes timestamps that Discord displays in each reader's own time, and the .ics file lets people add streams to their calendar, which also shows local time. Between the image, the Discord post and the calendar file, nobody has to do maths.
Frequently asked questions
Why not just use fixed offsets like ET = UK − 5?
Because the offset changes. The UK and US switch daylight saving on different Sundays, so for about a week in March and a week in late October or early November the gap is 4 hours, not 5. Fixed offsets are wrong in those weeks; real dates are not.
Which time zones should I show?
Your home zone plus the 2 or 3 places most of your viewers live, from your channel analytics. Common picks are JST, PT, ET, UK, CET, AEST and IST, which all have quick buttons.
Why does a label say EDT one week and EST the next?
The label follows the date. New York uses EDT in summer and EST in winter, London uses BST and GMT, Sydney uses AEDT and AEST. The image shows whichever applies to that stream.
What if my home zone has no daylight saving?
Then your times never shift, but your viewers' times still can. If you live in Tokyo, the LA and New York conversions change by an hour when the US changes clocks, and the tool handles that.
Does it handle half-hour zones like India?
Yes. India (IST, UTC+5:30), Adelaide and other zones with 30- or 45-minute offsets are converted with the same database, so a 20:00 IST stream shows the right minutes elsewhere.
More templates and guides
Last updated · Written by the Rooh Sites team.