Discord Relative Timestamp Generator

What "relative" means here

Most timestamp formats print a fixed point in time — a date, a clock time, or both. The relative format (format letter R) is different: it prints a phrase describing the gap between now and the timestamp, like "in 45 minutes" or "2 hours ago." Because Discord's client recomputes that phrase every time the message is rendered, it never goes stale the way a hand-typed sentence would.

How the phrase changes over time

Set a moment 90 minutes in the future and the timestamp will read "in an hour" shortly after you post it, "in 40 minutes" a little later, "in a few seconds" as it approaches, and then flip to "a few seconds ago," "an hour ago," and so on once the moment has passed. This makes it well suited to anything with a lifespan — a limited-time offer, a status check-in, or "last seen" style messages.

Relative time reads differently depending on distance

Discord scales the phrasing to the size of the gap: timestamps a few seconds away read in seconds, ones a few hours away read in hours, and ones weeks or months away round to the nearest larger unit. That's a deliberate readability choice on Discord's part, not something this generator controls — the same underlying Unix time will always produce the same relative phrase for a given reader's clock.

Related formats

Looking for the giveaway/raid-timer framing of this exact format code, seethe countdown timestamp page andgiveaway & raid timers. For a side-by-side look at all seven Discord format codes, see the format reference.

Relative time vs. typing it by hand

Typing "in 2 hours" directly into a message feels simpler than generating a code, right up until someone reads it later. A hand-typed phrase is only accurate at the moment it was written — an hour after posting, "in 2 hours" is now wrong by an hour, and there's no way to fix that without re-editing the message. A relative timestamp sidesteps the problem entirely: you write it once, and it's correct for every reader at every point in time, including days or weeks later when someone scrolls back through channel history and needs to know how long ago something actually happened.

A common mix-up: past vs. future

Because the same format code handles both directions automatically, it's easy to set a time in the wrong direction without noticing — picking yesterday's date when you meant tomorrow, for instance, quietly turns an intended "in 3 hours" into "21 hours ago," with no error or warning from the generator. The live preview above always shows exactly what the phrase will read as right now, so a quick glance before copying catches a flipped date instantly.

Relative time in message history

One side effect worth knowing: a relative timestamp keeps changing even in old messages. Scroll back through a channel from months ago and a timestamp originally posted as "in 2 days" will now correctly read as "2 months ago" — which is usually exactly what you want for historical context, but is worth remembering if you were expecting a message's timestamp text to match a screenshot taken right after it was posted.