Unix Timestamp Converter
Convert Unix timestamps in seconds or JavaScript milliseconds into UTC and common timezone views. Also convert an ISO date-time string back into Unix seconds and milliseconds.
Epoch
1970-01-01 UTC
Units
seconds + ms
Views
UTC + zones
Live converter
Unix timestamp inputs
Convert Unix seconds or JavaScript milliseconds into UTC and local time displays.
UTC date-time
2026-06-10T12:00:00.000Z
Timestamp comparison table
| View | Value | Note |
|---|---|---|
| UTC | Wed, Jun 10, 2026 12:00 | UTC+00:00 |
| Dubai | Wed, Jun 10, 2026 16:00 | UTC+04:00 |
| New York | Wed, Jun 10, 2026 08:00 | UTC-04:00 |
| ISO input seconds | 1781092800 | From ISO field |
| ISO input milliseconds | 1781092800000 | From ISO field |
Convert timestamps for logs, APIs, databases, and debugging
Timestamp debugging
Translate Unix seconds and JavaScript milliseconds into readable UTC and timezone-specific values.
Full comparison table
Review surrounding units or time zones after the selected result, reducing repeated input for adjacent checks.
Formula-backed output
Use visible method notes to understand how the result was produced before copying it into another workflow.
Unix timestamp conversion formula
Unix timestamps count elapsed time from the Unix epoch at 1970-01-01 00:00:00 UTC. JavaScript Date values use milliseconds.
Working formulas
Seconds to milliseconds
milliseconds = Unix seconds x 1000
JavaScript Date constructors use milliseconds.
Milliseconds to seconds
Unix seconds = floor(milliseconds / 1000)
Unix timestamp APIs often store seconds.
Epoch
0 = 1970-01-01T00:00:00Z
The timestamp is measured from midnight UTC at the Unix epoch.
Symbols
- Unix seconds - timestamp seconds
- Whole seconds elapsed since the Unix epoch.
- JS milliseconds - Date time value
- Milliseconds elapsed since the same UTC epoch.
Why timestamp units need clear labels
Seconds and milliseconds together
- Unix APIs commonly use seconds, while JavaScript Date values use milliseconds.
- The converter labels both units so users do not accidentally shift a date by a factor of 1000.
- ISO input conversion helps check expected timestamps before saving values into systems.
UTC first
- The primary result is an ISO UTC timestamp, which is the safest value for debugging.
- Timezone rows are displayed as views of the same instant, not separate moments.
- Offsets remain visible for quick inspection across regions.
Built for technical time debugging
Developers
Convert API timestamps, log fields, queue events, and database values into readable times.
Analysts
Check whether imported timestamp fields are seconds, milliseconds, or ISO strings.
Ops teams
Compare event timestamps across UTC, Dubai, New York, and other operational contexts.
How it works in three quick steps.
Enter the timestamp
Paste a Unix timestamp and choose whether it is seconds or JavaScript milliseconds.
Read UTC and timezone views
Review the ISO UTC date and the table of local-time views.
Convert ISO back to timestamp
Use the ISO field to calculate Unix seconds and milliseconds for a known date-time string.
Save timestamp conversions
Copy result
Copy the selected conversion with labels so the result can move into tickets, docs, worksheets, or chat.
Print the table
Print the full table when a task needs repeated comparisons across related units or time zones.
Keep the formula visible
Use the formula notes to explain whether the result came from a factor, an offset, or a timezone rule.
About this Unix timestamp converter
Timestamp bugs often come from unit mismatch. A value may be Unix seconds in one API, JavaScript milliseconds in a browser, and an ISO string in a database export. This converter keeps those forms visible together.
UTC is shown first because it is the cleanest debugging reference. Local-time rows are useful for human interpretation, but they are displays of the same instant rather than separate stored values.
The ISO input field supports the reverse workflow: start with a known date-time string and calculate the seconds or milliseconds needed for a system field.
Keep building