Discord dynamic timestamps let you post a single time that every member sees in their own timezone. Instead of writing "Event starts at 8 PM EST (1 AM CET)" you post one code, and Discord renders the correct local time for each reader automatically.
The format
A dynamic timestamp is a Unix timestamp wrapped in a special syntax:
<t:1735689600:F>
The number is the Unix time in seconds (not milliseconds). The letter after the second colon is the style, which controls how the time is displayed.
The seven styles
Discord supports seven display styles. The same moment renders differently depending on the letter you choose:
t— short time (8:00 PM)T— long time (8:00:00 PM)d— short date (12/31/2024)D— long date (December 31, 2024)f— short date and time (December 31, 2024 8:00 PM) — the defaultF— long date and time (Tuesday, December 31, 2024 8:00 PM)R— relative (in 3 hours / 2 days ago) — updates live
The relative style R is especially useful for countdowns: it stays accurate without you ever editing the message.
Where you can use them
Dynamic timestamps work in regular messages, embeds, and most bot output. They do not render in channel names, usernames, or the server description. If you paste a code somewhere it isn't supported, members just see the raw <t:...> text.
Generate them without doing math
Converting a date into a Unix timestamp by hand is tedious and error-prone. We built a Discord Timestamp Generator — pick a date and time, and it gives you all seven codes ready to copy, with a live preview of how each one will look.
A tip for recurring events
If you run scheduled events across a multi-server network, post the same timestamp code in every server's announcement channel. Members in different countries each see the start time in their local timezone, which dramatically cuts down "wait, what time is that for me?" questions. Pair that with synchronized event roles — managed centrally with CloudMod — and a network-wide event becomes a single action instead of a dozen copy-pastes.