Unix Timestamp Converter
Convert Unix epoch seconds or milliseconds to readable UTC/local dates, or convert a local date back to epoch.
Right now
updates every second
Reading this as seconds. A 13-digit number is milliseconds.
All conversions run in your browser. Timestamps and dates are not sent to any server.
What is a Unix timestamp?
A Unix timestamp (epoch time) is an integer count from 1970-01-01T00:00:00Z. Most systems store this as seconds or milliseconds and use it in logs, databases, APIs, and token claims.
The timestamp value represents one exact instant globally. What changes across regions is only the formatted display, such as UTC output versus your local timezone string.
Why use an epoch converter?
Raw epoch values are hard to read during incident debugging. Converting them quickly helps map events to deployments, alerts, cron jobs, and user activity timelines.
The reverse conversion is just as useful: pick a local date/time and copy epoch seconds or milliseconds for API requests, test fixtures, and database filters.
How to convert Unix time in this tool
Paste a number or pick a local date. Both fields stay on the same moment. The list shows Unix seconds, ISO 8601, a UTC string, a local string, and a relative time. On paste, values below 1e12 are treated as seconds and larger absolute values as milliseconds.
Now fills the current time and keeps it moving until you edit a field. The date picker sets the minute, so seconds stay 00 unless you type them in the timestamp.
All parsing and formatting run in-browser with JavaScript Date APIs. Your inputs are not sent to a server.
Seconds vs milliseconds (quick checks)
10-digit values are typically Unix seconds, while 13-digit values are usually milliseconds. Mixing them shifts dates by about 1,000x and is one of the most common timestamp debugging mistakes.
Epoch zero is 1970-01-01T00:00:00.000Z and negative values represent dates before 1970. JavaScript Date.now() returns milliseconds, while many server-side APIs return seconds.
Year 2038 and privacy notes
The Year 2038 issue affects systems using signed 32-bit seconds. Modern stacks usually avoid this with wider integer types, but older software may still require checks.
This converter is browser-only. Timestamps and date inputs stay on your device and are not stored after you leave the page.
Frequently asked questions
How do I convert a Unix timestamp to a readable date format?
Paste the value into Unix timestamp. A number under 1,000,000,000,000 is read as seconds, and a larger number as milliseconds. The list shows ISO 8601, a UTC string, a local string, and a relative time. You can switch units manually.
What is the difference between Unix seconds and milliseconds?
Both represent elapsed time since the Unix epoch, but in different units. Seconds are usually 10 digits and milliseconds are usually 13 digits. If you interpret milliseconds as seconds (or the reverse), the date shifts by roughly 1,000x.
Are Unix timestamps always in UTC?
A Unix timestamp is a timezone-agnostic instant counted from the UTC epoch. The number is global; only the display layer changes between UTC and local timezone formats.
How do I get the current Unix timestamp quickly?
Use the Now button in this converter to fill current values immediately. In code, JavaScript uses `Math.floor(Date.now() / 1000)` for seconds and `Date.now()` for milliseconds; many backend runtimes expose similar helpers.
How do I convert a date back to epoch seconds or milliseconds?
Set Local date and time. Unix seconds show in the timestamp field and in the list. Switch the unit to Milliseconds to copy the 13-digit value. The date picker sets the minute, so seconds are 00 unless you type them in the timestamp.
What is the Year 2038 problem (Y2K38)?
Legacy systems that store Unix time as a signed 32-bit second count overflow on 19 January 2038 UTC, when the value passes 2,147,483,647 and wraps negative. That can make clocks look like 1901. Modern stacks usually use 64-bit integers; audit older databases, binaries, and embedded firmware if you still depend on 32-bit time_t.
Why does my converted time look different from another timezone?
The same epoch value renders differently across timezones because formatting applies local offsets and daylight-saving rules. Compare UTC outputs when you need a neutral baseline across environments.
Is it safe to paste sensitive log timestamps here?
Yes. All conversion runs in your browser. Log lines, raw epoch integers, and picked dates are not uploaded, transmitted, or stored on our servers.
