Epoch to date
1767225600 -> 2026-01-01 00:00:00 UTC
Use this when a log, API response, database row, or shell command gives you a 10-digit Unix timestamp.
Epoch date answer
1767225600 = January 1, 2026 00:00:00 UTC
The Unix timestamp 1767225600 converts to January 1, 2026 at 00:00:00 UTC. It is the first second of 2026 in Coordinated Universal Time, so it is a useful boundary value when checking epoch dates, API timestamps, and database cutoffs.
Keep the unit clear: 1767225600 is seconds. If your tool expects milliseconds, use 1767225600000 for the same instant.
Exact conversion
- Unix seconds
1767225600- UTC date and time
January 1, 2026 00:00:00 UTC- ISO 8601 UTC
2026-01-01T00:00:00.000Z- Unix milliseconds
1767225600000- Weekday
Thursday- Boundary meaning
First second of 2026 in UTC
How to confirm the timestamp
Paste 1767225600 into the Unix timestamp to date converter or the main epoch converter. The UTC result should read 2026-01-01 00:00:00 UTC.
For the reverse check, convert January 1, 2026 00:00:00 UTC back to epoch seconds. The result should be 1767225600. A different local calendar date usually means the display timezone is not set to UTC.
Date to epoch
2026-01-01 00:00:00 UTC -> 1767225600
Use this when you need the UTC midnight cutoff for filters, scheduled jobs, fixtures, or analytics windows.
Milliseconds
1767225600000 -> 2026-01-01T00:00:00.000Z
Use the 13-digit value for JavaScript Date, browser APIs, and systems that store Unix time in milliseconds.
Use 1767225600 safely
- For SQL or analytics cutoffs, compare UTC timestamps against
1767225600. - For JavaScript, pass
1767225600000intonew Date(). - For ISO output, expect
2026-01-01T00:00:00.000Z. - For local displays, compare the timezone label before treating the visible date as a mismatch.
Related conversions
See the shorter Jan 1 2026 00:00:00 UTC reference, the broader start of 2026 epoch guide, or the epoch to date converter guide.
FAQ
What is 1767225600 as a date?
1767225600 is January 1, 2026 at 00:00:00 UTC. It is a Unix timestamp in seconds.
Is 1767225600 exactly January 1 2026 00:00:00 UTC?
Yes. The exact UTC date-time is 2026-01-01 00:00:00 UTC, which is also 2026-01-01T00:00:00.000Z.
What is the epoch millisecond value for January 1 2026 00:00:00 UTC?
The millisecond timestamp is 1767225600000. It represents the same instant as 1767225600 seconds.
Why can the local date show December 31 2025?
The timestamp is fixed in UTC. In timezones west of UTC, the same instant can display as the evening of December 31, 2025 locally.