Account

What new tool do you want?

Social & Creators

Discord Timestamp & Text Formatter

Generate Discord timestamps (<t:…:F>) that show in each reader's time zone, and a cheat sheet for Discord, WhatsApp and Telegram text formatting.

How to use

  1. 1Pick a date and time (in your time zone).
  2. 2Copy the timestamp code for the style you want and paste it into Discord.

How it's calculated

Discord timestamps use Unix seconds: <t:SECONDS:STYLE>, where style is t, T, d, D, f, F or R (relative). Each reader sees it in their own time zone.

Frequently asked questions

Why use Discord timestamps?

Everyone sees the time converted to their own time zone — no more 'is that 8pm my time or yours?'.

What does :R do?

It shows a relative time like 'in 3 hours' or '2 days ago', updating automatically.

How do I make bold text in WhatsApp?

Wrap it in asterisks: *bold*. Italic uses _underscores_, strikethrough ~tildes~ and monospace ```three backticks```.

Why Discord timestamps solve a problem links and plain text can't

Writing '8pm EST' in a Discord message means every reader has to do their own mental timezone math, and a surprising number simply get it wrong under time pressure — Discord's timestamp syntax instead encodes the moment as a single Unix timestamp (seconds since 1970), which Discord's client then renders in each individual reader's own local timezone setting automatically. The same <t:1783209600:F> code displays as evening in New York, the middle of the night in Tokyo, and whatever the correct local equivalent is everywhere else — one code, correct everywhere.

Worked example: Discord Timestamp & Text Formatter

Setting the date to July 4, 2026, time to 20:00, with a UTC offset of -4 (Eastern Daylight Time) computes a Unix timestamp of 1783209600 — the calculation subtracts the offset in milliseconds from the UTC-interpreted date/time before converting to seconds, so entering the correct offset for wherever you are is what makes the final timestamp accurate for everyone else. That same number feeds every style variant: <t:1783209600:F> for the full date and time, <t:1783209600:R> for a self-updating relative time like 'in 3 days', and so on — one computed value, six different display formats.

Why getting your own UTC offset wrong breaks the timestamp for everyone, not just you

Because the whole point of this timestamp is that it's calculated once from your stated local time and then rendered correctly for every reader regardless of their own timezone, an incorrect offset entered here doesn't just mislead you — it bakes a wrong absolute moment into the timestamp that every single reader sees converted to their own timezone equally incorrectly. Double-checking your own offset (accounting for daylight saving time, which shifts most offsets by an hour for part of the year) matters more here than in almost any other time-related input, since the error propagates to every viewer rather than staying local to the person who made it.

Half-hour offsets work, and the seconds are cut off

The offset box steps in half hours, so I can enter 5.5 for India or -3.5 for Newfoundland instead of pretending every zone is a whole hour. That offset is subtracted from the date and time I typed before the result is turned into a whole number of seconds. The fraction of a second is dropped, not rounded, so what I copy is always an integer. The page also always prints a formatting cheat sheet for Discord, WhatsApp, and Telegram under the codes, even when I only came for the timestamp. The styles I actually get are the full date, the short date and time, the relative form, the time alone, and the date alone, plus the raw second count.

Related tools

More: Social & Creators