Skip to main content
UnblockDevs
All toolsTimezone TranslatorCron ExpressionString Utilities
⏱️

Unix Timestamp Converter

Convert Unix timestamps to human-readable dates in any timezone — or convert dates back to Unix. Live clock, world clock, relative time, and 9 output formats. 100% in-browser.

100% in-browserUnix ↔ DateWorld clockNo signup

Current time — UTC

23:25:12Sat, May 30, 2026

Unix: 1780183512

Convert

Enter a Unix timestamp or pick a date above

You might also need
Browse all tools
Timezone TranslatorTranslate between timezonesCron ExpressionBuild & decode cron jobsString UtilitiesTransform & manipulate stringsJSON → TypeScriptGenerate TS types from JSONJSON → ExcelExport JSON to ExcelAll tools

The Unix Timestamp Tool Every Developer Bookmarks

You are debugging a log file and see 1704067200. You are reading an API response with a created_at field in epoch milliseconds. You are setting an expiry on a JWT token and need the timestamp for exactly 24 hours from now. In every case, you reach for the same tool: a Unix timestamp converter.

This one shows the current Unix time as a live clock, converts in both directions (Unix → date and date → Unix), auto-detects seconds vs milliseconds, outputs 9 formats at once — ISO 8601, UTC string, relative time, local date, day of year — and displays the same moment across 14 world timezones. No page reload. No server round-trips. Just fast answers.

How it works

Instant Conversion in Both Directions

01

View the live clock

The current Unix timestamp updates every second at the top. Click "Copy" to grab it anytime.

02

Pick conversion direction

Choose "Unix → Date" to decode a timestamp, or "Date → Unix" to convert a human-readable date to epoch time.

03

Enter your value

Paste a Unix timestamp (seconds or ms auto-detected) or pick a date with the date picker. Hit "Use now" to use the current time.

04

Copy any output format

Every output row has its own copy button — ISO 8601, UTC string, relative time, local date, and 14 world timezone clocks.

Use cases

When Developers Need a Timestamp Converter

🪵

Log File Debugging

Decode epoch timestamps in server logs, Kubernetes events, and database query logs to understand exactly when something happened.

🔑

JWT Expiry Debugging

Decode the exp and iat claims from JWT tokens (Unix seconds) to check if a token is expired or when it was issued.

📡

API Response Parsing

Decode created_at, updated_at, and expires_at fields from REST and GraphQL API responses during integration.

⏰

Scheduled Jobs

Calculate the exact Unix timestamp for a future cron job, scheduled task, or cache TTL expiry.

🌍

Cross-timezone Coordination

Convert a deployment or incident time to every team member's local timezone for post-mortems or scheduling.

🗄️

Database Timestamps

Decode Unix timestamps stored in MySQL, PostgreSQL, MongoDB, or Redis to understand when records were created or modified.

FAQ

Frequently Asked Questions

