Convert Seconds to Time

Yes – input 3661.5 and you’ll see 01:01:01.500 in HH:MM:SS, 1h 1m 1.5s in compact, 1 hour, 1 minute, 1.5 seconds in words, and PT1H1M1.5S in ISO. Milliseconds are rounded from the fractional part (so .5 = 500 ms). Most “seconds to time” converters silently drop decimals because they use parseInt – this one uses Number() and propagates the fraction through every output format.

Rejected with a specific error: “Negative seconds not allowed – use absolute value or Swap to reverse”. This is intentional. A common bug in seconds-to-time tools is silently calling Math.abs() so that -3600 displays as 01:00:00 with no indication anything was wrong – the result looks correct but the sign was eaten. We surface the issue instead.

Up to Number.MAX_SAFE_INTEGER (≈ 9.0 × 10¹⁵, or 285 million years in seconds). Beyond that, JavaScript’s double-precision floats lose integer precision and the breakdown stops being reliable, so the tool rejects with a specific error pointing to the cap. For everyday inputs (durations, video lengths, timestamps), you’ll never hit it.

HH:MM:SS rolls everything into hours – 90,000 seconds becomes 25:00:00. DD:HH:MM:SS splits the day field out – same input becomes 01:01:00:00. Use HH:MM:SS for video timestamps, stopwatch displays, and CSS-friendly times. Use DD:HH:MM:SS for elapsed durations where “1 day, 1 hour” reads more naturally than “25 hours”.

ISO 8601 durations (P1DT2H3M4S) are the standard interchange format for durations in APIs (JSON Schema, OpenAPI, GraphQL), databases (PostgreSQL interval), and code libraries (Java Duration, Python isodate, C# TimeSpan). If you’re feeding the converted value into one of those, copy the ISO row and it’ll parse on the receiving end without extra work.

The tool picks the largest unit that produces a non-trivial number (≥ 1) and shows that with one decimal place. So 90,000 s = 25.0 hours (not 1.0 day because hours fits cleaner). 86,400 s = 1.0 days. 45 s = 45.0 seconds. Useful for at-a-glance scale checks where you don’t need precision but want “is this minutes or days?” instantly.

Six: (1) Colon-separated HH:MM:SS or D:HH:MM:SS (2) compact 1d 2h 3m 4s with unit suffixes (3) full words "1 day, 2 hours, 3 minutes, 4 seconds" with commas optional (4) ISO 8601 P1DT2H3M4S (case-insensitive) (5) bare seconds (just a number) (6) millisecond suffix 1500ms. Mixed formats in batch mode work too – each line parsed independently.

The parser is lenient – 1 hour, 2 hours, 1 hr, 2 hrs all work. Output is grammatically correct: 1 day, 2 hours (singular for 1, plural for everything else). Zero values are skipped entirely in compact and words formats so the output stays clean rather than padding with 0 hours, 0 minutes.

No. All parsing, breakdown, format generation, and TSV emission run in your browser. Open DevTools → Network and confirm zero requests fire – even when you Convert, Swap, or Download. Safe for timestamp data from logs, video metadata, or anything you’d rather not send to a third-party converter.

Yes. Total bundle is about 20 KB. Load once, disconnect, keep using. Time conversion is a pure computation – no fonts to fetch, no analytics, no remote API. Useful on planes, in airgapped dev environments, or whenever a quick local conversion beats opening a cloud tool.