A meeting duration
90 minutes equals 1.5 hours or 5400 seconds. The breakdown is 0 days, 1 hour, 30 minutes, and 0 seconds.
Convert an elapsed duration
Fixed durations only. A day is exactly 24 hours here; calendar days can differ with daylight saving time.
Calendar units need dates
Months and calendar years are intentionally absent: their durations depend on the dates. The Julian year offered here is the fixed astronomical convention of 365.25 × 24 hours.
Converted amount
90 minutes (min)
hours (h)
Duration breakdown
0days (24 hours)
1hours
30minutes
0seconds
Equivalent units
| Unit | Amount |
|---|---|
| nanoseconds (ns) | 5.40000000e+12 |
| microseconds (µs) | 5,400,000,000 |
| milliseconds (ms) | 5,400,000 |
| seconds (s) | 5,400 |
| minutes (min) | 90 |
| hours (h) | 1.5 |
| fixed 24-hour days | 0.0625 |
| fixed 7-day weeks | 0.00892857143 |
| Julian years (365.25 fixed days) | 0.000171115674 |
Displayed values are rounded. CSV uses the available JavaScript numeric precision; it cannot restore precision absent from the input.
Calculations and CSV generation run locally in your browser. No measurement data is uploaded by this tool.
How to use the Time Unit Converter
- 01
Enter a nonnegative duration and choose its source unit. Scientific notation works for very short or long intervals.
- 02
Choose a target unit. The breakdown uses fixed 24-hour days and leaves any fractional seconds in the final part.
- 03
Copy the selected conversion or export the unit table. Use a date-aware tool when you need months, civil dates, or time-zone transitions.
Examples
A fixed seven-day interval
One fixed week equals 604,800 seconds. This describes an elapsed duration; it does not calculate the interval between local clock times a calendar week apart.
Subsecond timing
250 milliseconds equals 0.25 seconds, 250,000 microseconds, or 250,000,000 nanoseconds. No clock resolution or timer accuracy is implied by the conversion.
Fixed duration versus calendar arithmetic
Unit conversion works when each selected unit has a fixed relationship to the second. A calendar month may have 28, 29, 30, or 31 days, so no month option is provided. A calendar year can have 365 or 366 days. Date arithmetic also needs a calendar, a time zone, and rules for any clock changes.
What the Julian year option means
The Julian year here is a defined interval of 365.25 fixed days, totaling 31,557,600 seconds. It is useful in astronomical unit conventions. It is not a claim that every calendar year has that duration, and selecting it does not turn an elapsed interval into a civil date.
How the breakdown is formed
The tool removes whole 86,400-second days, then whole hours and minutes. The remainder is seconds. Very large totals above JavaScript’s safe whole-second integer range are not decomposed because the individual remainder parts could be misleading; direct unit conversions remain available.
What to know
- No dates, calendar months, time zones, daylight-saving transitions, or leap-second tables are applied.
- Subsecond detail is limited by floating-point precision, especially for very large totals.
- Decimal and scientific notation are supported; commas and unit text are not. Calculations use JavaScript floating-point numbers and displayed results are rounded.
Common questions
Why is there no month option?
A month is not a fixed number of seconds. Supply actual dates and a time zone in a date-aware calculator when the task is calendar-based.
Does a local day always last 24 hours?
The fixed day in this converter does. A local civil interval from midnight to midnight can differ when clocks change. Leap-second handling is also outside this duration model.
Can I enter negative time?
This tool models a nonnegative elapsed duration. It does not represent signed timestamp differences or dates before an epoch.
Does this convert Unix timestamps?
No. A timestamp identifies an instant relative to an epoch; this tool converts an interval between instants once you have determined its duration.