Time Duration Converter
Convert elapsed time units from milliseconds through average Gregorian years. The converter is built for durations, timers, logs, SLAs, and estimates, not calendar date arithmetic.
Base unit
second
Supported units
8
Includes
avg months + years
Live converter
Time duration inputs
Convert elapsed time units from milliseconds through average Gregorian years.
Converted result
1.5 hr
Duration comparison table
| Unit | Converted value | Unit name | Note |
|---|---|---|---|
| ms | 5,400,000 | Milliseconds | 1/1000 second |
| sec | 5,400 | Seconds | Base duration unit for this converter |
| min | 90 | Minutes | 60 seconds |
| hr | 1.5 | Hours | 3600 seconds |
| day | 0.0625 | Days | 24 hours |
| wk | 0.00892857142857 | Weeks | 7 days |
| mo | 0.00205343025524 | Average Gregorian months | 365.2425 days / 12 |
| yr | 0.000171119187937 | Average Gregorian years | 365.2425 days |
Base unit
second
Supported units
8
Includes
avg months + years
Convert durations for logs, timers, schedules, and estimates
Elapsed time checks
Translate milliseconds, seconds, minutes, hours, days, weeks, average months, and years for practical duration work.
Full comparison table
Review surrounding units or time zones after the selected result, reducing repeated input for adjacent checks.
Formula-backed output
Use visible method notes to understand how the result was produced before copying it into another workflow.
Time duration conversion formula
The converter normalizes elapsed durations to seconds, then divides by the target unit factor.
Working formulas
Base conversion
seconds = value x seconds per source unit
Every elapsed duration is converted into seconds first.
Target value
target value = seconds / seconds per target unit
The second value is divided by the target duration factor.
Average year
1 average year = 365.2425 days
Average months and years are for durations, not calendar dates.
Symbols
- seconds - base duration
- The normalized elapsed time value.
- average month - duration estimate
- 365.2425 days divided by 12, used only for elapsed-time estimates.
Fixed durations versus calendar time
This live converter answers elapsed-time questions by normalizing each input to seconds. It deliberately does not add months to calendar dates or infer daylight-saving changes, billing boundaries, or local civil-time rules.
Fixed units and labeled averages
The configured relationships from milliseconds through weeks are fixed: 1 minute is 60 seconds, 1 hour is 3,600 seconds, 1 day is 86,400 seconds, and 1 week is seven such days. Those factors are suitable for timers, traces, SLAs, and duration fields.
The month and year rows are different. They use an average Gregorian year of 365.2425 days and one twelfth of that duration for a month. Those are comparison estimates, not promises about the length of a named calendar month.
Worked conversion: 90 minutes
90 min x 60 s/min = 5,400 s; 5,400 / 3,600 = 1.5 h
Both results are exact in this fixed-duration model. The same 90-minute span can cross a daylight-saving transition on a wall clock, but that does not change its elapsed duration.
Choose the model before copying
For milliseconds, seconds, minutes, hours, days, and weeks, copy the result with the unit and preserve only the precision present in the source timer or record. The display is formatted to at most 12 significant digits.
For average months or years, keep the word average beside the value. If a start date, due date, renewal date, or legal deadline matters, use date-aware calendar arithmetic instead of a duration factor.
Use this page for a number of elapsed units. Use a timestamp or timezone tool when the question concerns a specific instant, local offset, or calendar date.
Convert a specific instant with the Unix timestamp toolLimits to keep with the result
- Average months do not reproduce February, 30-day months, 31-day months, or a specific billing cycle.
- Local daylight-saving shifts and time-zone rules are outside this fixed elapsed-time model.
- The converter does not add leap-second labels or reconcile a duration with an external clock source.
Why duration conversion needs notes
Good for elapsed time
- Timers, logs, SLA windows, and estimates can be converted through seconds cleanly.
- The table shows exact fixed units and clearly marks average month/year assumptions.
- Users can copy the selected result while keeping the full comparison table available.
Avoids calendar mistakes
- Months are not all the same length, so this page labels average months explicitly.
- Calendar date math should be handled by date-aware tools, not a raw duration converter.
- The notes column explains which rows are fixed and which rows are average estimates.
Useful for elapsed-time workflows
Operations and SLAs
Convert uptime, response windows, queue durations, and service-level targets.
Students and teachers
Convert seconds, minutes, hours, days, and weeks for classroom problems.
Planning estimates
Translate rough months and years into days or hours when average-duration assumptions are acceptable.
How it works in three quick steps.
Enter elapsed time
Type a timer value, log duration, SLA window, study interval, or estimate.
Choose duration units
Select units from milliseconds through average years. The result updates immediately.
Check average units
Use notes for months and years because those are average Gregorian durations, not calendar date shifts.
Save duration conversions
Copy result
Copy the selected conversion with labels so the result can move into tickets, docs, worksheets, or chat.
Print the table
Print the full table when a task needs repeated comparisons across related units or time zones.
Keep the formula visible
Use the formula notes to explain whether the result came from a factor, an offset, or a timezone rule.
Frequently Asked Questions
Is this duration converter the same as date arithmetic?
Why are months and years labeled as average?
How many seconds are in a day?
Can I convert milliseconds to hours?
When should I avoid average months?
Related digital and time converters
About this time duration converter
Time duration conversion is most reliable when it is treated as elapsed time. A log entry that lasts 90 minutes, a timeout that lasts 3000 milliseconds, or an SLA that lasts 48 hours can be normalized through seconds without needing a calendar.
The page includes average months and years, but labels them carefully. Those rows are useful for estimates and rough comparisons, not for exact date arithmetic where calendar months and time zones matter.
The full table helps users compare adjacent units quickly. A single duration can be copied as a selected result while still showing the assumptions behind longer units.
Who maintains this page
Ownership and review
Written and maintained by the Toolarithm editorial team. No review date is shown without a maintained editorial record. No independent professional review is claimed.
Methodology
Conversion factors are normalized to canonical units and checked in both directions. Exact definitions and offset formulas are preferred over rounded lookup values.
Read the editorial methodologyDates and sources
Review dates change only after a substantive method or content check.
Keep building