Settings
Result appears here after you select
{ } How to use
- Enter a date, date-time, or a Unix timestamp (seconds or milliseconds).
- Pick the target format — or leave it on "All formats" to see them all at once.
- The result updates as you change the format.
{ } How it works
Convert Between Date & Time Formats works on the text you provide. Adjust the options, then select Process ▸ and it runs entirely in your browser — nothing is uploaded to a server — then shows the result in the Output panel.
Inputs
- Date, date-time, or Unix timestamp — paste or type your input in the left panel (use Sample for an example)
- Target format — choose one — All formats, ISO 8601 (UTC), ISO date (YYYY-MM-DD), ISO date-time (YYYY-MM-DD HH:mm:ss), RFC 2822 / HTTP, Unix timestamp (seconds), Unix timestamp (milliseconds), US date (MM/DD/YYYY), European date (DD/MM/YYYY), Long date (Month D, YYYY), Time only (HH:mm:ss), Day of week, Day of year (default: All formats)
Output
TXT text — copy or download it from the Output panel.
{ } Common uses
- Turn a Unix timestamp from a log into something readable.
- Get the ISO 8601 form of a date written the American or European way.
- Find out what day of the week a date fell on.
{ } Limitations
- Everything is expressed in UTC, and an input without an offset is read as UTC. A timestamp that means 9am in Berlin is not shown as 9am here — Time Zone Converter is the tool for that.
- A bare number is treated as a Unix timestamp, and whether it is read as seconds or milliseconds is decided by its magnitude: 1e11 and above is taken as milliseconds. That is correct for every plausible modern date, but it is a heuristic rather than a declaration.
- The twelve target formats are fixed. There is no custom pattern, so an arbitrary layout cannot be requested.
{ } FAQ
Is my data uploaded to a server?
No. Everything runs locally in your browser — your files never leave your device.
Can I process more than one file at once?
This tool works on one input at a time.
Is this tool free?
Yes — it’s completely free and needs no sign-up.
Which format should I use for an API or a database?
ISO 8601 in UTC, almost always. It sorts correctly as plain text, it is unambiguous about the offset, and every language parses it. The US and European numeric forms are the ones to avoid in stored data, because 03/04 is two different dates depending on who reads it.