Days to Seconds (d to s)
Last updated:
Days-to-seconds conversions translate human-readable durations into the second-precision granularity required by software systems, billing engines, scientific instruments, and timing-critical regulations. Days are the natural unit for human reasoning about elapsed intervals above an hour — a 30-day billing cycle, a 7-day medical observation window, a 365-day calendar year — but downstream computation needs the second figure for monotonic clock arithmetic, per-second pricing, sub-second event ordering, and regulatory deadlines measured in seconds. The factor is exact: one day equals exactly 86,400 SI seconds, with leap-second adjustments affecting UTC display only and not the SI second itself. For interval calculations the leap second is a presentation concern handled by the calendar layer, not by the conversion factor.
How to convert Days to Seconds
Formula
s = d × 86400
To convert days to seconds, multiply the day figure by 86,400. The factor is exact since one day equals exactly 86,400 SI seconds by international convention, and the SI second is unchanged by UTC leap-second insertions. For mental work, "round to 90,000 and subtract 4%" gives a quick estimate accurate enough for back-of-envelope cloud-cost or capacity-planning calculations. For SLA-budget contracts, regulatory deadlines, billing reconciliation, and scientific-deployment data-volume estimates, use the full 86,400 multiplier exactly because compounding across long intervals (a 90-day window, a year-long deployment) makes any rounding visible at the audit or reconciliation layer where contractual tolerances are checked.
Worked examples
Example 1 — 1 d
One day equals 1 × 86,400 = 86,400 seconds. This is the canonical reference number for converting between days and seconds and appears in every timing-system constant table, scheduling library, and billing engine. The figure ignores leap-second insertions, which are UTC presentation adjustments rather than changes to the SI second itself.
Example 2 — 30 d
Thirty days equals 30 × 86,400 = 2,592,000 seconds — the figure cloud-pricing engines use for monthly cost computation. The 30-day month is a billing convention rather than a calendar reality (which alternates 28, 29, 30, and 31 days), so cloud invoices always show 30 × 86,400 seconds for the month even when the actual elapsed calendar interval is 28 or 31 days.
Example 3 — 365 d
Three hundred sixty-five days equals 365 × 86,400 = 31,536,000 seconds, a non-leap year. SaaS annual subscriptions, regulatory reporting periods, and clinical-trial primary-endpoint windows standardise on this figure regardless of whether the actual calendar year is a leap year. The 86,400-second discrepancy in leap years is handled at the calendar-system layer rather than re-derived in the seconds-counter.
d to s conversion table
| d | s |
|---|---|
| 1 d | 86400 s |
| 2 d | 172800 s |
| 3 d | 259200 s |
| 4 d | 345600 s |
| 5 d | 432000 s |
| 6 d | 518400 s |
| 7 d | 604800 s |
| 8 d | 691200 s |
| 9 d | 777600 s |
| 10 d | 864000 s |
| 15 d | 1296000 s |
| 20 d | 1728000 s |
| 25 d | 2160000 s |
| 30 d | 2592000 s |
| 40 d | 3456000 s |
| 50 d | 4320000 s |
| 75 d | 6480000 s |
| 100 d | 8640000 s |
| 150 d | 12960000 s |
| 200 d | 17280000 s |
| 250 d | 21600000 s |
| 500 d | 43200000 s |
| 750 d | 64800000 s |
| 1000 d | 86400000 s |
| 2500 d | 216000000 s |
| 5000 d | 432000000 s |
Common d to s conversions
- 1 d=86400 s
- 7 d=604800 s
- 14 d=1209600 s
- 30 d=2592000 s
- 60 d=5184000 s
- 90 d=7776000 s
- 180 d=15552000 s
- 365 d=31536000 s
- 730 d=63072000 s
- 1825 d=157680000 s
What is a Day?
The day (d) is exactly 86,400 seconds (24 hours × 3600 seconds per hour) by SI civil-day definition, fixed by the 1967 atomic-clock SI second standard. The recognised symbol is "d" (lowercase) under ISO 80000-3 conventions. The day is not part of the SI base units but is recognised by NIST and BIPM as a non-SI unit accepted for use with the SI. The civil-day at 86,400 s differs slightly from the astronomical solar-day (which varies seasonally due to Earth's elliptical orbit, averaging 86,400.002 SI seconds) and from the sidereal-day (86,164.09 SI seconds, the rotation period relative to distant stars). The IERS leap-second system absorbs the small difference between civil-day and astronomical-day length to maintain UTC within ±0.9 s of UT1. Sub-day precision uses hours, minutes and seconds; super-day precision uses weeks, months and years.
The day as a unit of time has been preserved unchanged across human history as the fundamental natural-time-cycle defined by Earth's rotation relative to the Sun (the solar day, averaging 24 hours over a year due to Earth's elliptical orbit) or relative to distant stars (the sidereal day, exactly 23 hours 56 minutes 4.0905 seconds = 86,164.0905 SI seconds). The civil "day" of timekeeping is fixed at exactly 86,400 SI seconds (24 hours × 60 minutes × 60 seconds) by the 1967 SI second-definition, with the small difference between civil-day length and astronomical-day length absorbed into the leap-second system maintained by the International Earth Rotation and Reference Systems Service (IERS). Leap seconds are inserted (or hypothetically deleted) into UTC at irregular intervals to maintain UTC within ±0.9 seconds of UT1 (a measure of Earth-rotation-based time). Like hours and minutes, the day is not part of the SI base units but is recognised by NIST and BIPM as a non-SI unit accepted for use with the SI in everyday-time-keeping, scheduling, and biological-and-medical contexts.
Everyday timekeeping and calendar systems: every modern calendar (Gregorian, Islamic, Hebrew, Chinese, Persian) denominates dates in days alongside months and years. Civil-time scheduling, meeting-and-event scheduling, and casual time-references all use days universally. Biological-and-medical research: medication-dose intervals (twice daily, once daily, every other day), clinical-trial follow-up schedules (Day 1, Day 7, Day 28 standard timepoints), pregnancy gestational-age tracking (typical 280 days from last menstrual period), and chronic-disease progression monitoring all use days as the natural time-unit for biological processes. Astronomy and space-science: orbital-mechanics calculations (planetary orbital periods in days, satellite-orbit periods in fractions of a day), space-mission-scheduling (Apollo missions in days, Mars-rover-mission time in sols-or-days), and astronomical-observation scheduling all use days as the natural time-unit for celestial-mechanics work. Employment and payroll: salary-quotation systems (US per-day rates for contractors, UK locum-medical-doctor day rates, freelancer day-rate quotations) use the day as the natural employment-time unit. Typical professional contractor day-rate is £400-£800 in the UK; salary-equivalent annual figures translate from per-day rates times typical 230 working days per year (260 weekday-days minus 30 holidays).
What is a Second?
The second (s) is the SI base unit of time, defined since 1967 as exactly 9,192,631,770 periods of the radiation corresponding to the transition between the two hyperfine levels of the ground state of the caesium-133 atom (the Cs-133 hyperfine transition at 9.192631770 GHz). The 2019 SI redefinition preserved this atomic-clock definition. The recognised SI symbol is "s" (lowercase, italics-disambiguated when needed). The second is the foundational unit for all other SI time-related units (the hertz at 1/s, the becquerel at 1/s for radioactive decay, the SI joule via 1 J = 1 N·m and the metre is defined via the speed of light × the second). Atomic clocks based on the caesium-133 transition currently achieve precision better than 1 part in 10^15, with the most-recent optical-lattice atomic clocks (Sr-87, Yb-171) approaching 1 part in 10^18 precision. The second is preserved unchanged across every modern timekeeping context, scientific publication, and engineering specification.
The second has been preserved unchanged in concept since Babylonian astronomy in the third millennium BC, where the day was divided into 24 hours, each hour into 60 minutes, and each minute into 60 seconds — the sexagesimal time-division system that survives globally today. The modern SI second was redefined in atomic terms at the 13th CGPM in 1967 as "the duration of 9,192,631,770 periods of the radiation corresponding to the transition between the two hyperfine levels of the ground state of the caesium-133 atom" at zero magnetic field and at rest at 0 K. The atomic-second definition replaced the older astronomical-second definition (1/86,400 of a mean solar day, since 1820) which was based on Earth's rotation rate and therefore subject to the slow secular slowdown of Earth's rotation due to tidal friction. The 2019 SI redefinition preserved the atomic-second definition as the fundamental SI base unit of time, with all other SI units (metre, kilogram, ampere, kelvin, mole, candela) anchored to defined fundamental constants traceable through the second. The second is the SI base unit of time and the universal primary unit across physics, engineering, atomic-clock metrology, GPS, and modern timekeeping.
Atomic-clock metrology and GPS: every modern atomic clock (caesium-fountain primary clocks at NIST, NPL, PTB, NMIJ; optical-lattice clocks at JILA, Riken, NPL) measures time in seconds with precision better than 1 part in 10^15. GPS satellites carry caesium and rubidium atomic clocks for nanosecond-precision timing, with the GPS-time-system traceable to UTC (Coordinated Universal Time) maintained by atomic clocks at BIPM in Paris. Physics-laboratory and engineering measurement: every modern physics-laboratory measurement involving time denominates in seconds for the SI-canonical primary documentation. Particle-physics decay-rate measurements, fluid-dynamics oscillation-period analysis, mechanical-engineering vibration-period analysis, and atomic-physics-spectroscopy lifetime measurements all use seconds. Sports timing and athletic-record certification: every IAAF-sanctioned (now World Athletics) athletics-meet timing system (Hamamatsu Photonics, Omega Timekeeping, Seiko Sports Timing) measures sport-event times in seconds with millisecond precision (Usain Bolt 100m world record 9.58 s; Eliud Kipchoge marathon world record 2:01:09 = 7269 s). Computing and electronics: every modern computer-system clock denominates time in seconds and sub-second multiples (clock cycles at GHz = billion-per-second, system-time in nanoseconds for high-precision events, kernel-time in microseconds for OS scheduling). Sub-second precision is universally required across modern computing systems.
Real-world uses for Days to Seconds
Cloud cost projection and capacity planning
Cloud-finance teams projecting AWS, GCP, or Azure spend translate workload-duration estimates from days into seconds before multiplying by per-second pricing. A 30-day capacity-reservation projection multiplies 30 × 86,400 = 2,592,000 seconds against the per-second instance rate to produce the monthly cost figure that lands in budget reviews. The day figure is the planning input from the engineering team; the second figure is the calculation input to the pricing engine. Both numbers appear on the same project-cost spreadsheet.
Pharmaceutical and clinical-trial timing
Clinical trial protocols specify dose-administration windows, blood-draw intervals, and observation periods in days for human-readable protocol documents (a 14-day washout, a 90-day primary-endpoint window, a 365-day safety follow-up) but the underlying electronic data-capture systems record timestamps in seconds because per-event timing precision matters for pharmacokinetic modelling. A 14-day washout converts to 1,209,600 seconds, the figure the EDC system uses to compute exact between-event intervals for PK/PD analysis. Regulatory submissions translate back to days for FDA and EMA reviewers.
Scientific deployment timing for long-term experiments
Long-baseline neuroscience recordings, polar-region instrument deployments, deep-sea moorings, and astronomical-survey campaigns plan in days at the proposal stage but execute in seconds at the data-acquisition stage. A 200-day ocean mooring deployment converts to 17,280,000 seconds for the data-storage and battery-budget calculations. The day figure goes into the cruise plan; the second figure goes into the sample-rate × duration calculation that determines acquisition-system disk and power requirements.
When to use Seconds instead of Days
Use seconds when the destination is a billing-engine input, a monotonic-clock arithmetic operation, a scientific data-acquisition timestamp, a real-time monitoring rule, or any pricing model whose granularity is per-second. Stay in days when the audience is human and the duration is above one hour: SLA contracts, project plans, regulatory protocols, customer-facing invoices, and human-readable summaries all stay in days because per-second precision is irrelevant at human-narrative scale. The conversion happens at the boundary between human-readable planning and machine-precision execution, and is typically a one-time calculation per planning cycle rather than a continuous-loop operation. Storing pre-converted second figures introduces precision loss when re-aggregated, so the day figure stays in the contract and the second figure is derived on demand.
Common mistakes converting d to s
- Confusing the 30-day billing month with the actual variable calendar month (28, 29, 30, or 31 days). Cloud-pricing and SaaS-billing engines treat every month as exactly 30 × 86,400 = 2,592,000 seconds for invoice consistency, but underlying compute usage runs on the actual calendar day count. The two figures diverge by up to 86,400 seconds (one day) per billing cycle and need to be reconciled at the audit layer rather than assumed identical.
- Multiplying days by 86,400 in a date-arithmetic context where the source-of-truth is calendar dates rather than elapsed seconds. Daylight-saving-time transitions create 23-hour or 25-hour calendar days in local time, and naive multiplication produces a one-hour offset in any conversion that crosses a DST boundary. Use UTC-based timestamps for the seconds figure and reserve calendar-date arithmetic for the day figure when DST is in scope.
Frequently asked questions
How many seconds in 1 day?
One day equals 86,400 seconds. The figure is exact and excludes leap-second adjustments. Every timing-system constant table, scheduling library, billing engine, and operating-system uptime API uses this exact constant for conversions between days and seconds.
How many seconds in 30 days?
Thirty days equals 2,592,000 seconds. This is the figure cloud-billing engines use for the standardised monthly-cost computation regardless of actual calendar month length. It is also the threshold for many SLA windows, observability-retention defaults, and SaaS subscription auto-renewal events.
How many seconds in a year?
A non-leap year (365 days) equals 31,536,000 seconds. A leap year (366 days) equals 31,622,400 seconds. The 86,400-second difference is one calendar day. Annual billing periods and regulatory reporting cycles typically standardise on 31,536,000 for simplicity, with leap-year adjustments handled at the calendar layer.
Why exactly 86,400 seconds in a day?
Because the SI second is defined by atomic-clock physics (the caesium-133 hyperfine transition) and a day is conventionally divided as 24 hours × 60 minutes × 60 seconds = 86,400. The conventional division predates the SI second by millennia, and the SI second was defined in 1967 to match the existing 86,400-per-day count to within measurement precision. The relationship is therefore exact by definition rather than by physical correspondence.
What about leap seconds — do they affect the days-to-seconds conversion?
No, even though it is the most-asked question on this conversion. The second IERS publishes a leap-second announcement, only the UTC display gets adjusted; SI-second arithmetic continues unchanged underneath. Days-to-seconds conversions should multiply by 86,400 every time. The 27 leap seconds inserted between 1972 and 2017 do not appear anywhere in the conversion factor, and the proposed 2035 abolition of UTC leap seconds will not change the factor either.
Related conversions
Related calculators
Age Calculator
Age in years, months, days, and hours from a birth date to today or any reference date
Date Difference Calculator
Number of days, weeks, months, weekdays, or years between two dates
Watts to kWh Calculator
Energy in kilowatt-hours from power in watts and time in hours
kWh to Watts Calculator
Average power in watts from energy in kWh and time in hours
Compound Interest Calculator
Future value, total interest, and growth from compound interest with optional regular contributions
Simple Interest Calculator
Interest charged or earned without compounding