Unix Timestamp Converter
Used 5,800 times
Paste a Unix epoch (seconds or milliseconds) or any date string — the tool auto-detects the format and outputs epoch, UTC, local time, ISO 8601, and a human-readable relative time.
Accepts Unix epoch (s or ms), ISO 8601, RFC 2822, or any string parseable by Date.parse. Press Enter or click Convert.
Latest Developer Tools articles
Bulk UUID Generator – Generate Hundreds of UUIDs for Test Fixtures
Learn how to generate batches of UUIDs for database seeding, test fixtures, and mock data. Covers UUID v4 and v7, output formats, and collision probability at scale.
HEX ↔ RGB ↔ HSL Color Converter
Convert colors between HEX, RGB, and HSL, build palettes, and ensure accessible contrast. Includes CSS snippets and WCAG guidance.
Compare API Responses Online – Debug Breaking Changes Between Versions
Learn how to compare REST API responses to find breaking changes, regressions, and contract violations. Covers JSON normalization, dynamic field handling, and API versioning workflows.
What is a Unix Timestamp?
A Unix timestamp (epoch) is the number of seconds elapsed since 00:00:00 UTC on 1 January 1970. Many systems also use milliseconds (multiply by 1000). Timestamps are timezone-independent, making them the standard for storing, comparing, and transmitting time in APIs, databases, and logs.
How to Use
- Paste a Unix epoch (e.g.
1700000000) or a date string (e.g.2024-01-15T12:00:00Z). - Press Enter or click Convert. Seconds vs milliseconds is detected automatically.
- Results show epoch-s, epoch-ms, UTC, local time (with UTC offset), ISO 8601, and relative time.
- Click the copy icon on any row to copy that value.
- Click Use current time to convert the current moment.
Common Use Cases
- Debugging logs — Convert raw epoch values in log lines to human-readable times.
- JWT expiry — The
expandiatclaims are Unix timestamps; convert them to confirm token validity. - Database queries — Generate epoch values for
WHERE created_at > ?filters. - API payloads — Verify that timestamps in request/response bodies represent the expected time.
FAQs
How does the tool detect seconds vs milliseconds?
If the numeric value is greater than 1e10, it is treated as milliseconds; otherwise seconds. This heuristic covers all dates from 2001 onward correctly.
What date string formats are supported?
Any format parseable by Date.parse(): ISO 8601 with or without timezone, RFC 2822, and most locale date strings. Ambiguous formats (e.g. 01/02/03) may be interpreted differently across browsers.
What is the Year 2038 problem?
32-bit signed integers overflow at epoch 2147483647 (2038-01-19). JavaScript uses 64-bit floats, so this tool handles dates well beyond 2038 without issue.