Unix Timestamp
Convert timestamps to human dates and back, with the live epoch ticking beside you. Everything runs on your device - nothing is ever uploaded.
Paste seconds, milliseconds, microseconds or nanoseconds - the unit is detected automatically.
Runs entirely on your device - nothing is ever uploaded.
More tools
- Stopwatch Time anything to the hundredth, with laps. Get started
- Timer A clean countdown that beeps when time is up. Get started
- Wheel Spinner Add options, spin the wheel, and let chance make the call. Get started
- Name Wheel Spin the wheel of names to pick a random winner. Get started
- Yes or No Wheel A two-slice decision wheel for instant answers. Get started
- Bingo Card Generator Printable word bingo cards in 3×3 to 6×6. Get started
- Random Team Generator Split any list of names into fair random teams. Get started
- Random Group Generator Divide people into random groups of any size. Get started
How to use Unix Timestamp
- Copy the live current timestamp from the clock at the top for logs and API calls.
- Paste a timestamp to read it as a date - seconds, milliseconds, microseconds and nanoseconds are detected automatically.
- Or pick a date and time to get its timestamp in seconds and milliseconds.
What it is for
Unix time counts seconds since 1 January 1970 and is how nearly every system records moments in time. Developers convert between epoch and local time constantly when reading logs, APIs, and databases.
How it works
Conversion uses your browser's date engine, so results appear in your device's timezone with the UTC equivalent shown. Values in seconds, milliseconds, and microseconds are detected automatically.
Worked example
1700000000 seconds → 2023-11-14 22:13:20 UTC (10 digits = seconds). 1700000000123 → the same instant in milliseconds (13 digits). Going the other way, 2026-01-01 00:00:00 UTC → 1767225600 s / 1767225600000 ms. If a timestamp looks "in the future," you likely pasted milliseconds where seconds were expected - divide by 1,000.
Limitations
Dates before 1970 yield negative timestamps that some databases reject. Far-future dates beyond January 2038 overflow 32-bit systems (the Y2K38 problem); this tool computes with full 64-bit doubles, but your backend may not. Daylight-saving transitions are handled by your browser's timezone database - for scheduling across zones, always store UTC and convert for display. Related: UUID Generator for unique IDs in logs.