Input
Output
Formatted result will be displayed here
Turning a date into epoch time means computing how many seconds passed from 1970-01-01 UTC until that moment. The tool accepts ISO 8601 strings, common human formats, and individual year-month-day-hour-minute-second inputs, then emits both seconds and milliseconds. You can pick UTC or your local zone for the source interpretation, which matters because a bare date string is inherently ambiguous about its offset.
Create a reproducible epoch value for a migration script so tests do not drift every time someone reruns the seed.
Add a number of seconds to now_epoch and get the correct expires_at value for a cache entry or a JWT.
Pick a date in a calendar and get the epoch value a scheduler expects without guessing time zones.
Cloud storage presigned URLs expect epoch seconds for the expiry. Convert a human date to avoid off-by-one-hour mistakes.
ISO 8601, RFC 2822, and most common slash and dash formats. When in doubt, use ISO with an explicit offset for unambiguous results.
A bare date without offset is interpreted as local by default to match the browser Date constructor. Append Z or an offset to force UTC.
Yes. Both forms are shown so you can paste straight into whichever consumer you are targeting.
Fractional seconds feed into the millisecond output. The seconds output is truncated to whole seconds like most Unix APIs expect.