Back to Tools

Timestamp Converter

Convert Human Readable Dates to Unix Timestamps instantly.

Input Data

From a calendar date to a Unix timestamp

APIs, databases and log files often store time as the number of seconds since 1 January 1970 UTC. When you need to put a specific date into a query, a config file or a test fixture, you have to turn it into that number. This tool does that direction of the conversion: you enter a human-readable date, and it returns the timestamp in both seconds and milliseconds.

How to convert a date

  1. Type a date into the Input Data box, for example 2023-12-31 23:59:00. Sample fills in 2025-01-01 12:00:00 for you.
  2. Click Process Now.
  3. The results panel shows Seconds and Milliseconds as large, easily selectable numbers. A line above them says how the date was parsed, written as a UTC string.
  4. Use Copy for the text or Download to save result.txt. Clear resets the box.

Which formats work, and which time zone applies

The date is read by your browser's built-in date parser, so anything it understands is accepted: ISO strings like 2025-03-15T08:30:00Z, and forms such as December 31, 2023 23:59:00 or 2023/12/31. Behaviour differs between browsers for unusual layouts, so the ISO style is the most dependable choice.

Time zone matters. A value that includes Z or an offset like +05:30 is exact. A date and time with no zone, such as the 2025-01-01 12:00:00 sample, is treated as local time on your device, so the timestamp will differ depending on where you are. Look at the "Parsed as" UTC line to see what was actually used. A date-only ISO string like 2025-01-01 is normally read as midnight UTC.

Everyday uses

  • Setting an expiry or start time in a JWT, cache header or scheduled job.
  • Building a range filter for a database or analytics query.
  • Producing a fixed timestamp for a unit test.
  • Checking how a log entry's date translates to the epoch value in your data.

Details worth knowing

The seconds figure is rounded down from the milliseconds, so fractional parts are dropped. Dates before 1970 return negative numbers, which is correct for Unix time. Leap seconds are not counted, as in standard Unix time.

If you see a message saying the format is invalid, your browser could not read the date; switch to the ISO layout, and note that a blank box gives a separate prompt to enter a date. To go the other way, from a number back to a date, the companion Unix Time Converter handles that.


Related Tools

Related Tools


Frequently Asked Questions

Does the tool return seconds or milliseconds?
Both. The result panel lists Seconds and Milliseconds separately. Many backends and languages use seconds, while JavaScript and some APIs use milliseconds, so copy the one that matches what your system expects.
Which time zone is used for my date?
If you include Z or an offset such as +02:00, that is used. If you write a date and time with no zone, your device's local time zone is assumed. The 'Parsed as' line shows the exact UTC moment that was used.
What date formats can I enter?
Anything your browser's date parser accepts. ISO 8601 such as 2025-01-01T12:00:00Z is the most reliable; common forms like 2023/12/31 or 'December 31, 2023' usually work too, though parsing of unusual layouts can vary between browsers.
Can it handle dates before 1970?
Yes. A date earlier than 1 January 1970 UTC produces a negative timestamp, which is how Unix time represents moments before the epoch. Treat the number as-is when pasting it into systems that support negative values.
How do I convert a timestamp back into a date?
Use the Unix Time Converter on this site. You paste the number there and it shows UTC, local and ISO 8601 versions. This page only goes from a written date to the numeric timestamp.
Support Chat
We typically reply within minutes

Hello! 👋 Before we start, please tell us your name.