TrustComponent
Sign inGet started

Free developer tools

Timestamp Converter.

The current Unix time, live — and instant conversion between timestamps and readable dates, entirely in your browser.

Developed and hosted in the EU
Timestamp Converter
Unix epoch · ISO 8601
Runs entirely in your browser
Current Unix time
— seconds

Interpreted in your local timezone.

All conversions run on your device — nothing is transmitted or stored. Times are shown in your browser's timezone.

One number, one instant

Unix time counts the seconds since January 1, 1970, 00:00 UTC — the epoch. Because it is a single number without any timezone attached, it is the standard way to store and compare points in time in databases, logs and APIs. The timezone appears only when you format the number for humans, which is exactly how this converter treats it: store UTC, display local.

Seconds or milliseconds?

The classic off-by-1000 bug: mixing up units. Current Unix time is a 10-digit number in seconds and a 13-digit number in milliseconds. JavaScript's Date.now() gives milliseconds, while date +%s, most APIs and databases use seconds. If your date renders as January 1970, you treated milliseconds as seconds; if it lands 50,000 years in the future, the reverse.

The year-2038 problem

On January 19, 2038 at 03:14:07 UTC, signed 32-bit timestamps overflow and wrap around to 1901. Modern 64-bit systems are safe, but embedded devices, legacy file formats and old database columns are not — worth checking for anything designed to live past 2038.

Prefer ISO 8601 in text

Where humans read the value — logs, JSON APIs, config — use ISO 8601 in UTC: 2026-07-07T09:30:00Z. It is unambiguous, machine-parseable and sorts correctly as a plain string. A good rule: Unix timestamps for storage and math, ISO 8601 for interchange, localized formats only at the UI.

Timestamps in your code

JavaScript
milliseconds!
// current time
const ms = Date.now();          // 13 digits
const s = Math.floor(ms / 1000); // 10 digits

// timestamp → date
const date = new Date(1783500000 * 1000);
date.toISOString(); // "2026-07-08T02:40:00.000Z"
Python
datetime, UTC-aware
from datetime import datetime, timezone

now = int(datetime.now(timezone.utc).timestamp())

# timestamp → datetime
dt = datetime.fromtimestamp(1783500000, tz=timezone.utc)
dt.isoformat()  # "2026-07-08T02:40:00+00:00"

Frequently asked questions

What is a Unix timestamp?
The number of seconds that have passed since January 1, 1970 at 00:00 UTC — the "Unix epoch". It is the most common machine format for points in time: a single number, no timezone ambiguity, easy to store, compare and sort.
Is my timestamp in seconds or milliseconds?
Count the digits: current timestamps have 10 digits in seconds and 13 digits in milliseconds. JavaScript's Date.now() returns milliseconds; most Unix tools and APIs use seconds. This converter detects the unit automatically from the length.
Do Unix timestamps have a timezone?
No — a Unix timestamp is always UTC by definition. Timezones only appear when you format the timestamp as a human-readable date. That is what makes timestamps ideal for storage: convert to the user's local time only at display time.
What is the year-2038 problem?
Systems that store timestamps as signed 32-bit integers overflow on January 19, 2038 at 03:14:07 UTC. Modern systems use 64-bit integers, which push the limit some 292 billion years out — but old embedded systems, file formats and databases can still be affected.
Can a Unix timestamp be negative?
Yes — negative values represent moments before January 1, 1970. For example, -86400 is December 31, 1969 at 00:00 UTC. Most systems handle this correctly, but some APIs reject negative values.
Does Unix time count leap seconds?
No. Unix time pretends every day has exactly 86,400 seconds. When a leap second occurs, Unix clocks repeat or smear a second instead of counting it. For everyday use this never matters — but it means Unix time is not strictly the number of physical seconds since 1970.
What is ISO 8601, and how does it relate?
ISO 8601 is the standard human-readable format: 2026-07-07T09:30:00Z, with the Z meaning UTC. It is the best text format for APIs and logs — unambiguous and sortable as a string. A Unix timestamp and an ISO 8601 UTC string describe the same instant in two representations.

More free tools

All tools →
Calendar Weeks

The current ISO calendar week at a glance, plus every week of any year.

Open tool
Password Generator

Strong random passwords with configurable length and character sets.

Open tool
Passphrase Generator

Memorable diceware-style passphrases from a 7,776-word list.

Open tool

Free tools from a European software company.

  • Runs in your browser
  • Made & hosted in the EU
  • No account needed
Explore our products Browse resources