Now (Unix)
—
·
UTC
—
Unix Epoch Converter
Free Unix timestamp converter. Convert epoch seconds or milliseconds to UTC, local time, and ISO 8601 instantly. Auto-detects seconds vs milliseconds.
Free
No login
100% browser-based
No data sent to servers
Try these next
What is a Unix Epoch Converter?
A Unix timestamp (also called an epoch timestamp) is the number of seconds elapsed since 00:00:00 UTC on 1 January 1970, known as the Unix epoch. It is the universal standard for representing time in software — databases, APIs, log files, and JWT expiry fields all use Unix timestamps because they are timezone-independent and trivially sortable.
This tool converts between Unix timestamps and human-readable dates instantly. Paste a timestamp to see the UTC and local time, or pick a date to get its Unix value. Supports seconds and milliseconds.
What is a Unix timestamp?
A Unix timestamp is the number of seconds elapsed since January 1, 1970 at 00:00:00 UTC (the Unix epoch). It's a universal, timezone-independent way to represent a moment in time.
What's the difference between seconds and milliseconds timestamps?
10-digit timestamps are in seconds. 13-digit timestamps are in milliseconds. JavaScript's Date.now() returns milliseconds; most Unix systems use seconds. This tool auto-detects which one you've entered.
How do I get the current Unix timestamp in code?
JavaScript: Math.floor(Date.now()/1000) · Python: import time; int(time.time()) · PHP: time() · Go: time.Now().Unix()
What timezone are Unix timestamps in?
Unix timestamps are always in UTC — they represent seconds since 1970-01-01 00:00:00 UTC regardless of your local timezone. When displaying timestamps to users, always convert to their local timezone. When storing timestamps in databases, always store as UTC and convert at display time.
How do I get the current timestamp in code?
JavaScript: Date.now() (milliseconds) or Math.floor(Date.now()/1000) (seconds). Python: import time; int(time.time()). PHP: time(). Unix shell: date +%s. SQL: UNIX_TIMESTAMP() (MySQL), EXTRACT(EPOCH FROM NOW()) (PostgreSQL). Note: most languages return milliseconds — divide by 1000 for seconds.
What is the Year 2038 problem?
On January 19, 2038 at 03:14:07 UTC, 32-bit signed Unix timestamps will overflow (max value: 2,147,483,647). Systems still using 32-bit timestamps will roll over to a negative number, causing date calculation bugs. Modern 64-bit systems are not affected — they can represent dates billions of years into the future.
What's the difference between Unix timestamp and ISO 8601?
A Unix timestamp is an integer (e.g. 1735689600) — compact and timezone-agnostic, ideal for calculations and APIs. ISO 8601 is a human-readable string (e.g. 2025-01-01T00:00:00Z) — easier to read and debug. Most modern APIs accept both. Use Unix timestamps for backend storage and ISO 8601 for logs and user-facing displays.