Time Converter

Convert Unix timestamps, ISO 8601, readable date strings, and compare time differences across global time zones.

Current Time

--:--:--

Unix: -

Input

Input Format Time Value Target Time Zone

Global Time Zones

Time Unit Conversion Reference

Every time unit in one table. Use it to check any conversion by hand, or type a value above to convert instantly.

Unit	In Seconds	Common Use
1 second	1 s	Base SI unit of time
1 minute	60 s	Everyday timing, meetings
1 hour	3,600 s	Work shifts, schedules
1 day	86,400 s	Daily planning, logs
1 week	604,800 s	Sprints, weekly reviews
1 month (avg 30.44 d)	2,629,800 s	Billing cycles, subscriptions
1 year (365 days)	31,536,000 s	Age, annual reports
1 year (leap, 366 d)	31,622,400 s	Calendar accuracy checks

Seconds to Time Format (hh:mm:ss)

Converting raw seconds into a readable hh:mm:ss clock format is the most common time conversion. The algorithm divides by shrinking units: hours first, then the remainder into minutes, and what is left is seconds.

Example: convert 9,782 seconds

Hours: 9,782 ÷ 3,600 = 2 (remainder 2,582 s)
Minutes: 2,582 ÷ 60 = 43 (remainder 2 s)
Seconds: 2
Result: 02:43:02

Quick lookup table

60 seconds	00:01:00
600 seconds	00:10:00
1,800 seconds	00:30:00
3,600 seconds	01:00:00
7,200 seconds	02:00:00
86,400 seconds	24:00:00 (1 day)
1900 seconds	00:31:40
1970 seconds	00:32:50

Tip: on this page select Readable as the input format, paste your seconds value, and every format — including ISO 8601 and UTC — updates at once, rendered in your target time zone.

How Each Time Format Is Used

Unix timestamp

Seconds since 1970-01-01 00:00:00 UTC. The lingua franca of databases, APIs, and logs because it is a single timezone-independent number. JavaScript usually adds a * 1000 because it works in milliseconds internally.

ISO 8601

The international standard (2026-08-16T12:00:00Z). Machine-sortable, unambiguous, and required by most modern REST APIs. The trailing Z marks UTC.

UTC string

RFC 7231 format (Sat, 16 Aug 2026 12:00:00 GMT) — still used in HTTP headers and email (Date header). Human-readable and always UTC.

Local readable time

What you see on a clock, e.g. 2026-08-16 20:00:00 in Shanghai for a 12:00 UTC instant. Always pair a local time with its timezone, or it is meaningless across regions.

Frequently Asked Questions

What is a Unix timestamp?

Unix timestamp is the number of seconds elapsed since January 1, 1970 00:00:00 UTC. It is timezone-independent for storage and comparison.

Can I convert ISO 8601 and UTC strings?

Yes. The converter supports Unix seconds, Unix milliseconds, ISO 8601, UTC strings, and browser-local readable formats.

Does timezone conversion account for DST?

Yes. Global conversion uses `Intl.DateTimeFormat` with IANA timezone IDs, including seasonal daylight saving changes.

How do I convert seconds to hh:mm:ss by hand?

Divide the seconds by 3,600 for hours, divide the remainder by 60 for minutes, and keep the rest as seconds. For example, 9,782 seconds is 2 hours, 43 minutes, 2 seconds (02:43:02).

How many seconds are in a day, a week, or a year?

A day is 86,400 seconds, a week is 604,800 seconds, and a 365-day year is 31,536,000 seconds. A leap year has 31,622,400 seconds.

Why do Unix timestamps in JavaScript look 1000x bigger?

JavaScript's Date works in milliseconds, while a classic Unix timestamp counts seconds. Multiply seconds by 1000 (or divide milliseconds by 1000) to convert between them — this tool does both automatically.

What is the difference between UTC and GMT?

GMT is a timezone (mean solar time at Greenwich), while UTC is a time standard kept by atomic clocks. For everyday conversion they show the same clock time, which is why the labels are often used interchangeably.