Date, time, and schedules
How long is PT90M, and is P1M the same as PT1M?
Tools to use
Video lengths, timeouts or scheduled durations may arrive as strings containing P and T. PT90M is a duration, not a date or clock time. Compare its components and seconds in Duration Converter, and avoid inventing a calendar or time zone for a value that has no starting instant.
Read PT90M in seconds and hours
PT90MThe minute component is 90 and total seconds is 5400: 90 × 60, or one hour and thirty minutes. If the ISO string remains PT90M, conversion has not failed. The tool inspects components and totals rather than guaranteeing a preferred spelling such as PT1H30M.
Entering bare 5400 means seconds here and represents the same length. Bare 90 means ninety seconds, not ninety minutes. Copying a number without its unit can create a sixtyfold error elsewhere. Share the notation and unit with the result.
P1M and PT1M are different units
P1M
PT1MP1M means one month; PT1M means one minute. Enter them separately. The latter totals sixty seconds; the former has no fixed total here because month length and the starting date are unspecified. Replacing every M as though it meant minutes changes the meaning.
Likewise P1Y is not always 365 days in seconds. A service may explicitly define a month as thirty days, but that is its own contract. Without such a rule, do not replace calendar units just to obtain a convenient number. An unavailable total can correctly indicate missing context.
Separate this duration model from a clock day
P1DT2HWithout months or years, this converter totals against a date without a time zone. P1DT2H is twenty-six hours, or 93600 seconds. This does not prove that the same wall-clock time tomorrow is always 86400 seconds away. For real instants across offset changes, use Date Difference with explicit endpoints.
A two-day calendar event, forty-eight processing hours and advancing two dates are different tasks. Do not mix business days, calendar dates and elapsed seconds. This converter does not infer holidays or closing times; identify which kind of time the result represents before using it.
Specify fractional seconds explicitly
PT1.5SPT1.5S totals 1.5 seconds. The displayed seconds component may be 1 because the current component list stops at whole seconds; inspect the ISO string and total for the fractional part. Do not reconstruct the result from an incomplete subset of displayed fields.
The tool does not guess whether 01:30 means hours/minutes or minutes/seconds. Use 90 for ninety seconds or PT90M for ninety minutes. Fractional bare-number input differs from ISO fractional input here, so use PT1.5S explicitly. Verify the receiver's supported duration syntax too.
A duration is not a deadline
PT30M from an API does not identify an expiry instant. It might run from issuance, last activity or represent processing duration. A deadline requires a reference time as well as a duration. A total of 1800 seconds does not mean the user has 1800 seconds remaining now.
Keep PT90M, PT1M, P1M, P1DT2H and PT1.5S as separate checks for unit placement, calendar context and fractions. If a receiver requires seconds, define how calendar units are handled. Explicitly missing context is preferable to an invented conversion that produces a wrong deadline.