1How do I convert a UTC timestamp to local time in JavaScript?
Use Intl.DateTimeFormat: new Intl.DateTimeFormat("en-US", { timeZone: "America/New_York", dateStyle: "full", timeStyle: "long" }).format(new Date(timestamp * 1000)). Or use toLocaleString: new Date(timestamp * 1000).toLocaleString("en-US", { timeZone: "America/New_York" }). Both apply DST automatically. Never use manual UTC offset arithmetic — it breaks during DST transitions.
2What is the difference between Unix seconds and milliseconds?
Seconds timestamps are 10 digits (e.g. 1704067200). Millisecond timestamps are 13 digits (e.g. 1704067200000). JavaScript's Date.now() uses milliseconds. Most UNIX system APIs and databases use seconds. This tool auto-detects which you have entered.
3Why do I get a wrong date when I convert a Unix timestamp?
The most common cause is mixing seconds and milliseconds. JavaScript's Date constructor expects milliseconds — if you pass a 10-digit seconds timestamp, multiply by 1000 first: new Date(timestamp * 1000). If the result shows 1970, you forgot the multiplication. If the date is off by a fixed number of hours, check the timezone — Unix timestamps are UTC and must be explicitly converted to local time.
4How do I get the current Unix timestamp in JavaScript?
Use Math.floor(Date.now() / 1000) for seconds, or Date.now() for milliseconds. In Python, use int(time.time()). In Go, use time.Now().Unix().
5What is the difference between seconds and milliseconds timestamps?
A seconds-precision Unix timestamp is a 10-digit integer (e.g. 1704067200). A milliseconds-precision timestamp is 13 digits (e.g. 1704067200000). JavaScript's Date.now() returns milliseconds; most server-side Unix APIs and JWT tokens use seconds. This tool auto-detects the precision from the digit count.
6How do I convert a Unix timestamp in JavaScript?
Pass the timestamp to the Date constructor: new Date(timestampMs) for milliseconds, or new Date(timestampS * 1000) for seconds. For ISO 8601 output: new Date(ts * 1000).toISOString(). For the current Unix timestamp in seconds: Math.floor(Date.now() / 1000).
7How do I convert a Unix timestamp in Python?
Use datetime.fromtimestamp(ts) for local time or datetime.utcfromtimestamp(ts) for UTC. For timezone-aware results: datetime.fromtimestamp(ts, tz=timezone.utc). In pandas: pd.to_datetime(ts, unit="s") for seconds or unit="ms" for milliseconds.
8How do I get the current Unix timestamp?
JavaScript: Math.floor(Date.now() / 1000) (seconds) or Date.now() (milliseconds). Python: int(time.time()). Go: time.Now().Unix(). PHP: time(). Bash: date +%s. This tool also shows the live current timestamp, updating every second.
9Why does my timestamp show 1970 in JavaScript?
If new Date(timestamp) returns January 1, 1970, you are passing a seconds-precision timestamp (10 digits) to a constructor that expects milliseconds (13 digits). Fix it with new Date(timestamp * 1000). Unix timestamp 0 is January 1, 1970 00:00:00 UTC — a near-zero value is a reliable sign of the seconds/milliseconds confusion.
10What is the Year 2038 problem?
The Year 2038 problem (Y2K38) occurs because many systems store Unix timestamps as a 32-bit signed integer, which maxes out at 2,147,483,647 — corresponding to January 19, 2038 03:14:07 UTC. After that it overflows. Modern 64-bit systems avoid this issue, but legacy embedded systems and older databases may still be affected.
11How do I convert a timestamp to UTC?
Unix timestamps are inherently UTC. To display as UTC in JavaScript: new Date(ts * 1000).toUTCString() or new Date(ts * 1000).toISOString(). In Python: datetime.utcfromtimestamp(ts) or datetime.fromtimestamp(ts, tz=timezone.utc).
12How do I store timestamps in a database?
Store timestamps in UTC as a Unix integer, an ISO 8601 string with a Z suffix, or a native TIMESTAMP WITH TIME ZONE column (PostgreSQL, MySQL 8+). Never store local times without an explicit UTC offset — DST transitions and server timezone changes can corrupt historical data.
13How do I convert ISO 8601 to Unix timestamp?
JavaScript: Math.floor(new Date("2024-01-01T00:00:00Z").getTime() / 1000). Python: int(datetime.fromisoformat("2024-01-01T00:00:00+00:00").timestamp()). This tool's Date → Unix mode accepts ISO 8601 strings and returns both seconds and millisecond timestamps.
14What is the difference between UTC and local time in timestamps?
A Unix timestamp is always UTC — the same integer represents the same moment everywhere on Earth. Local time is what a clock in a specific timezone shows for that moment. For example, Unix timestamp 1704067200 is 2024-01-01 00:00:00 UTC but 2023-12-31 19:00:00 EST. This tool converts any Unix timestamp to your chosen IANA timezone.
15How do I add or subtract time from a Unix timestamp?
Unix timestamps are integers, so arithmetic is straightforward: add 3600 for 1 hour, 86400 for 1 day, 604800 for 1 week. For months or years, use a library because month lengths vary. JavaScript: use dayjs or date-fns. Python: use timedelta for fixed durations or dateutil.relativedelta for calendar-aware offsets.
Learn more

Developer Guides

📖Working with Timestamps in APIs📖JWT Claims Deep Dive📖Timezone Best Practices for Backends📖Date Serialization in JSON

Last updated: May 2026

Feedback for timestamp_converter

Tell us what's working, what's broken, or what you wish we built next — it directly shapes our roadmap.

You make the difference

Good feedback is gold — a rough edge you hit today could be smoother for everyone tomorrow.

  • Feature ideas often jump the queue when lots of you ask.
  • Bug reports with steps get fixed faster — paste URLs or examples if you can.
  • Name and email are optional; we won't use them for anything except replying if needed.

Stay Updated

Get the latest tool updates, new features, and developer tips delivered to your inbox.

What you'll get
  • Product updates & new tools
  • JSON, API & developer tips
  • Unsubscribe anytime — no hassle

Get in touch

Feature ideas, bugs, or a quick thanks — we read every message.

support@unblockdevs.com