Time conversion is simple at small scales and slippery at large ones. Seconds, minutes, hours, days, and weeks convert with exact factors everyone knows: 60 seconds per minute, 60 minutes per hour, 24 hours per day, 7 days per week. Below the second, milliseconds (10^-3), microseconds (10^-6), and nanoseconds (10^-9) serve computing and science. The slipperiness starts at months and years: a month is 28 to 31 days, so converters use the average month of 30.436875 days (365.25/12), and a year is 365 days — or 365.25 accounting for leap years, the figure astronomers and long-range planners use.
The common conversions: 1 hour = 3,600 seconds; 1 day = 86,400 seconds; 1 week = 604,800 seconds; 1 average year = 31,557,600 seconds (about π x 10^7, a handy approximation physicists love). Going the other way, 100,000 seconds is 27.78 hours — just over a day and three hours — the kind of figure that appears in project estimates and server uptimes.
Practical uses cluster around billing, planning, and payroll: converting 2.5 hours to 150 minutes for a timesheet, turning a 90-day project into 12.86 weeks for a Gantt chart, or expressing a machine's 10,000-hour service interval as 1.14 years of continuous operation (10,000 / 8,766 = 1.141, using 8,766 hours per average year). Note that time zones and daylight saving are offsets, not conversions — this calculator converts durations, not clock times.