Why Is My Discord Timestamp Not Working?
If a timestamp is showing raw text, the wrong time, or nothing at all, it's almost always one of these five causes.
1. Milliseconds instead of seconds
Discord expects Unix seconds, not milliseconds. If your number is 13 digits long (something like 1735689600000) instead of 10 (1735689600), that's the problem — many programming languages' default "current time" functions return milliseconds. Fix: drop the last three digits, or divide by 1000 before formatting the code.
2. Malformed brackets or an invalid format letter
Discord only recognizes the exact pattern <t:UNIXTIME:FORMAT> — a smart/curly quote substituted for an angle bracket, a missing colon, or a letter outside t T d D f F R will make Discord display the raw text unchanged instead of a formatted timestamp.Fix: regenerate the code with the generatorrather than hand-editing a previous one, and paste it without any auto-formatting from another app.
3. It's not wrong — it's showing the reader's own time zone
This is the single most common thing mistaken for a bug. A Discord timestamp always renders ineach reader's own local time zone, not the zone it was created in. If you set 3 PM Eastern and a friend in London sees 8 PM, both of you are seeing the correct, converted time — nothing needs fixing.
4. Your system clock was off when you generated it
If you used a "current time" preset while your device's clock was skewed, the resulting timestamp will be genuinely off by that same amount for everyone, in every time zone. Fix: confirm your system clock is correct (most devices sync automatically, but virtual machines and some Linux setups can drift), then regenerate.
5. Daylight saving transitions
A timestamp generated shortly before a daylight-saving change can render an hour off from what you expected once the transition happens, because the underlying moment in time is fixed but the reader's local offset shifts. This isn't a bug in the timestamp — it's the same behaviour any calendar or clock app has across a DST boundary. Fix: double-check the rendered preview close to the transition date, and regenerate if the date shown doesn't match what you intended.
Still not working?
Regenerate the code from scratch using the tool below rather than editing an old one by hand — it guarantees correct syntax and seconds-based Unix time every time. For background on how the mechanism works at all, see how Discord timestamps work.