What is Timestamp Converter?
A Unix timestamp is the number of seconds (or milliseconds) that have elapsed since 00:00:00 UTC on 1 January 1970 — the "Unix epoch." It is the most common way computers store and exchange points in time, because a single integer is unambiguous, timezone-free, and easy to compare. This converter turns those raw numbers into human-readable dates and back again, showing local time, UTC, ISO 8601, and a relative ("3 hours ago") view all at once.
Anyone who works with logs, databases, APIs, or JWTs runs into Unix timestamps constantly. An API returns `created_at: 1700000000`, a log line is stamped with a 13-digit millisecond value, or a token's `exp` claim needs decoding. Instead of doing the math by hand, paste the value here and read off every format you need — the tool auto-detects whether you gave it seconds or milliseconds.
Use Cases
Here are the most common ways people use Timestamp Converter every day.
Debugging Logs and APIs
Server logs and API responses almost always use Unix time. When you see a timestamp like 1700000000 in an error log, paste it here to instantly know the local and UTC time the event happened, plus how long ago that was.
Decoding JWT and Token Expiry
JSON Web Tokens store issued-at (iat) and expiry (exp) as Unix seconds. Drop the number in to check exactly when a token was issued or when it expires, and whether it is already past.
Database Records
Many databases and ORMs store dates as epoch integers for portability. Convert a stored value to a readable date when inspecting rows, or convert a date to an integer to build a query filter.
Scheduling and Cron
When configuring scheduled jobs, feature flags, or cache expiry, you often need a future timestamp. Pick a date and time to get the exact seconds and milliseconds value to paste into your config.
Examples
Reading an API timestamp
Paste a value from a JSON response to see when it happened.
1700000000 Tue, 14 Nov 2023 22:13:20 UTC · ISO: 2023-11-14T22:13:20.000Z Getting a timestamp for a date
Pick a date and time to get the epoch value for your config or query.
2025-01-01 00:00:00 Seconds: 1735689600 · Milliseconds: 1735689600000 Timestamp Converter vs Manual calculation
Using this converter versus doing epoch math yourself.
| Feature | Toolorah | Manual calculation |
|---|---|---|
| Auto-detect seconds vs milliseconds | Yes | You have to know which |
| Local, UTC and ISO at once | Yes — all shown | Separate steps |
| Relative time ("3 hours ago") | Yes | Manual diff |
| Two-way conversion | Yes — date ↔ timestamp | Two formulas |
Tips for Using Timestamp Converter
- Values with 13 or more digits are treated as milliseconds; shorter values as seconds. JavaScript uses milliseconds, most backends use seconds.
- Use the "Use now" button to grab the current timestamp instantly for testing or config.
- ISO 8601 (the "Z" format) is the safest way to store and transmit dates between systems — it is unambiguous and timezone-aware.
- The relative view ("in 2 days", "5 minutes ago") is handy for sanity-checking whether a token or record is fresh.
Frequently Asked Questions
Does the tool use seconds or milliseconds?
Both. It auto-detects: a 10-digit value is read as seconds, a 13-digit value as milliseconds. On the date-to-timestamp side, it gives you both seconds and milliseconds so you can use whichever your system expects.
What timezone are the results in?
The "Local" line uses your browser's timezone. The "UTC" and "ISO 8601" lines are always in Coordinated Universal Time, which is the safe format for storage and APIs.
What is the Unix epoch?
It is the reference point 00:00:00 UTC on 1 January 1970. A Unix timestamp counts the seconds elapsed since that moment, which makes every point in time a single comparable number.
Is my data sent anywhere?
No. All conversion happens locally in your browser with JavaScript Date objects. Nothing is uploaded or stored.
What is ISO 8601?
ISO 8601 is the international standard date format, like 2023-11-14T22:13:20.000Z. The trailing Z means UTC. It sorts chronologically as plain text and is the recommended format for APIs and databases.