Unix timestamp to Discord timestamp
A unix timestamp discord workflow is simple: take seconds since epoch, wrap them in a Discord tag, and pick a format letter. This guide covers the conversion pitfalls bots and spreadsheets usually hit.
Prefer a visual picker? Use the Discord timestamp generator — it shows Unix seconds for the moment you select and copies full tags for you.
The conversion formula
Discord expects seconds, not milliseconds. If your system gives
1730000000000, divide by 1,000 to get 1730000000. Then
build:
<t:1730000000:f>
Replace f with any style from the Discord timestamp formats reference
(t T d D f F R).
Seconds vs milliseconds checklist
- Unix seconds today are around 1.7 billion (10 digits).
- Unix milliseconds are around 1.7 trillion (13 digits).
-
Pasting milliseconds into
<t:…>produces absurd far-future dates—always check the preview. - Negative values are valid for pre-1970 instants but rarely needed for community events.
From APIs and bots
Many Discord bots already schedule with Unix seconds. When composing a message
string, interpolate the integer into the tag rather than formatting a locale string
yourself. That keeps every member’s client responsible for localization. For
countdowns specifically, style R is covered in Discord relative timestamp.
ZenlyTime’s developer section also prints ISO 8601 and small language snippets so you can assert that your bot’s epoch matches the chat tag you are about to send.
Verify before you announce
- Confirm units (seconds).
- Paste the tag into a private Discord channel.
- Hover the rendered time and compare with your intended zone.
- Swap style letters without changing the Unix value if the wording is wrong.