Time Converter

Convert Unix timestamps to human-readable dates

Convert between Unix timestamps and human-readable dates in both directions. Paste a timestamp, get a date — or paste a date string and get the epoch seconds. No need to remember the format or write a throwaway script every time you're debugging a time-based field in an API response.

Unix Timestamp → Date & Time

Date & Time → Unix Timestamp

How to use

1Pick a panel — Top panel for timestamp → date. Bottom panel for date → timestamp.
2Enter a value — Top: Unix timestamp in seconds or milliseconds. Bottom: ISO 8601 or any readable date format.
3Click Convert — The result appears immediately below the input.
4Copy the result — The Copy button in the toolbar copies all values at once.

Examples

Unix timestamp from an API to a readable date

1716057600 → 2026-05-18 12:00:00 UTC

Read a date from an API — convert a created_at timestamp to a readable format without writing code.

Publication date to timestamp for filtering

2026-01-01 00:00:00 → 1735689600

Build a request parameter with a date filter — get a timestamp for from= or until= in the API.

Timestamp in milliseconds from JavaScript

1716057600000 → 2026-05-18 (auto-detected ms)

Paste a timestamp from Date.now() — the tool automatically detects milliseconds and shows UTC, Local, and ISO 8601.

ISO 8601 to Unix timestamp

2024-03-15T14:30:00Z → 1710509400

Convert an ISO 8601 date from an API response — prepare a timestamp for filtering requests or sorting.

Readable date to timestamp

2024-11-14 22:13:20 → 1731622400

Enter a date in any readable format — get a Unix timestamp for a request parameter or database storage.

When to use for web scraping

Timestamps appear everywhere in scraped data: created_at, updated_at, published_at in API responses. Some services return Unix timestamps in seconds, some in milliseconds, some in ISO 8601 strings. Manual conversion or throwaway scripts take time. The tool also helps form timestamps for API request parameters with date filtering.

FAQ

Seconds or milliseconds — how can I tell?›

A Unix timestamp in seconds right now is about 1.7 billion (10 digits). In milliseconds — about 1.7 trillion (13 digits). Just count the digits. The tool detects automatically too: if the value is greater than 10 billion — it treats it as milliseconds.

Is timezone taken into account?›

The result shows three formats at once: UTC, Local (your browser's timezone), and ISO 8601. Unix timestamps are always UTC — Local is displayed for convenient reading.

How do I convert a Unix timestamp from an API response?›

Copy the numeric field value (e.g., created_at: 1716057600) and paste it into the top panel. Click Convert — the tool automatically detects seconds or milliseconds and shows a readable date in UTC and Local. Useful for quick verification without writing code.

Why do timestamps in API responses look like large numbers?›

This is a Unix timestamp — the number of seconds (or milliseconds) since January 1, 1970 UTC. This format is convenient for storing and comparing dates in databases and APIs: numbers are easy to sort and compare without string parsing.

How do I handle timezones when parsing dates?›

If the API returns dates in ISO 8601 with a Z or +HH:MM suffix, the timezone is already explicitly specified. For Unix timestamps, no timezone is needed — always UTC. Problems arise with dates without a timezone: then check the API documentation for which timezone is implied.