Free · No account · Works in your browser

Hours Between Dates

Hours and minutes between two date-times

Hours Between Dates

Enter values below, then calculate.

Time Zone Converter Multi-city world clock — EST, PST, IST, UTC & 380+ cities Moon Phases Today's moon phase, lunar calendar, rise/set & zodiac sign Days Between Dates Count calendar days between two dates with weekday breakdown Date Duration Years/months/days between dates — time, workdays, and time zones Date Calculator Add or subtract days, weeks, months, or years Days Until Countdown to any date or upcoming holiday Business Days Workdays between dates, excluding weekends & federal holidays Days Left in Year Countdown to December 31 with day-of-year progress Days Until Month End How many days left in the current month Days Ago What date was N days before today Net 30 / 60 / 90 Invoice due dates for Net 30, 60, 90, and 120 terms When Is Easter Easter Sunday date — Computus algorithm

Hours between dates finds the elapsed time from one date-time to another in hours and minutes, crossing midnight, month boundaries, and daylight saving shifts when zones are set correctly. It answers support SLAs, rental timers, lab notebooks, and expense reports that bill by the hour even when the calendar date changes mid-span.

When hours between dates beats day counts

Choose this tool when both endpoints include a clock time or when sub-day precision matters. Parking garages, equipment rentals, on-call handoffs, and protocol-defined observation windows often span more than one calendar day but charge by the hour. Days between dates truncates to whole days and drops overnight hours you still owe.

Same-day spans — clock-in at 9:00 AM and out at 5:30 PM on one date — may be faster on the hours calculator when you never cross midnight. Use hours between dates when start and end sit on different calendar days or carry explicit zones.

How to use this calculator

Enter start and end datetimes. Add time zones when the inputs come from different cities or when logs store UTC. Calculate and read total hours plus residual minutes. Share the exact parameters in URLs or ticket notes when finance must reproduce a billing dispute.

Payroll systems that expect 7.5 instead of 7:30 can convert through the decimal hours converter after you have the exact minute total. For calendar-day spans without clocks, switch to date duration instead.

Time zones and daylight saving time

Two instants in different zones convert to a common baseline before differencing. Always label zones on exports — London start and Chicago end without labels invite twelve-hour disputes in expense review.

DST spring-forward removes a labeled hour on the civil clock; fall-back repeats an hour. A span that crosses those nights may show twenty-three or twenty-five civil hours for what feels like “one day.” The calculator follows zone rules when datetimes include zone data. Multi-city scheduling context lives on the meeting planner and time zone tools on the time tools hub.

Inclusive endpoints and elapsed versus paid hours

Datetime difference is continuous: from start instant to end instant. There is no separate inclusive toggle like calendar-day tools — the clock defines the span. Document whether your policy measures elapsed wall-clock hours or payable hours after breaks; this page returns elapsed time unless you adjust inputs manually.

Elapsed hours include nights and weekends. Union overtime rules that pay only weekday hours need separate aggregation — feed raw hour totals into a timesheet engine rather than treating this result as net pay. Workday-only spans belong on the business days calculator when the contract excludes weekends entirely.

Partial days and billing rules

Twenty-six hours is one calendar day plus two hours — do not round to one day for hourly contracts. Parking “daily max” rules may cap by calendar date while hourly math governs sub-daily segments; read the contract before merging the two ideas.

Minimum billable increments — quarter hours, half hours — may require rounding after this calculator returns exact minutes. Hotel nightly billing sometimes uses property checkout time; hours beyond checkout can roll an extra night despite a sub-twenty-four-hour clock span.

Worked examples

A support SLA starts at ticket creation datetime and ends at resolution. Enter both timestamps with the same zone as the ticket export. Rounding to whole days hides breaches near the twenty-four-hour threshold — hour precision keeps the SLA honest.

A conference call runs from 09:00 London to 14:00 Chicago on the same civil date with zones set on each field. Attach zone labels to the PDF expense line so finance approves without a rejection loop.

Server maintenance logged in UTC runs from 02:00 UTC Saturday to 08:00 UTC Saturday. Enter UTC on both sides to match internal logs, then convert display labels for a status page that speaks in local time.

Common mistakes

Mixing 12-hour clocks without AM/PM flips results by twelve hours. Using date-only fields when the policy starts at 5:00 PM on the start date undercounts morning hours on the end date. Ignoring DST on spring-forward days produces one-hour disputes that are tedious to unwind in audit.

Correlating logs without normalizing to UTC first creates incident timelines that disagree with customer-facing postmortems. Pick one baseline, calculate here, and publish the same hour total everywhere.

SLA, travel, and long spans

Document whether an SLA uses business hours or continuous clock hours before sharing a number. This page measures continuous hours unless you trim inputs yourself. Layovers spanning midnight count transit hours continuously — enter airport local datetimes and convert consistently.

Mark long spans on the 2026 yearly calendar when reporting overlaps holidays. Aircrew duty limits and clinical observation windows may use regulatory hour definitions that differ from simple datetime difference — confirm FAR, EASA, or protocol rules separately.

On-call rotations logged with handoff timestamps should use the same zone as the paging export. Post-incident reviews cite hour totals here when arguing shift overlap gaps — calendar days alone hide overnight coverage holes.

Logs, rendering, and freight clocks

Video render farms and GPU queues bill continuous hours from job start to completion. Pull timestamps from the queue exporter rather than rounded dates. Freight demurrage and yard detention clocks run the same way — gate-in and gate-out instants from yard logs beat date-only fields.

Clinical case report forms should mirror the timezone documented on protocol-defined observation windows. Mismatch between site entry and this calculation triggers query letters during trial audits.

SLA credits measured in business hours need business days instead of this 24-hour span when contracts exclude nights and weekends.

Warranty claims citing hours between install and failure should attach timezone-stamped logs for 2026 RMA reviews, not rounded day counts alone.

Related tools

See the time tools hub, hours calculator, and date tools hub. Calendar-day spans without clocks use days between dates on the date tools hub.

Frequently asked questions

How are hours between two dates calculated?

The tool converts both date-time inputs to a common instant, subtracts start from end, and expresses the difference in hours and minutes. When zones differ, each side is normalized before differencing so the result reflects true elapsed time, not two unrelated local clocks.

Do time zones affect the hour count?

Yes when start and end use different zones or when logs store UTC while you display local time. Label zones on shared reports. Enter UTC on both fields when correlating server logs so incident timelines match customer-facing postmortems and finance does not reject expense lines.

What happens on daylight saving transition days?

Spring-forward days have twenty-three labeled civil hours; fall-back days have twenty-five. A span crossing those nights may differ from a naive twenty-four-hour guess. Include zone-aware datetimes so the calculator applies the correct offset rules rather than a fixed twelve-hour offset.

Is this the same as days between dates?

No. Days between counts whole calendar days and drops sub-day precision. Hours between keeps clock-level detail across midnight and month boundaries. Use days between for lease nights; use hours between for SLAs, rentals, and billing tied to clock times or timestamps from ticket systems.

Does this count business hours or elapsed hours?

It returns elapsed wall-clock hours from start instant to end instant, including nights and weekends unless you change the inputs. Workday-only policies need the business days calculator or a timesheet tool that applies break, holiday, and overtime rules separately from raw datetime difference.

Can I measure same-day hours only?

Yes when start and end share one calendar date. For simple clock-in and clock-out on the same day, the hours calculator may be faster. Choose hours between dates when the span crosses midnight, months, time zones, or daylight saving transitions that same-day tools do not handle.

Processing, please wait...