Seconds vs. milliseconds
Do not trim 13-digit values before converting. A value like 1767225600000 is already milliseconds and represents the same instant as 1767225600 seconds.
Epoch time converter
Use this page when a log, API response, JWT claim, SQL row, or browser event gives you epoch time and you need the readable date behind it. Paste Unix seconds or milliseconds below, or use the reverse converter when you need to turn a calendar date into epoch time.
Direct reference: 1767225600 is January 1, 2026 at 00:00:00 UTC. See the dedicated 1767225600 reference if you only need that boundary value.
The safest rule is to identify your starting value before converting. Existing Unix numbers belong in the Unix timestamp to date converter. Readable calendar times belong in the reverse date-to-epoch tool on this page.
| Search intent | Typical input | What to do |
|---|---|---|
| epoch to date / epoch time to date | 1767225600 or 1767225600000 | Paste the raw number into Timestamp to Date. Keep 13-digit values intact so milliseconds are detected correctly. |
| epoch date | A Unix value where the calendar day matters | Use UTC first, then compare local time. The same epoch can display as the previous evening in timezones west of UTC. |
| convert epoch | Either a raw epoch value or a readable date | Numbers go into Timestamp to Date. Calendar dates go into Date to Timestamp so you generate the Unix value instead of decoding one. |
| 1767225600 jan 1 2026 utc | 1767225600 | The direct answer is January 1, 2026 at 00:00:00 UTC. Use 1767225600000 when a JavaScript API expects milliseconds. |
Do not trim 13-digit values before converting. A value like 1767225600000 is already milliseconds and represents the same instant as 1767225600 seconds.
Epoch time itself is UTC. If a result looks one day early or late, switch timezone display before changing the raw timestamp. Compare with the current UTC timestamp.
For a longer walkthrough focused only on decoding values, use the convert epoch to date guide.
It converts between Unix epoch time and readable dates. If you paste a 10-digit value such as 1767225600, the result is a date. If you start with a calendar date, the result is epoch seconds and milliseconds.
Yes. Epoch time counts from January 1, 1970 at 00:00:00 UTC. Timezone changes only affect the displayed date and clock time, not the underlying timestamp.
A 10-digit modern value is usually seconds. A 13-digit modern value is usually milliseconds. JavaScript Date.now() returns milliseconds, while many APIs, databases, and shell tools use seconds.
1767225600 is January 1, 2026 at 00:00:00 UTC. The matching millisecond value is 1767225600000.
Related Tools
More free tools for developers debugging timestamps, schedules, and text changes.