Audited 29 Jul 2026·Last updated 28 Oct 2026·5 citations·Tier 2·0 uses

Julian Date Calculator

Convert a UTC date and time to Julian Date, MJD, TJD, days since J2000.0 and Julian centuries T, for Gregorian dates or pre-1582 Julian calendar records.

Julian Date Calculator

The calendar date, read in whichever calendar you select below. No local timezone is ever applied — the clock time is taken as UTC exactly as typed.
0 to 23, in Coordinated Universal Time. Remember the Julian Day begins at NOON, so midnight UTC always gives a JD ending in .5.
h
0 to 59.
min
0 to 59. A leap second (23:59:60) cannot be represented as a Julian Date at all, since JD is a smooth count of days.
s
Calendar of the entered date
37 s since 2017 January 1 and unchanged as of IERS Bulletin C (no leap second at the end of 2026). It was 32 s in 2000 and 10 s in 1972 — change it if your instant is from another era.
s
Julian Date (JD)
2,461,250.5
Days and fraction of a day since noon UT on 1 January 4713 BC (Julian calendar), for the UTC instant entered.
Modified Julian Date (MJD)
61,250
Days since J2000.0
9,705.5 d
Julian centuries T (UT-based)
0.2657
Julian centuries T (TT-based)
0.2657
Julian Day Number (of this date)
2,461,251
Julian Day Number (containing this instant)
2,461,250
Truncated Julian Date (TJD)
21,250
Julian Date on the TT scale
2,461,250.5008
TT − UTC applied
69.184 s
Reading
JD 2461250.500000 and MJD 61250.000000 for 2026-07-29 00:00:00 UTC, read as a Gregorian calendar date. The Julian Day begins at NOON, which is why a midnight instant ends in .5; MJD begins at midnight, which is why it does not. On the Terrestrial Time scale the same instant is 69.184 s later, since TT = TAI + 32.184 s exactly and TAI − UTC = 37 s as entered. Two Julian Day Numbers are reported because two conventions exist: 2461251 labels this calendar date (the integer JD at its noon), while 2461250 is the noon-to-noon day this instant actually falls in.

Background.

Variable-star observers, satellite trackers and anyone reducing an old eclipse record hit the same snag: months have different lengths, the leap-year rule changed in 1582, and subtracting two calendar dates by hand is error-prone. Astronomy avoids the problem with the Julian Date, a single running count of days and fractions of a day. Noon UTC on 29 July 2026 is day 2,461,251; six hours later it is 2,461,251.25. The interval between any two observations, however far apart, is one subtraction.

Give a date and a UTC clock time and you get that number along with the variants other fields prefer: the Modified Julian Date used in geodesy and observatory logs, NASA's Truncated Julian Date, days since the J2000.0 epoch, and the Julian-century argument T that precession, nutation and sidereal-time formulas take as input.

Two settings decide whether the answer is right. One is the calendar. Anything dated before 15 October 1582, and much that was dated later, was written in the Julian calendar, which since March 1900 has run 13 days behind the Gregorian. Read a date in the wrong calendar and the Julian Date is off by that many days, with nothing in the number to warn you. The other is the time scale. The clock you type is read as UTC with no time zone applied, but ephemerides are computed on Terrestrial Time, which runs ahead of UTC by 32.184 seconds plus the accumulated leap seconds. That count is an editable input, 37 seconds by default, because it has grown by 27 since 1972.

The noon start leaves two habits that surprise newcomers: a midnight instant always gives a Julian Date ending in .5, and the phrase Julian Day Number has two meanings that disagree every morning. Both numbers are reported, each labelled.

What is julian date calculator?

The Julian Date (JD) is the number of days, including the elapsed fraction of the current one, since 12:00 Universal Time on 1 January 4713 BC in the proleptic Julian calendar, written −4712 in astronomical year numbering, which includes a year 0. Its starting point comes from Joseph Scaliger's Julian Period of 1583, which astronomers later turned into a continuous day count. Each day begins at noon so that one night of European observing stays inside a single day number. The other counts are fixed offsets: MJD = JD − 2400000.5, whose day zero is 17 November 1858 starting at midnight; TJD = JD − 2440000.5, zero on 24 May 1968; and the J2000.0 epoch is JD 2451545.0, defined as 1 January 2000 at 12:00 Terrestrial Time. A Julian century is exactly 36,525 days.

