Use this duration converter to convert nanoseconds, microseconds, milliseconds, seconds, minutes, hours, days, weeks, months, and years at once.
Last updated
Duration converter Use this duration converter to restate the same elapsed time across nanoseconds, microseconds, milliseconds, seconds, minutes, hours, days, weeks, months, and years while keeping exact elapsed units separate from average calendar estimates.
Common presets
Exact elapsed units versus average calendar units
Milliseconds through weeks stay exact because they are fixed elapsed-time relationships. Months and years are shown using average Gregorian lengths, so they are useful for rough planning but not for exact date-to-date answers.
Quick checkpoints
1 hour = 60 minutes = 3,600 seconds. 1 day = 24 hours. 1 week = 7 days. 1 average year = 365.2425 days.
When to switch tools
Use this page when you already know the elapsed quantity and need it in another unit. Use a date difference or time duration calculator when the answer depends on real calendar boundaries, leap years, business days, or clock times.
Enter a value Provide a duration to convert it across elapsed-time and calendar-estimate units.
Duration converter: seconds, minutes, hours, days, weeks, months, and years explained
A duration converter expresses one elapsed time in multiple units at once. It is useful when you need to move between machine-friendly values such as nanoseconds, microseconds, milliseconds, and seconds, human-friendly units such as hours and days, and rough calendar estimates such as months or years.
Elapsed time and calendar time are not the same thing
Minutes, hours, days, and weeks are fixed elapsed-time relationships once the second has been defined. That makes them ideal for logging, countdowns, runtimes, schedules, and service-level targets where you are measuring a span of time rather than working with real dates.
Months and years are different. Calendar months vary in length, and years can be 365 or 366 days. A duration converter therefore has to use average month and year values when it shows those outputs. That gives you useful estimates, but it does not replace exact date arithmetic.
How duration conversion works
The cleanest method is to translate the source value into seconds first and then divide by the target unit length. That is why an hour becomes 3,600 seconds, a day becomes 86,400 seconds, and a week becomes 604,800 seconds without ambiguity. Subsecond values follow the same pattern: 1 millisecond is 1,000 microseconds, and 1 microsecond is 1,000 nanoseconds.
For month and year estimates, the converter uses Gregorian averages: 365.2425 days per year and approximately 30.4369 days per month. Those values are good for planning and scale comparisons, but they should not be used when you need an exact calendar answer.
1 h = 60 min = 3,600 s
Hours, minutes, and seconds are exact elapsed-time relationships built from the second.
1 day = 24 h = 86,400 s
Day-level duration conversion stays exact when you are converting elapsed time rather than calendar dates.
1 year (avg) = 365.2425 days
Average Gregorian year length used for approximate month and year conversions.
Worked examples
A 90-minute meeting is 5,400 seconds, 1.5 hours, and 0.0625 days. In normalized fixed units, it is 1 hour and 30 minutes. An 8-hour shift is 28,800 seconds and one third of a day. A 30-day plan is 720 hours, about 4.29 weeks, and roughly 0.99 average months. These are exactly the kinds of translations a duration converter handles well.
What it does not do is decide how many calendar months exist between two dates or how many business days remain before a deadline. Those questions depend on real dates, leap years, and sometimes weekends or holidays, which is why they belong in date-specific tools.
Use seconds and milliseconds for technical logs or code runtimes.
Use minutes and hours for scheduling, billing, and study blocks.
Use days and weeks for planning windows and countdowns.
Treat months and years as estimates unless you are using exact calendar logic.
When this converter is the right tool
Use a duration converter when you already know the elapsed quantity and simply need it in another unit. That includes workout duration, media runtime, battery charging time, sprint length, and support-response targets written in different units.
Use a date-difference calculator instead when the question starts with two dates on a calendar. That route is the only reliable way to handle leap days, month boundaries, or business-day rules correctly.
Why a duration converter is different from a time duration calculator
A duration converter answers a unit-conversion question: if you already know the elapsed span, how should that same duration be expressed in seconds, minutes, hours, days, weeks, months, or years? That makes it a strong fit for turning a media runtime into seconds, a shift length into hours, or a sprint duration into days and weeks.
A time duration calculator answers a calendar question: how much time exists between two actual dates or clock times? That second workflow has to care about month boundaries, leap years, and sometimes daylight saving or business-day rules. The two tools are related, but they solve different user intents.
Where month and year conversions can mislead you
Exact elapsed units stay exact because they are fixed ratios. One hour is always 60 minutes, and one week is always 7 days in elapsed-time conversion. Months and years are different because the calendar does not keep them at one fixed length. That is why a good time unit converter has to label them as averages rather than treating them as interchangeable with exact day counts.
For example, 30 days is exactly 720 hours and exactly 4.2857 weeks, but it is only about 0.9856 average months. That does not mean the conversion is wrong. It means the month output is an average Gregorian estimate, not a promise that every 30-day span will cross one real calendar month boundary.
Common duration conversion workflows
Technical and operational workflows often start with seconds or milliseconds because logs, APIs, and device traces store elapsed time in base units. A duration converter helps translate those raw values into minutes, hours, or days so they are easier to review with human teams.
Planning workflows often start the other way round. A team may know it has a 90-minute workshop, an 8-hour shift, a 14-day sprint, or a 30-day plan. The converter makes it easy to restate those blocks for scheduling software, service-level reporting, billing notes, or communication with stakeholders who prefer another unit.
Convert milliseconds and seconds for telemetry, software runtime, and network timing.
Convert minutes and hours for meetings, workouts, charging windows, or media runtimes.
Convert days and weeks for project planning, countdowns, or notice periods.
Use average months and years only for rough long-range planning, not exact calendar arithmetic.
Normalized duration and copy-ready formats
Many competing time converters stop at a table of equivalent units. A normalized duration is different: it decomposes the same elapsed span into fixed units such as weeks, days, hours, minutes, seconds, milliseconds, microseconds, and nanoseconds. That is the form people usually need when they want to read 90 minutes as 1 hour 30 minutes instead of only 1.5 hours.
Copy-ready formats help when the converted value has to move into another system. HH:MM:SS is convenient for media runtimes, timers, and spreadsheets. Total seconds and total milliseconds are common in APIs and logs. The elapsed ISO-style output keeps fixed days and clock units visible while avoiding average months and years.
Frequently asked questions
Why does the converter show months and years as averages?
Because calendar months and years are not fixed elapsed durations. Months vary in length, and leap years add an extra day. The converter therefore uses average Gregorian values for quick planning estimates.
How many seconds are in a day?
A day contains 86,400 seconds because 1 day = 24 hours, 1 hour = 60 minutes, and 1 minute = 60 seconds. Multiplying 24 by 60 by 60 gives 86,400.
Should I use this converter for exact date differences?
Only if you already know the elapsed duration. If you need the exact difference between two calendar dates, use a date-difference calculator so leap years, month lengths, and business-day rules are handled correctly.
Is a duration converter the same as a time duration calculator?
No. A duration converter restates one known elapsed span in different units, while a time duration calculator works from actual dates or times and has to account for real calendar boundaries.
Why does 30 days not equal exactly 1 month here?
Because the converter treats months as average Gregorian months, about 30.4369 days each. A 30-day duration is therefore slightly less than one average month. Real calendar months vary between 28 and 31 days, so exact month counts belong in date-based tools.
When should I convert to milliseconds instead of seconds?
Use milliseconds when the duration is short enough that second-level reporting would hide meaningful detail. That is common in runtime metrics, animation timing, hardware latency, telemetry, and response-time monitoring.
When do microseconds or nanoseconds matter?
Microseconds and nanoseconds matter for high-resolution telemetry, hardware timing, database traces, code profiling, and scientific measurements. They are usually too small for everyday scheduling, but they prevent short technical durations from being rounded into zero seconds.
What is a normalized duration?
A normalized duration breaks one elapsed span into the largest fixed units first. For example, 90 minutes can be shown as 1 hour and 30 minutes. This is different from average month or year estimates, which depend on calendar assumptions.
What is the safest unit to use for exact elapsed planning?
Seconds through weeks are the safest because they are fixed elapsed-time relationships. Once you move into months and years, the outputs become average planning estimates rather than exact calendar counts.
