Date to Epoch Converter

You need an epoch value — for a JWT expiry claim, a created_at column, a cron-adjacent script, an API filter — and all you have is a human date. Type it as ISO 8601 or pick it from the date-time input above and the unix timestamp in seconds and milliseconds appears immediately, ready to copy.

Dates entered without a timezone offset are interpreted as UTC, not your local browser time — the one behavior that silently ruins epoch values produced by other converters. Conversion runs locally in your browser.

FAQ

Should I store epoch in seconds or milliseconds?

Follow whatever your system already expects — seconds is the classic unix convention (10 digits today), milliseconds is common in JavaScript and JVM stacks (13 digits). Mixing them up is the single most common epoch bug.

What happens if I don't specify a timezone?

This page assumes UTC, which is the only safe default: a bare "2024-01-01T10:00" means 10:00 UTC. Add an explicit offset like +02:00 if you mean a local wall-clock time.

How far in the future or past can I go?

Anything JavaScript's Date can represent — roughly ±100 million days around the epoch, including pre-1970 dates that produce negative timestamps.