Days to hours converter

What This Tool Does

This converter translates a number of days into the matching number of hours — and in both directions at once. The two input fields are coupled live: typing into one updates the other without a button press. Alongside, the same duration is rendered as D:HH:MM, so sprint plans and shift rosters read in one view.

Pure-client. Every value stays inside your browser. No server, no tracking, no cookie wall. The tool works offline as soon as the page has loaded once.

Why Does It Need a Tool at All?

“Times twenty-four” is head math — when the number is round. As soon as the number is not round, friction starts. How many hours is 3.75 days? How many days is 287 hours? What does a sprint board entry of 4:18:00 mean? The converter answers all three in one view and saves the mental ping-pong between decimal days and D:HH:MM notation.

Decimal days — the sprint-planning standard

Scrum teams and project-management tools count in decimal days: 1.5 d, 0.5 d, 3.25 d. The reason is summation math — story points × velocity gives the sprint workload directly. Two tickets at 1.5 days plus one ticket at 0.5 days come to exactly 3.5 days. Filing the same workload as 3:12:00 forces hours-to-decimal conversion first — an extra failure point in velocity tracking.

D:HH:MM — the shift-and-roster standard

Shift schedules, on-call rosters and standby lists write durations in D:HH:MM notation. “Standby from Friday 18:00 to Sunday 06:00” reads as 1:12:00 or 1.5 days. On a sprint board the same workload lands as 1.5 d — and the step between is exactly the conversion the right-hand block shows live.

Important: 24 h is not a work-day

A calendar day is 24 hours. A full working day under §3 ArbZG is only 8 hours of working time, extendable to 10 in exceptions. The use-case table separates the two: the calendar value “1 d → 24 h” applies to calendar durations such as holiday, sick leave and delays; the work-day value “1/3 d → 8 h” applies to working-time arithmetic. Conflating the two leads to 168-hour weeks instead of the correct 40-hour working week.

Which Use Cases Does the Tool Surface?

The table groups the most common search intents into a single overview — from EU passenger rights through week structures to the German minimum holiday under the Federal Holiday Act.

Minimum holiday under §3 BUrlG

The German Federal Holiday Act §3 BUrlG names 24 working days of paid minimum holiday per calendar year, based on a six-day working week (Monday to Saturday). Translated to a five-day working week, that is 20 working days. Either way it equals four calendar weeks or 28 calendar days — 672 hours of calendar time. Many collective agreements and contracts grant more than the statutory minimum, often 30 days on a five-day week.

Sick leave and continued pay

Initial medical sick notes in Germany typically cover up to two weeks under the AU-Richtlinie — 14 days or 336 hours of calendar time. §3 EFZG (Entgeltfortzahlungsgesetz) obliges the employer to continued pay for up to six weeks — 42 calendar days or 1,008 hours. Beyond that, statutory health insurance pays Krankengeld.

EU air-passenger delays beyond 3 hours

EU Regulation 261/2004 grants air passengers a flat compensation between 250 € and 600 € when arrival delay exceeds three hours, depending on flight distance. Three hours equals 0.125 days or 0:03:00 in D:HH:MM. Cancellations without sufficient advance notice fall under the same flat amounts.

Rail-passenger refunds from 1 hour

EU regulation 1371/2007 article 17 mandates a 25-percent refund for one-hour delays in long-distance rail and 50 percent at two hours. One hour equals 1/24 day or 0:01:00 in D:HH:MM. Regional rail in Germany follows separate national thresholds under the Fahrgastrechte-Verordnung.

Week and working-week structures

A full calendar week is 7 × 24 = 168 hours. A five-day working week covers 120 hours of calendar time, of which a full-time contract typically counts 40 hours as working time. A weekend is 48 hours. Banking conventions use a 30-day month (720 hours), even though calendar months vary between 28 and 31 days.

Which Mental Rule of Thumb Works Without a Tool?

Days times twenty-four — for round numbers, head math is enough. 5 × 24 = 120. For half days, the rule “half a day = 12” helps: 5.5 d = 5 × 24 + 12 = 132. Odd values break the mental shortcut — 3.7 days is 88.8 hours, and no one verifies that without a calculator.

In reverse — hours to days — the friction is worse. 287 hours? Divided by 24 it is 11.958 days or 11:22:59 in D:HH:MM. Anyone summing multiple Excel rows needs that precision at latest when matching against the sprint plan.

Why Use a Coupled Live Converter Instead of a Table?

A static conversion table only covers discrete values. Whole and half days appear, but odd values like 3.73 d or 89 h do not. As soon as a question mentions an unusual value, head math starts. The coupled live converter handles any value instantly, both directions, no submit click. Alongside, the D:HH:MM readout updates in lockstep — saving the mental step a bare number cannot.

Pure-client also means the values never leave your device. No server logs, no cookies, no cookie wall. The input tolerates either decimal style (German comma, English period) regardless of locale.

What Other Time Tools Are Related?

More tools from the kittokit ecosystem that fit the topic:

• Hours to Minutes — hours to minutes with decimal ↔ HH:MM:SS and a working-time table.
• Years to Days — years to days with three year-length modes and life-expectancy anchors.
• Months to Days — months to days with Julian average and 30-day banking model.
• Working Days Calculator — workdays between two dates, German holidays included.