What it converts
Converts fixed elapsed intervals from milliseconds through seven-day weeks using the second as base.
ELAPSED TIME WORKSPACE
Convert fixed elapsed intervals among milliseconds, seconds, minutes, hours, 24-hour days, and seven-day weeks without applying a calendar.
Conversion result
Load the reviewed example or enter a value to compare every available duration unit unit.
What this tool delivers
This page rescales elapsed time; it does not shift a timestamp, compare zones, count business days, or decide how long a calendar month lasts.
Converts fixed elapsed intervals from milliseconds through seven-day weeks using the second as base.
A non-negative duration, its source unit, the required destination unit, and an appropriate output precision.
A selected interval, second-based equation, equivalent duration table, and CSV record.
Calculation method
The input is multiplied by seconds per source unit and divided by seconds per destination unit. One minute is 60 seconds, one hour is 3,600 seconds, one displayed day is 86,400 seconds, and one displayed week is 604,800 seconds.
Review the BIPM SI definition of the secondQuick answers
This converter handles elapsed-duration units, so its day is exactly 86,400 seconds and its week is seven such days. A local civil day can appear shorter or longer across a daylight-saving transition. For appointments or timestamps, use a timezone-aware date calculation with explicit start and end instants instead.
Not responsibly without a convention. Calendar months contain different numbers of days, years may include leap days, and financial products sometimes impose separate day-count rules. This page excludes months and years rather than inventing an average. Supply actual dates or a named contractual convention in a calendar-aware workflow when those periods matter.
No. The factors describe fixed unit relationships and do not reconstruct a historical UTC timeline. Leap-second handling depends on the timestamp scale, data source, and system behavior. If sub-minute timing accuracy matters, retain the original time standard, timestamp metadata, synchronization method, and uncertainty rather than relying on a unit conversion alone.