Convert Time Zones First
If the two timestamps come from different time zones, convert them before entering them. A start time in New York and an end time in Los Angeles cannot be compared safely until both are in the same time zone.
Daylight saving time can also change the real elapsed hours for ranges that cross a clock change. A span over the spring change may be one hour shorter than the clock faces suggest. A span over the fall change may be one hour longer.
This matters for travel records, remote teams, customer support logs, server logs, and event schedules. If one system stores local time and another stores UTC, convert first or the duration can be off by hours.
Example: Overnight Span
A shift, outage, flight delay, or event from 10:00 PM to 6:00 AM should use the next calendar date as the end date. If the start and end dates are the same, the page treats 6:00 AM as earlier than 10:00 PM and marks the duration as backward.
A backward result is usually a sign that the dates were entered in the wrong order or the end date should be moved to the next day. The duration is still shown so the size of the gap is clear.
For short same-day spans, the date still matters less than the time. For anything that crosses midnight, crosses time zones, or crosses a daylight saving change, the date becomes part of the calculation.
Choosing the Useful Output
The main result is easiest to read: days, hours, minutes, and seconds. Decimal hours are usually better for billing and timesheets. Total minutes work well for service windows, trip logs, and operational reports. Total seconds work well for technical logs, audits, and performance records.
For date-only spans, use the days between dates calculator. For a full week of clock-in and clock-out rows, use the time card calculator. For finding a future or past date from a known start date, use the date calculator.
Decimal hours can look strange at first. A result of 1.50 hours means 1 hour and 30 minutes. A result of 1.25 hours means 1 hour and 15 minutes. Use the readable breakdown when communicating the time, and the decimal value when entering it into a billing or spreadsheet system.
If a system rounds time before billing or reporting, apply that rule after calculating the raw duration. This page gives the elapsed span; it does not round to quarter hours, tenths of an hour, or minimum billable blocks.
Common Mistakes
Do not enter only the times when a span crosses midnight. The date matters. A 10:00 PM to 6:00 AM range is an overnight span, not a negative same-day span.
Do not mix local time from one system with UTC or server time from another system. Logs, calendars, travel records, and remote-work schedules often store time in different zones.
Do not use a date-only count when partial days matter. A project that starts Monday at 4:00 PM and ends Tuesday at 9:00 AM is not the same as a full one-day block.
Also check whether the end timestamp is meant to be included. For most elapsed-time records, the duration stops at the exact end time. For event attendance or date-only reporting, a different counting rule may apply.