Overlapping time of two intervals calculator

Supply the start and end of each interval in ISO 8601 format, including either Z or a numeric UTC offset. The calculation converts every boundary to the same UTC timeline, finds the later start and earlier end, and reports the shared duration in milliseconds, seconds, minutes, and hours. Separate intervals and intervals that merely touch return zero, making the result straightforward to use in scheduling, billing, monitoring, and reporting workflows.

Define both intervals with unambiguous boundaries

Enter four values: the start and end of the first interval, followed by the start and end of the second. Every value must be a complete ISO 8601 datetime containing a calendar date, a clock time with seconds, and either Z or an explicit offset such as +02:00 or -05:30. Requiring an offset prevents a local wall-clock value from being interpreted differently on another computer. Each start must be earlier than its corresponding end. The calculator treats intervals as half-open ranges: the start belongs to the interval, while the end is its boundary. That convention avoids counting the same instant twice when adjacent bookings, shifts, or processing windows meet. Fractional seconds from one through three digits are accepted and normalized to milliseconds. Calendar dates and clock components are validated directly, so impossible values such as February 30, hour 25, or a malformed offset produce an input error instead of a plausible but incorrect duration. Use the same four fields whether the ranges are expected to overlap or not; no special flag is needed for empty intersections.

Understand the deterministic UTC calculation

The calculation places all four boundaries on one UTC timeline before comparing them. A value ending in Z is already in UTC. A value with a positive numeric offset is moved backward by that offset, while a value with a negative offset is moved forward. This means two differently written datetimes can represent the same instant. After conversion, the overlap begins at the later of the two starts and ends at the earlier of the two ends. If that end is later than the computed start, their difference is the overlap. Otherwise, the duration is exactly zero. The implementation uses Gregorian calendar arithmetic and integer millisecond values; it does not consult the machine clock, locale, timezone database, network, random data, or JavaScript Date behavior. Consequently, identical inputs always produce identical results. Output includes the same duration expressed as milliseconds, seconds, minutes, and hours. These are conversions of one computed quantity rather than separate rounded estimates, so consumers can choose the unit that best matches a database, invoice, dashboard, or scheduling rule.

Apply the result safely in real workflows

Use overlap duration whenever two known time windows must be compared: an employee shift against approved leave, equipment operation against a tariff period, an incident against a service window, or a reservation against an availability block. A positive value tells you how much shared time exists, not merely whether the intervals intersect. Zero has two possible meanings: the intervals are separated, or one ends at the exact instant the other begins. Both cases have no elapsed time in common under the half-open boundary convention. For money or quota calculations, prefer overlap_milliseconds or overlap_seconds as the source value and apply your own documented rounding only after receiving the result. Do not round each input boundary beforehand unless that is part of the business policy. The endpoint evaluates explicit offsets only; it does not accept named zones such as America/New_York and does not infer daylight-saving rules. Resolve named local times to ISO datetimes with offsets before calling it. The API costs $0.002 per request, while the browser implementation can run the same deterministic calculation locally for interactive checks.