Purpose and scope
What this technical calculator produces
Apply an entered TAI−UTC offset to a UTC timestamp.
The Leap-Second and TAI-UTC Converter keeps UTC timestamp and TAI−UTC seconds visible beside the result so the inputs can be checked, saved, and reproduced without reconstructing the calculation later.
Instructions
How to use this calculator
Enter the values requested for the Leap-Second and TAI-UTC Converter and replace every sample with the actual schedule, record, or system being analyzed.
- Use UTC timestamp and TAI−UTC seconds to establish the starting conditions for the Leap-Second and TAI-UTC Converter.
- Set TAI−UTC seconds to match the actual case rather than leaving example assumptions in place.
- Run the Leap-Second and TAI-UTC Converter with a baseline set of values, then change only one uncertain input at a time when comparing alternatives.
Calculation
Method used
The entered whole-second offset is added to UTC to produce the corresponding TAI label.
The displayed formula makes the role of UTC timestamp and TAI−UTC seconds explicit. In the Leap-Second and TAI-UTC Converter, keeping those inputs separate helps distinguish a changed assumption from a changed calculation rule.
Calculation method last reviewed: June 20, 2026.
Worked scenario
Example calculation
To audit your own Leap-Second and TAI-UTC Converter result, compare UTC timestamp and TAI−UTC seconds with the worked scenario. In the Leap-Second and TAI-UTC Converter, if the direction or scale looks wrong, verify TAI−UTC seconds before changing several inputs at once.
Interpretation
Validating the generated output
The arithmetic is only as accurate as the supplied offset for the historical or future date.
Read the headline together with the supporting metrics for UTC timestamp and TAI−UTC seconds. A plausible-looking Leap-Second and TAI-UTC Converter result can still be unreliable when one of those values uses the wrong unit, date boundary, or local convention.
The GPS Week and Time-of-Week Converter extends the Leap-Second and TAI-UTC Converter by letting you convert UTC time into GPS week and seconds-of-week using an entered offset.
Visual audit
Checking the technical output
The Leap-Second and TAI-UTC Converter technical output is generated from UTC timestamp and TAI−UTC seconds. Before relying on the Leap-Second and TAI-UTC Converter, compare the human-readable preview with the copyable value, then test that value in a safe environment using the intended platform time zone or syntax rules.
Boundaries
Important edge cases and limitations
Historical and future offsets must be supplied from an authoritative leap-second table.
If one of these exclusions applies, treat the Leap-Second and TAI-UTC Converter output as a baseline and correct TAI−UTC seconds or another affected input before recalculating.
Practical use
Recommended workflow
Verify the offset against an authoritative leap-second bulletin before scientific or operational use.
Use the NTP Timestamp Converter alongside the Leap-Second and TAI-UTC Converter to convert between UTC time and the NTP seconds epoch. When work based on the Leap-Second and TAI-UTC Converter expands, the Julian Date and Modified Julian Date Converter can convert a UTC timestamp into Julian Date and Modified Julian Date.
Input audit
Checklist for this calculation
- Confirm the source and units for UTC timestamp and TAI−UTC seconds before entering them.
- Preserve TAI−UTC seconds with any saved or shared Leap-Second and TAI-UTC Converter result.
- For the Leap-Second and TAI-UTC Converter, review the exclusions above for conditions that could change TAI−UTC seconds or the calculation method.
- Recalculate the Leap-Second and TAI-UTC Converter whenever a recorded input or real-world condition changes.
Questions
Frequently asked questions
Why is the TAI−UTC offset not constant?
UTC inserts leap seconds while TAI is a continuous atomic time scale.
How should the leap-second and tai-utc converter result be checked?
The arithmetic is only as accurate as the supplied offset for the historical or future date. Verify the offset against an authoritative leap-second bulletin before scientific or operational use.
How is the leap-second and tai-utc converter result calculated?
The entered whole-second offset is added to UTC to produce the corresponding TAI label. TAI label = UTC timestamp + entered TAI−UTC whole-second offset.
Which reference supports the leap-second and tai-utc converter?
The References section links to IERS: Bulletin C leap-second announcements for the rule, definition, or method associated with this calculation.
Verification
References
Reference and calculation method reviewed: June 20, 2026.