Leap Day to Unix Timestamp – Convert February 29

Local only

Demonstrate valid leap-day parsing and contrast it with impossible calendar dates.

Multi-row timestamp converter

Compare timestamps and ISO 8601 dates. Inputs without an offset use UTC.

Row 1Date -> Timestamp
1709164800
Milliseconds: 1709164800000Timezone: UTC (Z)ISO: 2024-02-29T00:00:00.000Z

Leap-year date parsing

Can February 29 be converted to a Unix timestamp?

February 29 is valid only in a leap year. VetaTool validates the calendar fields before conversion, so 2024-02-29 converts normally while impossible dates are rejected. This tool is free to use. No account or payment is required.

Last updated

What you can do here

  • Unix seconds and milliseconds conversion
  • ISO 8601 parsing
  • Explicit timezone interpretation
  • Fractional and negative Unix timestamps
  • Browser-local processing

Steps

  1. Enter the February 29 ISO value.
  2. Confirm the normalized ISO value keeps February 29.
  3. Compare with the invalid-date page if the year is not a leap year.

Calendar validity is checked before timestamp conversion

The parser reconstructs the UTC calendar components and rejects dates that JavaScript might otherwise normalize into another day or month.

2024 leap-day example

2024 is a leap year, so February 29 is accepted.

ISO date

2024-02-29T00:00:00Z

Unix seconds

1709164800

Common questions

Frequently asked questions

Would 2023-02-29 work?

No. 2023 is not a leap year, so February 29 is not a valid calendar date.

Is leap-day handling timezone dependent here?

The example explicitly uses Z, so the instant is UTC.

Recommended next steps

Invalid Date to TimestampDetect impossible calendar dates instead of relying on rollover behavior.Date Only to Unix TimestampConvert a YYYY-MM-DD calendar date from UTC midnight to Unix time.Unix Timestamp Converter OnlineConvert Unix seconds, milliseconds, ISO 8601 dates, and timezone-aware values locally.

Debugging a specific Timestamp issue? Browse Timestamp troubleshooting.