Date to Epoch Converter
Paste or type a date — get the Unix timestamp instantly in every unit you might need.
What you can paste
Sometimes you have a date you can read — a deadline on a calendar, a value copied out of a spreadsheet, a string sitting in a log file or API response — and you need the Unix timestamp it corresponds to. This page goes the opposite direction from the main Epoch Converter: instead of starting from a number, you start from a date.
Type or paste it straight into the box above — there is no separate “convert” step. Standard date formats work out of the box: ISO 8601 and RFC 3339 (2026-03-15T14:30:00Z), SQL-style datetimes (2026-03-15 14:30:00), MongoDB'sISODate("…")wrapper, and named-month strings like “March 15, 2026”. If nothing happens, the most likely cause is an ambiguous numeric date (is 03/04/2026 March 4th or April 3rd?) — switch to ISO 8601 and it will always resolve correctly.
Every unit at once
Different stacks expect different units: JavaScript wants milliseconds, most databases store seconds, and .NET uses 100-nanosecond ticks. TimeTools shows them all together so you can copy the exact one your code needs.
Frequently asked questions
How do I convert a date to a Unix timestamp?
Paste or type a date into the box above — an ISO date, a SQL datetime, a named-month string like "March 15, 2026", or anything similar. TimeTools detects the format instantly and shows the Unix timestamp in seconds, milliseconds, ISO 8601, and .NET ticks. Click any row to copy it, or click Now to use the current moment.
What date formats can I paste?
ISO 8601 and RFC 3339 (2026-03-15T14:30:00Z), SQL-style datetimes (2026-03-15 14:30:00), MongoDB's ISODate("…") wrapper, and named-month strings such as "March 15, 2026" or "Mar 15 2026 14:30:00 GMT+0100". If you already have a Unix timestamp (a plain number), use the Epoch Converter instead — this page is for human-readable dates.
Why wasn't my date recognized?
The most common cause is a day/month order the parser can't disambiguate — 15/03/2026 isn't valid in the US month/day/year convention, so it's rejected rather than silently guessed wrong. Numeric day-month-year formats are inherently ambiguous across regions; use ISO 8601 (2026-03-15) to be unambiguous every time.
Can I convert a date in a specific time zone?
The Local time row uses your browser's time zone automatically. To see the same instant in other zones, use "Add time zone" below the results — added zones are saved and stay available across visits. If your input string itself includes an offset (e.g. +01:00 or Z), that offset is used to anchor the exact instant before any zone conversion.
What is the timestamp in seconds vs milliseconds?
Seconds is the classic Unix value (10 digits today); milliseconds multiplies it by 1000 (13 digits) and is what JavaScript's Date.now() returns. Both are shown side by side so you can copy whichever your system expects.
How is this different from the Epoch Converter?
Same output, opposite direction. The Epoch Converter takes a Unix timestamp and tells you the date; this page takes a human-readable date and tells you the Unix timestamp. Both show the full set of formats — UTC, local time, ISO 8601, RFC 3339, Unix seconds/ms, and .NET ticks.
Does my data leave the browser?
No. The conversion runs entirely in your browser using built-in JavaScript date APIs. Nothing you enter is sent to a server.