Julian Date Converter

Astronomers, satellite operators, and log analysts often need a date that does not restart at midnight in every time zone. The Julian Date Converter turns a Gregorian UTC date and time into astronomical Julian Date forms, or reverses a decimal Julian Date back to a UTC timestamp. It is a specialized time-and-date tool, not a day-of-year label maker.

Results

In Civil date to Julian Date mode, the calculator asks for a calendar date and a HH:mm time interpreted as UTC. It returns four related values: Julian Date (JD), Modified Julian Date (MJD), Reduced Julian Date (RJD), and Truncated Julian Date (TJD). In Julian Date to civil date mode, it accepts a decimal JD and returns the corresponding mixed-calendar UTC date-time plus the equivalent proleptic-Gregorian ISO instant. Before the 1582 reform those two labels can have different year-month-day text while identifying the same instant.

The difference from ordinary calendar math is continuity. A JD value advances by exactly one per day and uses the fractional part for time of day. That makes it convenient for observations, ephemerides, cross-system logs, and long intervals where month lengths and time zones would get in the way. If your starting timestamp is local civil time, convert it with the time zone calculator before entering it here. For human ages and anniversaries, use the age calculator; for elapsed hours or minutes, use the time duration calculator.

Algorithm and formulas

The calculator implements the standard mixed-calendar astronomical conversion. It uses the Julian calendar through October 4, 1582, omits October 5–14, and applies the Gregorian correction from October 15, 1582. It accepts civil years 0001 through 9999 and deliberately does not use astronomical year numbering: there is no input year zero, and BCE/negative years are outside this tool’s range. It also rejects civil dates invalid under the selected branch, including Gregorian February 29, 1700. In simplified form, with UTC time folded into the fractional day:

$\text{JD} = \left\lfloor 365.25 \times (y + 4716) \right\rfloor + \left\lfloor 30.6001 \times (m + 1) \right\rfloor + d + B - 1524.5 + \frac{h + \frac{\text{min}}{60} + \frac{s}{3600}}{24}$

For Gregorian dates, the correction term is:

$B = 2 - A + \left\lfloor \frac{A}{4} \right\rfloor,\quad A = \left\lfloor \frac{y}{100} \right\rfloor$

The related outputs are simple offsets from JD:

$\text{MJD} = \text{JD} - 2400000.5$

$\text{RJD} = \text{JD} - 2400000$

$\text{TJD} = \text{JD} - 2440000.5$

The reverse conversion separates the integer and fractional parts of JD + 0.5, reconstructs the mixed-calendar year, month, and day, then turns the fractional day into hours, minutes, and seconds. A JD that would map outside civil years 0001 through 9999 is rejected rather than emitting astronomical year zero or a signed ISO year.

Worked example: JD 2460000.500000

Enter 2023-02-25 and 00:00 in civil-date-to-Julian mode. The calculator creates a UTC date at midnight and runs the conversion. The primary result is Julian Date (JD) 2460000.500000. The related values are:

$\text{MJD} = 2460000.5 - 2400000.5 = 60000.0$

$\text{RJD} = 2460000.5 - 2400000 = 60000.5$

$\text{TJD} = 2460000.5 - 2440000.5 = 20000.0$

The display therefore shows MJD 60000.000000, RJD 60000.500000, and TJD 20000.000000. If you switch to Julian-Date-to-civil-date mode and enter 2460000.5, the stated method returns 2023-02-25 00:00:00 UTC and an ISO instant for the same moment.

How to interpret Julian Date values

Julian Date starts at noon UTC by convention, which is why a midnight UTC timestamp ends in .5. Modified Julian Date subtracts 2400000.5, so it rolls over at midnight and is easier to read in operational systems. Reduced and truncated forms are other shortened counts; always confirm which one a data feed expects because the numbers can differ by thousands of days.

For astronomy, JD keeps observation sequences sortable even when telescopes, archives, and researchers are in different time zones. Observing logs can be merged without asking whether a local night crossed midnight, and long-running instruments can compare exposures by simple subtraction. For IT, the same continuous-count idea helps with reproducible logs and data files, but many APIs prefer ISO 8601 or RFC 3339 timestamps instead. Use the JD value only when the receiving system explicitly wants it.

A useful rule is to store both forms when possible: the Julian value for calculation and an ISO-style UTC timestamp for human review. That pairing makes audits easier because a scientist, operator, or developer can verify the calendar date without manually converting the large day number.

Edge cases and common mistakes

Do not confuse astronomical Julian Date with the Julian calendar or with ordinal day-of-year codes. Do not enter local noon unless you first convert it to UTC. Be careful with dates before national Gregorian adoption; the algorithm’s calendar branch may not match the civil calendar used in a particular historical record. The calculator’s civil-date-to-Julian mode accepts minutes but not seconds, so a high-precision observation should be converted with software that preserves seconds and subsecond time scales.

Also remember that UTC itself is not the same as terrestrial time or barycentric dynamical time. Professional ephemeris work can require leap-second and relativistic time-scale handling beyond this calculator. This page is best for educational conversions, logs, planning, and checking common JD, MJD, RJD, and TJD relationships.

Sources

• U.S. Naval Observatory, Converting between Julian Dates and Gregorian calendar dates — authoritative formula reference for JD conversion.
• International Astronomical Union, List of IAU resolutions — official resolutions covering astronomical standards, time scales, and units.
• BIPM, The International System of Units brochure — official reference for SI time units used in precise measurement.