Converting Between Date Formats
Dates appear in dozens of formats across systems. The Date Format Converter unifies them: paste any recognizable date in, pick or type the output pattern, and see the result instantly.
Inputs It Understands
This tool auto-detects:
- ISO 8601:
2026-04-14T12:00:00Z,2026-04-14,2026-04-14 15:30 - RFC 2822 / HTTP:
Tue, 14 Apr 2026 12:00:00 GMT - Unix timestamps: seconds (
1776124800) or milliseconds (1776124800000) — the detector switches mode automatically using the magnitude of the number. - Human-readable strings that the browser's native
Dateconstructor can parse:April 14, 2026 12:00,04/14/2026.
The Format Tokens
Format patterns use a lightweight token syntax similar to Moment.js and dayjs:
| Token | Meaning | Example |
|---|---|---|
YYYY / YY | 4- or 2-digit year | 2026 / 26 |
MMMM / MMM / MM / M | Month name / short / padded / plain | April / Apr / 04 / 4 |
DD / D | Padded / plain day | 14 / 14 |
dddd / ddd | Weekday long / short | Tuesday / Tue |
HH / H | 24-hour padded / plain | 09 / 9 |
hh / h | 12-hour padded / plain | 09 / 9 |
mm / m | Minutes padded / plain | 05 / 5 |
ss / s | Seconds padded / plain | 07 / 7 |
A / a | AM/PM or am/pm | PM / pm |
Any other characters pass through literally — so YYYY-MM-DDTHH:mm:ss yields 2026-04-14T12:00:00, and dddd, MMMM D yields Tuesday, April 14.
Why Not Just Intl?
The built-in Intl.DateTimeFormat is excellent for locale-aware display, but it doesn't support arbitrary token patterns. When you need a very specific output — a legacy log format, a custom filename prefix, a column header — a token-based converter is faster than building it by hand.
Presets
The quick presets cover the most common cases: ISO 8601 for computing, US (MM/DD/YYYY) and EU (DD.MM.YYYY) for regional documents, RFC-style for email headers, and 12h clock for user-facing UIs. Click a preset and the pattern populates immediately.
Tiny Online Tools






