Duration Converter

Convert Time Duration Online

A duration converter is an essential tool for anyone who needs to translate time spans between different units such as seconds, minutes, hours, days, weeks, and years. Whether you are calculating project timelines, analyzing performance metrics, or working with time duration values in code, converting between time units accurately saves effort and prevents costly mistakes. Our free online converter handles all common duration formats instantly.

Understanding Time Duration

Time duration represents the length of a time interval, measuring how much time elapses between two points. Unlike timestamps that identify a specific moment, durations describe a span. The concept seems simple on the surface, but the relationships between time units introduce surprising complexity. A minute is always 60 seconds, and an hour is always 60 minutes, but beyond that, the relationships become less uniform.

A day is typically 86,400 seconds (24 hours), but days affected by daylight saving time transitions can be 23 or 25 hours long. A month can be 28, 29, 30, or 31 days depending on which month and whether it is a leap year. A year is usually 365 days but is 366 days in a leap year. These irregularities mean that converting durations involving days, months, or years requires careful consideration of context and conventions.

In computing, durations are commonly expressed in milliseconds, seconds, or as composite values like "2 hours 30 minutes 15 seconds." The ISO 8601 standard defines a duration format using the pattern PnYnMnDTnHnMnS, where P marks the beginning of the duration, and each component is preceded by its value. For example, P1Y2M3DT4H5M6S represents a duration of 1 year, 2 months, 3 days, 4 hours, 5 minutes, and 6 seconds. This standardized format is used in many APIs and data interchange formats.

Understanding Duration Units

Time duration units form a hierarchical system where each larger unit contains a fixed number of smaller units, at least up to the level of days. The base unit in the International System of Units (SI) is the second, defined since 1967 as the duration of 9,192,631,770 periods of the radiation corresponding to the transition between two hyperfine levels of the ground state of the cesium-133 atom. All other time units are derived from this precise definition.

The standard relationships between common time units are well established. One minute equals 60 seconds. One hour equals 60 minutes or 3,600 seconds. One day equals 24 hours or 86,400 seconds. One week equals 7 days or 604,800 seconds. These relationships are exact and universal, making conversions between these units straightforward multiplication or division operations.

Larger units introduce variability. A month is conventionally treated as 30 days (2,592,000 seconds) for duration calculations, though actual calendar months range from 28 to 31 days. A year is conventionally treated as 365 days (31,536,000 seconds) or sometimes 365.25 days (31,557,600 seconds) to account for leap years. These conventions are approximations, and the appropriate choice depends on the context. For precise calculations spanning specific calendar periods, it is better to work with exact dates rather than approximate duration conversions.

How the Conversion Works

Duration conversion between time units relies on the fixed mathematical relationships between those units. The process involves either multiplying (when converting from larger to smaller units) or dividing (when converting from smaller to larger units) by the appropriate conversion factor. For composite durations, each component is converted separately and the results are summed.

When working with specific dates rather than abstract durations, our date to Unix timestamp converter can help you determine the exact number of seconds between two calendar dates. For calculating the difference between times in different zones, the time difference calculator accounts for UTC offsets automatically. You may also find the online Base64 encoding tool useful when you need to encode duration values for transmission in APIs or data payloads.

Conversion Formula

The core conversion formulas between common time duration units are based on these exact relationships:

Seconds to Minutes: minutes = seconds / 60

Seconds to Hours: hours = seconds / 3,600

Seconds to Days: days = seconds / 86,400

Minutes to Hours: hours = minutes / 60

Hours to Days: days = hours / 24

Days to Weeks: weeks = days / 7

Days to Years (approximate): years = days / 365.25

For composite duration conversion, the process works by first normalizing the entire duration to the smallest unit (typically seconds), then converting to the target unit. For example, to convert "2 hours 30 minutes 45 seconds" to total minutes: first convert everything to seconds (2 x 3600 + 30 x 60 + 45 = 9045 seconds), then divide by 60 to get 150.75 minutes.

The reverse process, converting a single unit value to a composite representation, uses successive division with remainders. To convert 9045 seconds to hours, minutes, and seconds: 9045 / 3600 = 2 hours with remainder 1845; 1845 / 60 = 30 minutes with remainder 45 seconds. The result is 2 hours, 30 minutes, 45 seconds.

Practical Applications

Project Management: Project managers frequently need to convert between time duration units when planning schedules and tracking progress. A task estimated at 120 hours needs to be expressed in work days (typically 15 days at 8 hours per day) or work weeks (3 weeks) for scheduling purposes. Sprint durations, milestone intervals, and resource allocation calculations all require fluent conversion between hours, days, and weeks. Accurate duration conversion prevents scheduling errors that can cascade through an entire project timeline.

Performance Monitoring: Application performance metrics are often measured in milliseconds but need to be reported in more meaningful units. A database query that takes 45,000 milliseconds is more intuitively understood as 45 seconds or 0.75 minutes. Server uptime of 7,776,000 seconds is more meaningful when expressed as 90 days. Monitoring dashboards and alerting systems routinely convert between time units to present metrics in the most appropriate scale for human interpretation.

Video and Audio Production: Media professionals work with durations constantly. A podcast episode might be 3,720 seconds long, which is more usefully expressed as 1 hour and 2 minutes. Video editors need to convert between frames, seconds, and timecode formats. Music producers work with beats per minute and need to calculate the duration of measures in seconds. The time duration converter simplifies these calculations across the production workflow.

