Unix Timestamp Converter
Convert between Unix timestamps and human-readable dates
Current Timestamp
Seconds
1783698166 Milliseconds
1783698166000 7/10/2026, 3:42:46 PM
Timestamp to Date
Date to Timestamp
Convert Unix timestamps to readable dates and back, in any timezone
Unix timestamps are seconds (or milliseconds) since 1970-01-01 UTC. They are everywhere: API responses, JWT claims, log files, database columns, telemetry, and command-line output. This page converts in both directions, switches between seconds and milliseconds, and lets you preview the same instant in UTC and in your local timezone. That helps when debugging clock skew, scheduled jobs, scheduled emails, and bug reports written by users in different regions.
- Decide whether your input is in seconds (10 digits, common in JWT and Unix tooling) or milliseconds (13 digits, common in JavaScript).
- Paste the timestamp or pick a date and watch the converted values update for both UTC and your local time.
- When debugging logs, copy the timestamp from the log line directly to avoid transcription errors.
- For scheduled jobs and reminders, double-check the timezone offset that the producing system uses.
Time bugs are usually about timezone boundaries, not arithmetic
Unix timestamps are simple. What creates bugs is the conversion layer between machine time and human time: local zones, DST, database column types, log formats, and API documentation often disagree with each other.
The same instant can appear differently in browsers, Node, Java, database consoles, and cloud logs without any data corruption at all. That makes timestamp pages ideal candidates for substantial explanatory content.
How to use a time converter during incidents
During debugging, normalize everything to the same timezone and precision first. Many false alarms come from comparing seconds to milliseconds, or UTC logs to local-time dashboards.
The page should also remind users that storage choices matter. Saving timestamps as strings, mixing local and UTC values, or silently switching precision between APIs creates long-term analysis costs that no incident team enjoys.
Best use cases
- Translating JWT `exp` and `iat` claims into human-readable dates.
- Reading database columns that store timestamps as integers.
- Comparing scheduled job times across systems with different default timezones.
Common mistakes to avoid
- JavaScript `Date.now()` returns milliseconds, but most Unix tooling and POSIX `time()` return seconds. Mixing them produces 1970 dates or far-future dates.
- Daylight saving time shifts can make local-time scheduling unreliable. Store timestamps in UTC and convert only at the edge.
- Comparing timestamps across systems with unsynchronized clocks gives misleading results. Verify NTP before chasing skew bugs.
Related tools
Move directly into the next step instead of leaving the site to do adjacent work elsewhere.
Cron Expression Debugger
Explain cron expressions in both directions, predict upcoming runs, and debug scheduler rules safely in the browser.
JWT Decoder & Security Auditor
Decode and inspect JSON Web Tokens with client-side security checks for none algorithm, expiry, audience, issuer, and risky claim setups.
JSON Formatter / Validator
Format, minify and validate JSON data
UUID / ULID Generator
Generate UUIDs (v1, v4, v7) and ULIDs in bulk. UUID v7 is timestamp-prefixed and lexically sortable — great for database keys.
FAQ
How do I tell seconds from milliseconds?
A 10-digit number is almost certainly seconds; a 13-digit number is almost certainly milliseconds. Beyond 2286 the digit count grows, but for present-day data this rule of thumb works.
What timezone does the tool show?
Both UTC and your browser's local timezone, so you can spot offset bugs without switching tools.
Can I convert ISO 8601 strings?
Yes. Paste an ISO string and the tool will display the corresponding Unix timestamp in both seconds and milliseconds.