Dates appear everywhere — record rows, reports, exports, emails. Different locales have different conventions; choosing the right format matters for clarity and avoiding ambiguity (08/09/2025 means very different things in the US vs UK).
Format Categories
- Short date: Compact for table cells, e.g. 13/05/2026.
- Long date: Friendly for content, e.g. 13 May 2026.
- Short datetime: 13/05/2026 14:32.
- Long datetime: 13 May 2026, 2:32 pm.
- Relative: “2 hours ago”, “Yesterday”, “Last week”.
- ISO: 2026-05-13 — universally unambiguous, computer-friendly.
Recommended by Locale
- UK / Europe: DD/MM/YYYY (or D MMM YYYY for long).
- US: MM/DD/YYYY.
- ISO standard: YYYY-MM-DD (best for technical / audit views).
- East Asia: YYYY-MM-DD or YYYY年MM月DD日.
Where the Format Is Applied
- Table column cells.
- Form input displays (the input parser still accepts other formats).
- Report headers and labels.
- Email templates (where tokens use the format helper).
- Document templates (PDF outputs).
- Exports (CSV, Excel — though always-recommended to use ISO for exports).
Worked Examples
- UK SaaS: Short DD/MM/YYYY, long D MMM YYYY, datetime DD/MM/YYYY HH:mm.
- US enterprise: Short MM/DD/YYYY, long MMM D YYYY, datetime MM/DD/YYYY h:mm a.
- International audit logs: Force ISO (YYYY-MM-DD HH:mm:ss) regardless of user locale — avoids ambiguity in compliance reviews.
- Multi-tenant SaaS: Each tenant sets their own default; users can override.