Design Date and Time Display
Content & UX Writing · microcopy, internationalization, tables
Updated 2026-07-28
- Choose the format from what the user is doing. Relative time is best for recent activity, absolute dates are best for records, and both together are best for anything auditable.
- Stop relative time before it stops being useful. "3 minutes ago" is clear, "14 months ago" is not, so switch to a real date after about a week.
- Never write a numeric date in an ambiguous order. The same three numbers mean two different days depending on the reader, so include the month as a word wherever space allows.
- Show the timezone whenever the exact moment matters. A meeting, a deadline, a log entry, or a scheduled send needs to say which clock it is on.
- Say whose timezone it is. "3:00 PM your time" removes the arithmetic that users otherwise do wrong.
- Keep the sortable form in dense tables. A fixed-width, year-first format lines up in a column and sorts correctly, while a friendly format does neither.
- Give the full value on hover or in the detail view. Relative time is a summary, and users occasionally need the exact timestamp behind it.
- Handle the awkward cases deliberately:
- Today, yesterday, and tomorrow, which read better as words.
- Ranges within one month, where repeating the month is noise.
- Times that cross midnight in another timezone.
- Dates that have not happened yet, which need a different tense.
Dates are read at a glance and acted on immediately, so an ambiguous one causes a real mistake rather than a moment of confusion.
Related guides