How to use this calculator.

  1. Type the date as your source gives it and set the calendar to match. Use Julian for anything before 15 October 1582 and for later records from countries that changed late; a pre-1582 date left on Gregorian brings a note that the calendar did not exist yet.
  2. Enter hour, minute and second in UTC, converting local time first: 21:30 in a UTC+3 zone is 18:30 UTC. A leap second, 23:59:60, cannot be entered because the day count has no place for it.
  3. Leave TAI − UTC at 37 seconds for anything since 1 January 2017. For older instants use the value then in force, such as 32 seconds for 1999 to 2005 or 10 seconds in 1972, or the Terrestrial Time outputs will be off by the difference.
  4. To log or subtract observations, read JD or MJD. To feed a formula from an almanac or from Meeus, read days since J2000.0 or T, and check whether it wants the UT-based T (sidereal time) or the TT-based one (planetary positions, precession, nutation). The results grid shows four decimals of a day (about 8.6 seconds); the reading line underneath gives six.

The formula.

JD = ⌊365.25(Y+4716)⌋ + ⌊30.6001(M+1)⌋ + D + B − 1524.5 MJD = JD − 2400000.5 T = (JD − 2451545.0) ⁄ 36525

The conversion follows chapter 7 of Jean Meeus's Astronomical Algorithms. January and February are counted as months 13 and 14 of the previous year, which puts the leap day at the very end of the counting year and keeps the month arithmetic regular. Then JD = ⌊365.25(Y + 4716)⌋ + ⌊30.6001(M + 1)⌋ + D + B − 1524.5. The first term counts the days in whole Julian years from far back. The second counts the days in months already completed: 30.6 reproduces the alternating 31- and 30-day pattern from March onward, and the extra 0.0001 stops a product such as 30.6 × 5 = 153 from slipping to 152.9999 in floating-point arithmetic. D is the day of the month plus the clock time as a fraction of 86,400 seconds. B = 2 − A + ⌊A/4⌋, with A = ⌊Y/100⌋, removes the century leap days the Gregorian calendar drops; for a Julian-calendar date B is zero. The integer method of Fliegel and Van Flandern (1968), reproduced in the Explanatory Supplement to the Astronomical Almanac, gives the same day numbers.

Everything else is a fixed offset or ratio. MJD = JD − 2400000.5, TJD = JD − 2440000.5, days since J2000.0 = JD − 2451545.0, and T = that difference ÷ 36,525. For Terrestrial Time, JD(TT) = JD + (32.184 + TAI − UTC) ÷ 86,400, and the TT-based T is taken from JD(TT). The 32.184 seconds is exact by definition: it makes Terrestrial Time continuous with the older Ephemeris Time scale. No step is approximate, so a wrong answer can only come from the wrong calendar, a clock time that is not UTC, or the wrong leap-second count.

A worked example.

Example

Take noon UTC on 1 January 2000, with TAI − UTC set to 32 seconds, the value in force that year. January counts as month 13 of the previous year, so Y = 1999 and M = 13. Then A = ⌊1999 ÷ 100⌋ = 19 and B = 2 − 19 + ⌊19 ÷ 4⌋ = 2 − 19 + 4 = −13. The year term is ⌊365.25 × 6715⌋ = 2,452,653, the month term is ⌊30.6001 × 14⌋ = 428, and D is 1.5: the first of the month plus half a day. Adding up, 2,452,653 + 428 + 1.5 − 13 − 1524.5 = 2,451,545, so JD = 2451545 exactly. MJD is 51,544.5, TJD is 11,544.5, and days since J2000.0 is 0, which makes the UT-based T zero as well. The TT-based T is not zero. TT − UTC is 32.184 + 32 = 64.184 seconds, or 0.00074287 of a day, so JD(TT) reads 2,451,545.0007 and T(TT) = 0.00074287 ÷ 36,525 = 2.034 × 10⁻⁸ centuries. That small number is the whole point of the example: J2000.0 is noon on the Terrestrial Time clock, which fell at 11:58:55.816 UTC, so noon UTC came 64.184 seconds after the epoch.

calendargregorian
date2000-01-01
minute Utc0
second Utc0
tai Minus Utc Seconds32
hour Utc12

Frequently asked questions.

