Discord Timezones: Why Timestamps Break & How to Fix Them
Timestamps exist to kill timezone confusion — so when one shows the wrong time, one of a short list of causes is responsible. Run down this list.
Advertisement
How Discord converts timezones
The Unix number inside <t:…> is always UTC seconds. Each device converts it to its own system timezone at render time. That means the reader's device clock and timezone setting decide what they see — the sender's timezone is irrelevant once the code is correct.
Fix list, most common first
| Symptom | Cause | Fix |
|---|---|---|
| Year 58,000+ | Milliseconds, not seconds (13 digits) | Divide by 1000 |
Raw <t:…> text | Space, line break or broken bracket | Re-copy the exact snippet |
| Off by whole hours | Picked in the wrong timezone, or device zone wrong | Regenerate in your zone; check device settings |
| Off by minutes | Device clock drift | Enable automatic date & time |
| R never updates | Message not re-rendered | Reopen the channel or hover the message |
DST edge cases
Because the code stores an absolute UTC instant, daylight-saving changes between "now" and the event are handled automatically. The classic mistake is scheduling "8 PM every Friday" by hand across a DST boundary — generate each occurrence separately instead.
Next: usage walkthrough · all 7 formats