Article — Day Converter - Days to Hours, Weeks, Years
The Day Converter
A day equals exactly 24 hours, 1,440 minutes, or 86,400 seconds. In larger units, 1 day = 1/7 of a week = ~1/30 of a month = 1/365.2425 of a Gregorian year. Day-to-seconds, day-to-minutes, and day-to-hours are exact; day-to-months and day-to-years are calendar averages.
Time looks straightforward until you start to convert across scales. Seconds, minutes, and hours roll cleanly into a day. Days into weeks, also clean — 1 week is exactly 7 days. But days into months hits a wall (28 to 31 days per month), and days into years hits another (365 or 366 depending on whether the year is a leap). This converter handles both clean and approximate cases, and the article below explains where each one is exact and where it is not.
Why we convert days at all
The day is the human-scale time unit. Our brains plan in days for work, sleep, exercise, and travel. Computers, on the other hand, plan in seconds. Calendars and contracts plan in months and years. Astronomers plan in Julian dates. Every interesting time-aware system needs to translate between these scales, which is the whole job of a day converter.
The conversion factors are simple in principle but pick up subtleties at the year boundary. The international system of units defines the second as exactly 9,192,631,770 cycles of a caesium-133 atomic transition, and every shorter or longer unit (minute, hour, day) is built from integer seconds. That gives day-to-second and day-to-hour their exactness.
The modern definition of the second has nothing to do with the rotation of Earth. It is defined by an atomic transition in caesium-133, which is more stable than Earth's spin. UTC occasionally adds a "leap second" to keep clock time roughly in sync with the slowing rotation of the planet.
Days to hours, minutes, seconds
The three smallest day conversions are exact and the easiest to remember.
1 day = 24 hours1 day = 1,440 minutes1 day = 86,400 seconds1 week = 604,800 secondsThe 86,400 number appears so often in computing that experienced programmers memorise it. Many systems store time as the number of seconds elapsed since 1 January 1970 — the Unix epoch — and conversions to and from human dates lean on the 86,400-second day as a building block.
Days to weeks and months
Days to weeks is the easiest larger conversion: one week is exactly seven days. Days to months is harder, because months are not uniform. February has 28 days (29 in a leap year), April–June–September–November have 30, the rest have 31. The average over a year is 30.4375 days per month, but month-by-month spans differ by up to 11 percent.
This converter uses 30 days per month for its month output. It is a reasonable default for short-term planning ("90 days" ≈ "3 months"), and the visible difference is small for spans under a year. For exact spans, look up the specific months involved.
- February = 28 days (29 in leap year)
- April, June, September, November = 30 days each
- January, March, May, July, August, October, December = 31 days each
- Total year = 365 (or 366) days
- Average month = 30.44 days over a non-leap year
- Average month = 30.4375 days using the Gregorian 365.25 figure for the same purpose
Days to years and leap years
The Gregorian year averages 365.2425 days. The exact value comes from the leap-year rule: every year divisible by 4 is a leap year, except century years that are not divisible by 400. Across 400 years there are exactly 97 leap years, giving (400 × 365 + 97) ÷ 400 = 365.2425.
This converter uses 365.2425 for days-to-years output. Use 365 if you want a non-leap year exactly, or 366 for a leap year — both are equally valid depending on the context. The 365.2425 average is the right default for spans longer than a few years.
Julian vs Gregorian year length
The Julian calendar (still used by some Orthodox churches for liturgical dates) uses a simpler rule: every fourth year is a leap year, no exceptions. That gives 365.25 days per year. The Gregorian reform of 1582 added the century rule (years divisible by 100 are not leap years unless also divisible by 400), shaving 0.0075 days per year off the Julian average.
The difference is small day-to-day (about 11 minutes per year), but it accumulates. By 1582 the Julian year had drifted 10 days ahead of the seasons, and Pope Gregory XIII dropped those 10 days in one stroke — 4 October 1582 was followed by 15 October 1582 in Catholic Europe. Protestant Britain held out until 1752; Russia until 1918.
If you ever see a date converter that disagrees with another by a small number of days for very old events, the difference is almost always Julian vs Gregorian dating. For events before 1582 in most of Europe, both calendars produce different day numbers for the same physical day.
The day converter in software and time math
Software date libraries deal with days constantly. The Unix epoch — 1 January 1970 UTC — counts seconds, and every higher-level operation (adding days, finding age in years, computing weekdays) leans on day-level arithmetic. The 86,400-second day is the bridge between low-level integer time and high-level calendar display.
Modern code increasingly handles leap years and Gregorian rules through libraries (date-fns, Luxon, Python's datetime, Java's java.time) rather than by hand. The converter on this page does the same — uses Gregorian averages for the year output so that, for example, 365 days reads as 0.9993 years and 730 days reads as ~2 years.
A short history of day-length standards
Egyptian astronomers split day and night into 12 "hours" each by 2,000 BCE, producing the 24-hour day that survived all subsequent reforms. The Babylonians contributed base-60 minutes and seconds, which carried into Greek, Arabic, and finally European timekeeping. By the medieval period the 24 × 60 × 60 second hierarchy was universal in the West.
The atomic redefinition of the second in 1967 untied the day from Earth's rotation. The "mean solar day" still averages 86,400 seconds, but the actual rotation is variable enough that UTC needs occasional leap seconds (added at the end of June or December) to keep clock time aligned with astronomical time. There have been 27 leap seconds since 1972; the next is scheduled to depend on long-term measurements of Earth's spin.
Common day-conversion mistakes
Most day-conversion errors come from treating averages as exact spans or missing leap days. A few patterns repeat across spreadsheets and code:
- 30 days = 1 month — usually fine for short ranges, wrong for exact dates
- 52 weeks = 1 year — close (52 × 7 = 364), but a year is 52.18 weeks
- 365 days = 1 year always — wrong every fourth year
- using 365.25 in modern code — Gregorian average is 365.2425; for spans under ~100 years the difference is invisible, for longer spans it accumulates
- summing days across DST boundaries — a day is not always 86,400 seconds in local time; some days are 23 or 25 hours due to daylight saving
- treating month boundaries as 30 days — adding 30 days to 31 January in code rarely lands on the same calendar day in February
On the day clocks spring forward, local time gets 23 hours of actual elapsed time even though the calendar marks one full day. On the autumn day clocks fall back, it gets 25 hours. Code that adds seconds blindly across these days will drift. For most scheduling work, this is a corner case; for billing or compliance, it is a known pitfall.