Why does a midnight instant give a Julian Date ending in .5?
Because each Julian day runs from noon to noon, midnight is always half-way through one. Midnight UTC on 29 July 2026 is JD 2,461,250.5. The Modified Julian Date subtracts 2,400,000.5 partly to move the boundary back to midnight, which is why the same instant has a whole-number MJD of 61,250.
Two Julian Day Numbers are shown. Which one should I quote?
The first is ⌊JD + 0.5⌋, the integer JD at noon of the calendar date you entered; it stays the same all civil day and is the usual meaning in calendar algorithms, Fliegel and Van Flandern's included. The second is ⌊JD⌋, the noon-to-noon day the instant falls in, which changes at noon. At 06:00 UTC on 29 July 2026 they read 2,461,251 and 2,461,250; by 18:00 both read 2,461,251.
How do I convert an observation dated before October 1582?
Enter the date as written and switch the calendar to Julian. The reform made Thursday 4 October 1582 (Julian) the day before Friday 15 October 1582 (Gregorian): their Julian Dates at midnight are 2,299,159.5 and 2,299,160.5, one day apart. Britain and its colonies kept the Julian calendar until 1752 and Russia until 1918, so check the source's country as well as its year.
Why is 29 February 1900 accepted in one calendar and refused in the other?
The Julian calendar makes every fourth year a leap year, so 29 February 1900 existed there, at JD 2,415,091.5. The Gregorian calendar skips century years not divisible by 400, so 1900 had no 29 February while 2000 did. That skipped day is how the gap between the calendars grew from 12 to 13 days in March 1900.
Is the UT-based T accurate enough for sidereal time?
Sidereal-time formulas are defined on UT1, the time scale tied to the Earth's actual rotation. UTC is kept within 0.9 seconds of UT1 by leap seconds, so a T computed from UTC can put local sidereal time out by up to about 0.9 seconds of time. That is fine for pointing a telescope, but not for arcsecond-level reductions, which need the published UT1 − UTC correction.
Can I subtract two Julian Dates to time an event?
Yes: the difference is in days, and multiplying by 86,400 gives seconds. Resolution is the limit. The results grid shows four decimals of a day, about 8.6 seconds, and the reading line six, about 0.09 seconds. For anything shorter, take the interval straight from the two clock readings rather than from day counts in the millions.
What changes if I set the wrong leap-second count?
JD, MJD, TJD and the UT-based outputs do not change, because they follow the UTC clock you typed. Only TT − UTC, JD(TT) and the TT-based T move, by exactly the error in seconds. Entering 37 for an instant in 2000 shifts them by 5 seconds, about 2.7 arcseconds of the Moon's motion, while the day counts stay identical.

References& sources.

  1. [1]Meeus, J. (1998). Astronomical Algorithms, 2nd edition, Willmann-Bell, chapter 7 ('Julian Day'). Source of the primary conversion algorithm implemented here, including the March-start year shift and the Gregorian century correction B. Print / bibliographic reference — no authoritative free full text exists, so no URL is offered rather than linking a scan of uncertain provenance.
  2. [2]Fliegel, H.F. & Van Flandern, T.C. (1968). 'A Machine Algorithm for Processing Calendar Dates.' Communications of the ACM 11(10):657. The pure-integer algorithm, implemented independently here as a cross-check on Meeus's method, with which it agrees across twelve sample dates. Peer-reviewed; the ACM Digital Library copy is paywalled, so it is shipped as a bibliographic reference.
  3. [3]Urban, S.E. & Seidelmann, P.K. (eds.) (2013). Explanatory Supplement to the Astronomical Almanac, 3rd edition, University Science Books. Reproduces the Fliegel–Van Flandern algorithm (pp. 617–619 in the 3rd edition; p. 604 in the 1992 edition) and defines JD, MJD and the relationships between UT, TAI and TT. Print; the U.S. Naval Observatory's publication page for it is linked. Retrieved 2026-07-29.
  4. [4]IERS Bulletin C, International Earth Rotation and Reference Systems Service. Verified by retrieval 2026-07-29 to state that the difference between UTC and TAI is −37 seconds 'from 2017 January 1, 0h UTC, until further notice', and that NO leap second will be introduced at the end of December 2026. Source of the default TAI − UTC input. Open access.
  5. [5]International Astronomical Union, Resolution A4 (1991), defining Terrestrial Time, and the conventional relation TT = TAI + 32.184 s exactly, which makes TT continuous with the earlier Ephemeris Time scale. Bibliographic reference to the IAU resolution text.

How this page was produced

Published by
Quanta Calculator
Primary sources
5 cited below
Method
JD = ⌊365.25(Y+4716)⌋ + ⌊30.6001(M+1)⌋ + D + B − 1524.5 MJD = JD − 2400000.5 T = (JD − 2451545.0) ⁄ 36525
Published
Last verified

Built with AI assistance and verified by automated tests against the cited sources — every worked example on this page is computed by the same code that runs the calculator. How we build and check calculators.

In this category

Embed

Quanta Pro

Paid features are coming later.

  • All 1560 calculators remain free
  • No billing is enabled
Coming soon