Convert a Unix Timestamp
Epoch, ISO 8601 and timezone math
What is Unix Timestamp Converter?
Paste a Unix timestamp, a log line, a JSON payload or a Mongo document, and every timestamp-shaped value inside it is found and converted. Most converters give you one box for one number, which means finding and extracting the value yourself first. This one scans free text and reads Unix seconds, milliseconds, microseconds and nanoseconds, ISO 8601, RFC 2822, Mongo ObjectIds, .NET ticks and Windows FILETIME. Each result is shown in UTC and in as many timezones as you pin, and the page URL carries the moment so a colleague opens exactly the same conversion.
How do I use Unix Timestamp Converter?
- Paste the value, or the whole line or payload it sits in.
- Pick which detected timestamp to convert if there is more than one.
- Pin the timezones you care about; they are remembered on this device.
- Copy any format, or copy the link to share the exact moment.
When should I use Unix Timestamp Converter?
Reach for this when reading a log line, debugging a token expiry, or comparing an event across regions. To measure the gap between two calendar dates, use Date Difference. To compare working hours across offices, use Timezone Converter. For a recurring schedule expression, use Cron Generator.
Frequently asked questions
How does it tell seconds from milliseconds?
Digit count is the first filter: roughly 10 digits is seconds, 13 is milliseconds, 16 is microseconds and 19 is nanoseconds. Because that is only a heuristic, each reading is also checked for plausibility, and a value that lands between 1990 and 2100 wins. When two readings are both plausible, both are shown rather than one being picked silently.
Why is my number not detected?
Numbers are only treated as timestamps when they resolve to a moment between 1990 and 2100. That is what stops ports, HTTP status codes, byte counts and IDs from filling the results with noise. Paste the bare value on its own and the stricter parser will accept a wider range.
What is a Mongo ObjectId doing in a timestamp tool?
The first four bytes of an ObjectId are the document creation time in Unix seconds, so any ObjectId is also a timestamp. Paste one and the creation time is read straight out of it, which saves a trip through a database client.
What are .NET ticks and Windows FILETIME?
Both count 100 nanosecond intervals, .NET from year 1 and FILETIME from 1601. They are 18 or 19 digits, which collides with nanosecond Unix epochs, so when a value could be either, both readings are offered.
Does the shared link contain my pasted text?
No. The link carries only the selected moment as a number. Whatever you pasted, including any log content around it, stays in your browser and is never put in the URL.
Where are my pinned timezones stored?
In your browser local storage on this device only. They are never sent anywhere, and they are not part of the shared link.
Does it handle leap seconds?
No, and neither does Unix time itself. A Unix timestamp counts non-leap seconds by definition, so a leap second repeats a value rather than adding a new one. Every mainstream language and database behaves the same way.
Is my file uploaded anywhere?
No. Everything runs in your browser. Your files never leave your device, and there is no server component for this tool.
Tools that pair well with Unix Timestamp Converter
- Time Zone Converter compare times across zones, free and in your browser.
- Date Difference Calculator days/weeks/months between dates, free and in your browser.
- Cron Expression Parser human-readable cron, free and in your browser.
- JWT Decoder inspect jwt payloads, free and in your browser.