Date To Unix Timestamp
Calculator
Results
- Seconds since the Unix epoch
- 1,749,997,800
- Milliseconds since the Unix epoch
- 1,749,997,800,000
- Days since the Unix epoch
- 20,254
- Minutes since the Unix epoch
- 29,166,630
Time and date results
| Seconds since the Unix epoch | 1,749,997,800 |
| Milliseconds since the Unix epoch | 1,749,997,800,000 |
| Days since the Unix epoch | 20,254 |
| Minutes since the Unix epoch | 29,166,630 |
formula-map diagram
- Seconds since the Unix epoch
- 1,749,997,800
- Milliseconds since the Unix epoch
- 1,749,997,800,000
- Days since the Unix epoch
- 20,254
- Minutes since the Unix epoch
- 29,166,630
Time relationship
Formula
epoch seconds = (UTC date/time − 1970-01-01T00:00:00Z) in seconds= 1749997800
Note
This is a simplified model: it uses fixed conversions (60 minutes per hour, 24 hours per day, 7 days per week, 365 days per year) and ignores leap years, daylight saving changes, public holidays and irregular month lengths. Check the result against a real calendar before relying on it.
Example: with the default inputs, calculator.timedate.epoch_seconds is 1749997800.
More in Time and date
See all →Frequently asked questions
How do I convert a date to a Unix timestamp?+
Enter the year, month, day, hour and minute. The calculator computes the seconds elapsed between 1970-01-01 00:00:00 UTC and that moment.
Is the time I enter local or UTC?+
UTC. The hour field is labeled UTC, so convert your local time to UTC first if you need a timestamp for a local moment.
What other values does it return?+
Besides epoch seconds, it returns epoch milliseconds, whole days since the epoch, and the timestamp expressed in minutes.
Is there a field for seconds?+
No. The inputs stop at the minute, so the result always falls on a whole minute.
Why can the result be negative?+
Dates before 1970-01-01 00:00 UTC come before the epoch, so their count of seconds is negative.