Time Converter
Converters · Added 9 August 2026
Convert a duration between time units, from milliseconds to years, and see the same span expressed every way at once.
Result
1 min in hour
0.0166666667 h
1 min = 0.0166666667 h
The same value in every unit
- Millisecond (ms)
- 60,000
- Second (s)
- 60
- Minute (min)
- 1
- Hour (h)
- 0.0166666667
- Day (d)
- 0.000694444444
- Week (wk)
- 0.0000992063492
- Month (average) (mo)
- 0.0000228158917
- Year (average) (yr)
- 0.00000190132431
A month here is the average Gregorian month (30.436875 days) and a year is 365.2425 days, so long spans stay consistent. For an exact gap between two calendar dates, use the date difference calculator instead.
How to use the time converter
- 1Enter the duration you want to convert.
- 2Pick the unit you have and the unit you want.
- 3The result appears immediately, with the full breakdown across all units below it.
- 4For the gap between two specific calendar dates, use the date difference calculator instead — it accounts for real month lengths and leap years.
Examples
A timeout value in code
- Input
- 90,000 milliseconds
- Result
- 1.5 minutes
Working hours in a year
- Input
- 2,000 hours
- Result
- 83.3333333 days
A typical full-time year of about 2,000 working hours is a little over 83 continuous days.
A long-running process
- Input
- 1,000,000 seconds
- Result
- 11.5740741 days
About the time converter
Durations and dates are different problems
A duration is a quantity — ninety minutes, three weeks, two billion seconds. It has no position on the calendar, so converting it is straightforward multiplication once you settle on how long an average month and year are.
A date range is a different question. The span from 31 January to 1 March is not a fixed number of days; it depends on the year. Any tool that answers calendar questions with average month lengths will be wrong by a day or two, which is why those questions belong in the date difference calculator instead.
Units that trip people up
Milliseconds are the usual source of confusion in software, where timeouts, animation durations and Unix timestamps all use them and a factor of 1,000 goes missing surprisingly often. If a delay is a thousand times longer or shorter than intended, this is almost always why.
At the other end, 'a billion seconds' is a genuinely unintuitive quantity — it is close to 31.7 years. Human intuition for durations breaks down somewhere around a few million seconds, which is exactly where a converter earns its place.