Date & Time Format Converter
Find dates and times inside notes, email, logs, or pasted spreadsheets, then normalize their format and time zone.
Calculation and conversion of the text and files you enter happen in your browser, and the tool does not send your original input or results to a server. For traffic related to visit statistics and ads, see the privacy policy.
How to use it
- Paste notes, email, logs, or spreadsheet cells into Source text. Recognized dates and times are highlighted immediately below the input.
- Check the numeric date order, the reference year for dates without a year, and the input zone for times without a zone. Yellow marks need your review.
- Choose an output format and zone, then copy the result. Use Matches only to extract one normalized value per line.
Examples
Normalize a mixed-format meeting note
Turn 2026-10-03T05:00:00Z, Oct 3, 2026 2:00 PM, and Korean-style dates into one consistent format.
- Input
Seoul 2026-10-03T05:00:00Z / follow-up Oct 4, 2026 2:30 PM
- Result
Seoul 2026-10-03 05:00 / follow-up 2026-10-04 14:30
Compare logs from different time zones
Convert 14:30 KST and 2pm EST to the same output offset before comparing event order.
Details
This tool scans the text for supported date and time shapes instead of treating the entire input as a date. Characters, spaces, and line breaks between matches remain unchanged. An explicit ISO 8601 or RFC 2822 offset, or an abbreviation such as KST or EST, takes priority. Otherwise, the selected input time zone is used.
A numeric date such as 10/03/2026 can mean October 3 in month/day order or March 10 in day/month order. The converter marks it yellow and lets you choose. A missing year is filled from the reference year. A time with no date uses the current reference date so that it can still be converted between offsets.
Time-zone abbreviations are fixed offsets here: EST means UTC−5 while EDT means UTC−4. The converter does not infer historical or future daylight-saving rules for a city, so choose the exact abbreviation or verify the offset for regions that change clocks. To reduce false positives, Unix timestamps must be standalone 10-digit seconds or 13-digit milliseconds representing a date from 2000 through 2100. Version numbers, comma-formatted amounts, invalid calendar dates, and ordinary phone-number examples are ignored.
Frequently asked questions
Is my pasted text uploaded or saved?
No. Detection and conversion run in this browser tab. The input is not stored, sent to a server, or placed in the page URL.
Does 10/03/2026 mean October 3 or March 10?
Both interpretations are common. Select month/day or day/month under Numeric date order. These matches are included in the Needs review count.
What happens when a time has no time zone?
The selected input zone is applied. A date without a time starts at midnight in that zone; a time without a date uses the reference date.
Why are phone and version numbers left alone?
The parser checks separators and calendar ranges. Unix timestamps have strict digit and year limits, so 1.2.3, 10,000, and common mobile phone numbers are not treated as dates.
Which custom-format tokens can I use?
Use YYYY MM DD ddd HH hh mm ss A Z X x for year, month, day, weekday, 24-hour time, 12-hour time, minute, second, AM/PM, offset, Unix seconds, and Unix milliseconds.