API fixture
1767225600
Use when the field name expects Unix seconds.
Epoch date answer
The Unix timestamp 1767225600 equals Thursday, January 1, 2026 at 00:00:00 UTC. It is a 10-digit epoch-seconds value. The matching 13-digit millisecond value is 1767225600000.
Use this page when you need the direct UTC answer, then open the Unix timestamp to date converter if you need to check the same value in another timezone.
1767225600Unix epoch secondsThursday, January 1, 2026 at 00:00:00 UTC2026-01-01 00:00:00 UTC2026-01-01T00:00:00.000Z17672256000001767225600
Use when the field name expects Unix seconds.
1767225600000
Use when passing the instant into new Date(...).
2026-01-01T00:00:00.000Z
Use when a human-readable UTC timestamp is safer than a raw number.
The UTC answer never changes: 2026-01-01 00:00:00 UTC. Local time can look different because timezone conversion changes the displayed clock. In America/Los_Angeles, the same instant is the afternoon of December 31, 2025; in UTC, it is the first second of January 1, 2026.
For a broader walkthrough, compare this answer with the exact 00:00:00 UTC reference and the start of 2026 timestamp page.
1767225600 is seconds, so do not pass it directly to JavaScript Date.1767225600000 is milliseconds, so do not multiply it again.2026-01-01T00:00:00.000Z is the ISO form for systems that prefer strings.Yes. 1767225600 is the Unix seconds timestamp for January 1, 2026 at exactly 00:00:00 UTC.
As an epoch date, 1767225600 converts to Thursday, January 1, 2026 in UTC.
Use 1767225600 for epoch seconds and 1767225600000 for epoch milliseconds. They represent the same instant.
A local timezone west of UTC can display the same instant on December 31, 2025. The UTC conversion is still January 1, 2026.
Related Tools
More free tools for developers debugging timestamps, schedules, and text changes.