Julian Date
& Sidereal Time Converter

The Astronomer's Chronometer

In standard civil life, we measure time using the Gregorian calendar. However, for the study of celestial mechanics and the tracking of the moon phase today, more precise systems are required. This page is intended as a standing reference: bookmark it, link to it, and use it whenever you need the definitions, formulas, and conversion tables behind Julian Dates and sidereal time.

What is the Julian Date (JD)?

The Julian Day system was introduced in 1583. It is a simple, continuous count of days and fractions of days since noon Universal Time on January 1, 4713 BC (on the proleptic Julian calendar). Because it is a single decimal number rather than a year/month/day triplet, it lets scientists compute the exact interval between two astronomical events — say, two solar eclipses thousands of years apart — by simple subtraction, with no month-length or leap-year bookkeeping.

A JD value like 2461075.71235 encodes both the date and the time of day: the integer part is the day count, and the decimal fraction is the time elapsed since the preceding noon UT.

History: Scaliger and the Julian Period

The system was devised by the French-Italian scholar Joseph Scaliger in 1583, and named — most historians agree — in honor of his father, Julius Caesar Scaliger, rather than the Roman Julian calendar (though the two names are frequently confused; see the FAQ below). Scaliger wanted a single, unbroken day-count that could reconcile the many overlapping chronological systems used by historians of his era.

He built it from three astronomical/calendrical cycles that were all in common use: the 28-year Solar Cycle (after which weekdays realign with calendar dates in the Julian calendar), the 19-year Metonic Cycle (after which lunar phases repeat on the same calendar dates), and the 15-year Roman Indiction Cycle (a tax-assessment cycle). Multiplying these together gives a "Julian Period" of 7,980 years (28 × 19 × 15). Scaliger picked the start point, 1 January 4713 BC, because it was the most recent year in which all three cycles simultaneously began — a date early enough that it precedes all recorded history, so every historical event in the ancient world could be assigned a single, unambiguous, always-increasing day number.

In 1849, astronomer John Herschel proposed adapting Scaliger's day-counting idea specifically for astronomy, starting the count at noon so a full night's observations would fall on one calendar date — and the modern astronomical Julian Day Number was born.

Modified Julian Date (MJD)

For modern computing, astronomers and satellite operators often use the Modified Julian Date, introduced by the Smithsonian Astrophysical Observatory in 1957 for tracking Sputnik. It is simply:

Subtracting 2,400,000.5 does two things: it removes the leading digits that never change in the modern era (shortening the number for storage and display), and it shifts the day boundary from noon to midnight UTC, aligning it with civil timekeeping. MJD 0 corresponds to 17 November 1858, 00:00 UTC.

How to Calculate Julian Date by Hand

You don't need a telescope-grade tool for a rough conversion. For any Gregorian calendar date (year Y, month M, day D, all integers, with time-of-day added separately), the standard algorithm is:

The result, JDN (Julian Day Number), is an integer valid at noon UT on that calendar date. Adding the fractional day offset from UT noon gives the full JD, which is what the converter at the top of this page computes for you automatically — along with sidereal time, which requires additional Earth-orientation terms that are impractical to compute by hand.

Quick-Reference Table of Notable Julian Dates

A handful of fixed reference points come up constantly in astronomy and computing. Use this table to sanity-check conversions or as quick anchors for your own calculations.

Julian Date vs. UTC, TAI, GPS Time, and Unix Time

JD is a day-counting scheme, not a time standard in the metrological sense — it can be built on top of different underlying clocks, and which one matters for precision work:

Because JD is most commonly expressed on the UT/UTC scale, it inherits UTC's leap-second irregularities. High-precision applications (pulsar timing, deep-space navigation) instead use Julian Ephemeris Date (JDE), based on the uniform Terrestrial Time (TT) scale, which currently runs about 69 seconds ahead of TAI-derived UT.

Understanding Sidereal Time

Sidereal time is "star time." While a solar day is 24 hours, a Sidereal Day is approximately 23 hours, 56 minutes, and 4.09 seconds — the time it takes Earth to complete one full rotation relative to the distant "fixed" stars, rather than relative to the Sun. The roughly 3 minute 56 second gap exists because, while the Earth spins, it also advances along its orbit, so it must rotate slightly more than 360° each day for the Sun to return to the same point in the sky.

Greenwich Mean Sidereal Time (GMST) is the sidereal time at the 0° meridian, the same for every observer on Earth at a given instant. Local Sidereal Time (LST) adjusts GMST for your own longitude — add roughly 4 minutes of sidereal time for every degree of longitude East, subtract for West — and is essential for anyone using an equatorial telescope mount, since it tells you exactly which Right Ascension is crossing your local meridian right now.

Precession and Astronomical Epochs

Earth's axis slowly wobbles over a roughly 26,000-year cycle, called precession of the equinoxes. Because the celestial coordinate grid (Right Ascension and Declination) is tied to Earth's axis and equinox, star catalogs and telescope pointing models must specify which moment in time — epoch — their coordinates are valid for.

The current standard is J2000.0, corresponding to JD 2451545.0 (1 January 2000, 12:00 TT). Older catalogs and some legacy software use B1950.0. Coordinates given in one epoch must be precessed to another before comparison — using J2000 coordinates with a B1950-era pointing model, for instance, will place objects noticeably off-target.

Practical Applications

Beyond amateur astronomy, JD and sidereal time show up in several fields where clean, calendar-independent timekeeping matters:

Telescope pointing & equatorial mounts

Setting an equatorial mount's hour-circle correctly requires LST; a mount synced to the wrong sidereal time will point at the wrong Right Ascension even if Declination is correct.

Satellite & orbital tracking

Orbital element sets (TLEs) reference specific epochs, and propagating an orbit forward or backward in time is far simpler as JD arithmetic than as calendar-date arithmetic.

Pulsar timing & deep-space navigation

Millisecond-pulsar timing arrays and interplanetary spacecraft navigation depend on the uniform TT-based Julian Ephemeris Date, since leap-second jumps in UTC would otherwise corrupt long-baseline timing models.

Historical & archaeoastronomical research

Because JD is continuous across the Julian/Gregorian calendar reform of 1582, it's the standard way historians and archaeoastronomers date ancient eclipse and lunar records without re-deriving calendar conversions each time.

Common Pitfalls

Glossary