Scientific Research: Scientists across many disciplines work with time durations spanning enormous ranges. A chemical reaction might complete in 0.003 seconds (3 milliseconds), while a geological process might span 31,557,600,000 seconds (approximately 1,000 years). Expressing these durations in appropriate units is essential for clear communication in research papers, presentations, and data analysis. Physicists, chemists, biologists, and earth scientists all benefit from quick and accurate duration conversion.

Fitness and Health: Athletes and fitness enthusiasts track workout durations, rest intervals, and recovery periods in various units. A marathon finishing time of 14,400 seconds translates to 4 hours. Interval training might specify 90-second work periods with 30-second rest periods, and calculating total workout duration requires summing these intervals across multiple sets. Sleep tracking applications convert between hours and minutes to present sleep duration data in the most readable format.

Time Duration Reference Table

Duration	Seconds	Minutes	Hours	Days
1 Minute	60	1	0.0167	0.000694
1 Hour	3,600	60	1	0.0417
1 Day	86,400	1,440	24	1
1 Week	604,800	10,080	168	7
30 Days	2,592,000	43,200	720	30
90 Days	7,776,000	129,600	2,160	90
180 Days	15,552,000	259,200	4,320	180
365 Days	31,536,000	525,600	8,760	365
365.25 Days	31,557,600	525,960	8,766	365.25
10 Years	315,576,000	5,259,600	87,660	3,652.5

Frequently Asked Questions

How many seconds are in a day?

There are exactly 86,400 seconds in a standard day. This is calculated as 24 hours multiplied by 60 minutes per hour multiplied by 60 seconds per minute (24 x 60 x 60 = 86,400). This value is used universally in computing, science, and engineering as the standard length of a day in seconds. However, it is worth noting that days affected by daylight saving time transitions may effectively be 23 or 25 hours long from a civil time perspective, and days containing a leap second are technically 86,401 seconds long in UTC.

How do I convert milliseconds to a readable duration format?

To convert milliseconds to a human-readable format like "X hours Y minutes Z seconds," first divide by 1,000 to get total seconds. Then use successive division: divide total seconds by 3,600 to get hours (keep the integer part), divide the remainder by 60 to get minutes (keep the integer part), and the final remainder is the seconds. For example, 5,432,100 milliseconds equals 5,432.1 seconds, which breaks down to 1 hour (3,600 seconds), 30 minutes (1,800 seconds), and 32.1 seconds.

What is the ISO 8601 duration format?

The ISO 8601 duration format uses the pattern PnYnMnDTnHnMnS, where P is the duration designator that starts the expression, Y represents years, M represents months (before T) or minutes (after T), D represents days, T is the time designator separating date and time components, H represents hours, and S represents seconds. For example, P2DT3H30M means a duration of 2 days, 3 hours, and 30 minutes. Components with a value of zero can be omitted, so P1H is not valid but PT1H correctly represents one hour. This format is used in XML Schema, many web APIs, and calendar applications.

How many hours are in a year?

A standard non-leap year contains 8,760 hours (365 days x 24 hours). A leap year contains 8,784 hours (366 days x 24 hours). For average calculations that account for the leap year cycle, the commonly used value is 8,766 hours per year, based on the average year length of 365.25 days. This average value is frequently used in engineering, energy calculations (such as kilowatt-hours per year), and capacity planning where precision to the individual hour is not critical but a reasonable annual estimate is needed.

Why is converting months and years to seconds imprecise?

Months and years are not fixed-length time units. A month can be 28 days (February in a non-leap year), 29 days (February in a leap year), 30 days (April, June, September, November), or 31 days (January, March, May, July, August, October, December). Similarly, a year is 365 days in common years and 366 days in leap years. When a duration converter says "1 month = 2,592,000 seconds," it is using the convention of 30 days per month, which is an approximation. For precise calculations involving specific calendar periods, you should use exact date arithmetic rather than approximate duration conversion.

How do programming languages handle duration conversion?

Most modern programming languages provide built-in support for duration manipulation. Python offers the timedelta class in the datetime module, which supports arithmetic with days, seconds, and microseconds. JavaScript does not have a native duration type but libraries like Luxon and date-fns provide comprehensive duration handling. Java introduced the Duration and Period classes in Java 8, where Duration handles time-based amounts (hours, minutes, seconds) and Period handles date-based amounts (years, months, days). Go provides the time.Duration type measured in nanoseconds with convenient constants like time.Hour and time.Minute.

What is the difference between duration and time interval?

A duration is an abstract length of time without reference to specific start or end points. For example, "3 hours" is a duration. A time interval (or time period) is a specific span between two defined points in time, such as "from 9:00 AM to 12:00 PM on February 25, 2026." While both represent amounts of time, intervals are anchored to the calendar and can be affected by time zone changes and daylight saving transitions, whereas durations are purely abstract quantities. Converting between the two requires knowing the specific start or end point of the interval.

How do I convert between work hours and calendar days?

Converting between work hours and calendar days requires knowing the number of working hours per day, which varies by organization and country. The most common convention is 8 working hours per day and 5 working days per week, giving 40 hours per work week. Under this convention, 160 work hours equals 20 work days (approximately one calendar month). However, some countries use different standards: France mandates 35 hours per week, while some industries operate on 12-hour shifts. Always clarify the working hours convention before performing this type of conversion to avoid scheduling errors.