Free · No account · Works in your browser

Discord Timestamp

Discord timestamp codes (R / t / T / d / D / f / F)

Discord Timestamp

Enter values below, then calculate.

Unix Timestamp Epoch seconds ↔ human-readable date Converters Unix, Excel, FILETIME, ISO 8601, and calendar converters FILETIME Converter Windows FILETIME / LDAP timestamp converter Excel Date Converter Excel serial date \u2194 calendar date ISO 8601 Converter ISO 8601 and RFC 2822 date formats Year 2038 Problem Y2038 epoch overflow explained with converter Roman Numeral Date Convert years and dates to Roman numerals Cron Calculator Next run times from a cron expression LDAP Timestamp Active Directory LDAP / FILETIME converter UUID Timestamp Extract time from UUID version 1 Batch Timestamp Converter Convert many Unix timestamps at once Hex Timestamp Converter Hexadecimal Unix timestamp converter

Generate Discord timestamp codes that render in each reader’s local clock. Paste Unix seconds, a Discord <t:…> token, or pick a calendar date to copy Relative, short, and long formats for 2026 announcements.

What Discord timestamps solve

Discord stores message times in UTC, but members read times in their own locales. Hard-coding “3 PM EST” in a post forces every reader to convert. Discord’s dynamic timestamp markup solves that by embedding a Unix second and a display style so the client formats the moment locally.

The markup looks like <t:1704067200:F>. The number is seconds since 1970-01-01 UTC. The trailing letter chooses the style Discord should render: relative (“in 2 hours”), short time, long time, short date, long date, or combined date and time variants.

This converter exists so you can build those tokens without leaving the browser. Paste an epoch, decode an existing token, or start from a calendar date when you are planning events for 2026.

How to use this tool

Enter Unix seconds in the value field, paste a full Discord token such as <t:1704067200:R>, or choose a calendar date. Convert to see every style letter with copy-ready markup. Prefer seconds rather than milliseconds; if you paste a 13-digit value, the tool treats it as milliseconds and divides by 1,000.

Use Relative (R) for countdowns and reminders. Use Long date/time (F) for launches and meetings. Short styles keep chat compact when the date is already clear from context. Always preview in a Discord sandbox channel before pinning a public announcement.

Related converters on this site include the Unix timestamp page for epoch math, ISO 8601 for interchange strings, and the countdown creator when you need a full-page live timer instead of chat markup.

Styles explained

R shows a relative phrase that updates as time passes. t and T are short and long times of day. d and D are short and long calendar dates. f and F combine date and time at two levels of detail. Pick one style per mention; mixing several styles for the same instant is usually noise.

Discord evaluates the Unix second in UTC, then formats for the viewer. Two people reading the same token see different clock faces but the same underlying moment. That is intentional and preferable for multi-region communities.

If a token looks wrong, check whether you used milliseconds by mistake, whether the date was noon local versus UTC midnight, and whether daylight saving changes shifted the civil clock in your region around the target day in 2026.

Workflow tips

For recurring weekly events, generate a fresh token each week rather than reusing an old Relative stamp that already passed. For evergreen docs, prefer absolute F/D styles so archived messages stay readable years later.

Keep a spreadsheet column of Unix seconds if you schedule many drops; convert in batch mentally by testing one row here first. When integrating bots, have the bot emit Discord tokens server-side from a true UTC Instant rather than from a floating local string.

Do not use Discord timestamps as a legal clock for contracts. They are a chat convenience. For contracts and logs, store ISO 8601 with offsets or Unix seconds in your own systems and only render Discord markup for human announcement channels.

Related tools on Make a Calendar

Practical tips for 2026

Bookmark this page for recurring work in 2026. Prefer relative links when you share results inside Make a Calendar so hub navigation stays consistent. Recheck edge cases around midnight, daylight saving transitions, and leap days whenever your workflow crosses those boundaries. Keep a short note of the inputs you used so teammates can reproduce the same conversion later.

When you compare outputs with another system, align time zones first, then units (seconds versus milliseconds), then calendar rules. Small mismatches usually come from UTC versus local interpretation rather than from the math itself. Use the related tools below when you need a neighboring calculator instead of forcing one page to do every job.

Frequently asked questions

What is a Discord timestamp code?

It is markup like that Discord renders as a localized date or relative phrase for each reader. The number is Unix seconds UTC; the letter selects the display style.

Which style should I use for event announcements?

Use F or f for absolute date and time so archived messages stay clear. Use R when you want a live “in 3 hours” phrase that updates until the moment passes.

Seconds or milliseconds?

Discord expects Unix seconds. Thirteen-digit millisecond values will look centuries off if you paste them raw. This tool auto-detects long digit strings and converts them down to seconds.

Can I paste an existing Discord token?

Yes. Paste the full string to decode the Unix second and regenerate every style letter for copy.

Do timestamps respect time zones?

Yes. Discord stores UTC and formats for each member’s client locale, so teammates see their local wall clock for the same instant.

Is conversion private?

Conversion runs in your browser for ordinary use. You are not required to upload chat history to generate markup for 2026 announcements.

Processing, please wait...