Discord Timestamp Generator

Because Discord renders the tag in each reader's own timezone. Everyone in the channel sees the moment in their local time without anyone doing the arithmetic, so you never have to write "20:00 CEST (2pm EDT / 11am PDT)" again.

The relative style goes further and keeps counting on its own, so a pinned message showing "in 2 days" stays correct tomorrow without being edited.

Usually the timestamp was built in a different timezone than you meant. A Unix timestamp is one fixed instant with no timezone attached, so if it was generated as UTC while you were thinking in local time, everyone sees the same wrong moment. Open the options above and check the timezone matches the one you have in mind.

Daylight saving is the other cause. Countries switch on different dates, so build the timestamp for the real target date rather than adding a fixed number of seconds to some other date.

Finally, make sure the number is in seconds, not milliseconds. A 13 digit value lands roughly 50,000 years from now.

They render in normal messages, replies, embeds sent by bots and webhooks, forum posts, and thread starters. They work the same on desktop, web, and mobile.

They do not render in places Discord treats as plain text: channel names and topics, your status, server descriptions, and code blocks. Wrapping a tag in backticks shows the raw code, which is handy when you want to show someone the syntax.

Zulip has the same idea with its own syntax, <time:2026-08-03T14:30:00+02:00>, and the table above builds it for you. Zulip shows one absolute localised date and time, so there is no equivalent of Discord's relative countdown.

Almost nowhere else lets you do this by typing. Slack and Microsoft Teams both have the feature, but only for messages sent by an app: Slack through its API or a webhook, Teams inside an Adaptive Card. Typing either one into the message box just shows the raw text.

Telegram can show a per reader time, but you insert it from the composer rather than pasting a tag, so there is nothing for a generator to produce. WhatsApp, Signal, X, Reddit, Google Chat, Webex and Twitch have no such feature at all, and a pasted tag will simply appear as literal text.

The number of seconds since 1 January 1970, 00:00:00 UTC, known as the Unix epoch. It is how most software stores a moment in time, because it is a single number with no timezone or formatting attached.

Discord takes that number and formats it per reader. The tag <t:1785760200:F> is just "the 1,785,508,200th second after the epoch, shown the long way".

Yes, indirectly. Every Discord ID (messages, users, channels, servers) is a snowflake with the creation time baked in. Take the ID, shift it right 22 bits, and add Discord's epoch of 1420070400000 to get milliseconds, then divide by 1000 for a timestamp you can paste into a tag.