This is your one-stop Discord timestamp cheat sheet — every format code, syntax template, and quick reference you need without having to search again. Bookmark it, screenshot it, share it in your server resource channel. Everything here is copy-ready and accurate across all Discord platforms including desktop app, web browser, mobile iOS and Android.
Quick Reference — All 7 Discord Timestamp Format Codes
All Discord timestamps use this syntax: <t:UNIX_TIMESTAMP:FORMAT_LETTER> where UNIX_TIMESTAMP is the number of seconds since January 1 1970 and FORMAT_LETTER is one of 7 single-letter format codes.
| Format Name | Code | Example Output (12hr) | Example Output (24hr) | Best For |
|---|---|---|---|---|
| Short Time | <t:UNIX:t> | 9:01 AM | 09:01 | Quick time references |
| Long Time | <t:UNIX:T> | 9:01:00 AM | 09:01:00 | When seconds matter |
| Short Date | <t:UNIX:d> | 11/28/2018 | 28/11/2018 | Compact date only |
| Long Date | <t:UNIX:D> | November 28, 2018 | 28 November 2018 | Formal date display |
| Short Date/Time | <t:UNIX:f> | November 28, 2018 9:01 AM | 28 November 2018 09:01 | Most common — events |
| Long Date/Time | <t:UNIX:F> | Wednesday, November 28, 2018 9:01 AM | Wednesday, 28 November 2018 09:01 | Official announcements |
| Relative Time | <t:UNIX:R> | in 2 hours / 3 years ago | in 2 hours / 3 years ago | Countdowns and reminders |
Default format — if you omit the format letter entirely, <t:UNIX_TIMESTAMP> renders as Short Date/Time (f).
Copy-Ready Syntax Templates
Replace UNIX_TIMESTAMP with your actual Unix timestamp value generated from our tool. The Relative Time format (R) is especially popular in bot embed countdown fields — it stays accurate and updates automatically without the bot needing to edit the message. For deadline reminders, event announcements, and scheduled task notifications, R is the standard bot timestamp format.
Using Discord Timestamps on Mobile
All 7 Discord timestamp formats work identically on mobile iOS and Android — the conversion and rendering happens on Discord's platform, not on your device. The timestamp code you paste from our generator on desktop will display exactly the same way on mobile. The only difference is that on mobile you tap a rendered timestamp to see its full Long Date/Time tooltip, whereas on desktop you hover.
One mobile specific note: the custom date input and custom time input on some mobile browsers can behave differently from desktop — if you're generating timestamps on mobile, use our tool's separate inputs option if the combined date and time picker doesn't respond correctly on your mobile device.
Tracking Message History With Timestamps
Beyond scheduling, timestamps are valuable for tracking message history in busy channels. When a member references an event that happened last week, dropping a Short Date/Time (f) timestamp for that date gives every reader immediate context — they see exactly when it happened in their own local format without needing to know the original poster's time zone. This is particularly useful for community server moderation logs, collaborative project timelines, and any channel where when events occurred matters for managing conversations and tracking essential information.
Common Mistakes and How to Fix Them
Mistake 1 — Pasting inside backticks: The most visible mistake. If your message shows <t:1722495600:F> as literal text instead of a formatted date, you've wrapped it in backticks or a code block. Delete the backticks and re-paste as plain text.
Mistake 2 — Using milliseconds instead of seconds: A Unix timestamp from JavaScript's Date.now() returns 13 digits (milliseconds). Discord needs 10 digits (seconds). Divide by 1000 or use our generator which handles seconds vs milliseconds automatically.
Mistake 3 — Wrong format letter: Only t T d D f F R are valid. A typo like :G or :r (lowercase r works, uppercase R also works — both are valid for relative time) may break rendering. Use our generator to avoid manual syntax errors.
Mistake 4 — Spaces inside the code: <t: 1722495600 :F> with spaces breaks rendering. The code must be continuous with no spaces inside the angle brackets.
Mistake 5 — Wrong angle brackets: Using (t:1722495600:F) or [t:1722495600:F] instead of <t:1722495600:F> breaks everything. Must be < and > specifically.
Related Guides
- What Is a Discord Timestamp?
- Discord Timestamp Formats Explained
- How to Use Discord Timestamps
- Discord Timestamp Generator
Frequently Asked Questions
Ready to generate Discord timestamps?
Open the Generator