Free · No account · Works in your browser
Julian Day Number
Julian Day Number (JDN) converter
Julian Day Number
Enter values below, then calculate.
Julian Day Number (JDN) assigns a continuous day index to every calendar date, starting at noon Universal Time to avoid midnight ambiguity in astronomical observation logs. Historians of science, astronomers, and orbital mechanics software use JDN to subtract dates without month-length tables. This converter maps civil Gregorian dates to JDN and back, distinct from the Julian calendar civil reform page.
JDN versus Julian calendar pages
The Julian calendar hub on this site covers the Old Style civil calendar still used by some churches. Julian Day Number is a scalar day count for astronomy — unrelated naming trips newcomers. Modified Julian Date (MJD) subtracts 2400000.5 for shorter numbers — see modified Julian date.
Ordinal YYDDD codes label day-of-year for logistics — use ordinal date when you need warehouse labels, not JDN.
How Julian Day Number is defined
JDN for a Gregorian date is computed with standard astronomical formulas so consecutive civil days increment by one at the noon boundary in the UT system. JDN 0 is defined historically as noon on 4713 BCE January 1 in the proleptic Julian scale — academic tables may differ slightly on BCE labeling but agree for modern dates.
Half-day offsets matter: astronomers observing at night on Monday may log the JDN that started at Monday noon UT. Software that assumes midnight civil time should document its offset.
When teams use JDN
Planetarium software plots ephemerides against JDN axes. Historians compare manuscript dates across calendar reforms by converting to JDN first. Space ops teams correlate TLE epochs with civil schedules. Archaeology databases store JDN for stratigraphy layers spanning BCE and CE without two-digit year bugs.
Excel or Unix pipelines should convert JDN to ISO dates before feeding CRM systems that expect yyyy-mm-dd.
Worked examples
Verify JDN for January 1 on a known reference epoch against a published almanac row — off-by-one means your code uses midnight instead of noon boundary.
Compute delta days between two excavations by subtracting JDN values instead of looping months — cross-check with days between dates for civil inclusive counts.
Eclipse planning for 2026 — convert event date to JDN, compare with MJD from the MJD converter by subtracting 2400000.5.
Accuracy notes
Gregorian proleptic rules apply backward before the 1582 reform in most calculators here — state that assumption in research papers. Leap years follow Gregorian 4/100/400 rules. BCE years use astronomical year numbering in some libraries — confirm your sign convention.
Roman numeral ceremonial dates use Roman numeral date. Cron schedules use cron calculator.
Literature and catalog cross-refs
SIMBAD, JPL Horizons, and USNO publications cite JD or MJD for observation midpoints. When a paper tables JD for J2000.0, confirm whether they mean noon or midnight-based JDN before comparing with this converter's civil date output.
Variable star epoch updates in AAVSO bulletins assume JD continuity — plot light curves in JD rather than civil dates to avoid leap and month-length kinks in differencing.
Software integration
Python astropy Time and IDL julday functions may differ by half-day — unit-test one known pair from this page in CI. Store JDN as integer when your pipeline uses noon convention; store JD as float when time-of-day within the day matters.
Database columns typed as FLOAT for JD lose precision on very large values — some teams store JDN integer plus seconds offset instead.
Common mistakes
Confusing Julian calendar civil dates with Julian Day Number. Applying local timezone to JDN without converting to UT first. Using JDN where ordinal YYDDD suffices — wastes precision and confuses logistics partners.
Subtracting civil dates as MM/DD strings instead of converting to JDN first — month-length errors accumulate.
Museum and archive catalogs
Digitization projects normalizing heterogeneous date fields to JDN enable sorting manuscripts that mix Julian and Gregorian labels in one finding aid — convert each row, store JDN as canonical sort key, keep display date in original calendar.
Exhibition timelines plotting objects on one axis use JDN internally while labels show civil dates visitors expect.
Teaching astronomical time
Undergraduate labs ask students to compute JDN by hand once, then verify here — focus grading on showing noon convention, not memorizing five-digit results. Follow with MJD conversion homework to reinforce the 2400000.5 offset.
Planetarium volunteer training includes JDN vocabulary so docents answer guest questions about ephemeris tables printed in handouts.
Ephemeris publishing
Amateur astronomers publishing comet observation logs should convert local observation civil date to JDN with documented UT offset — sharing logs without JDN forces collaborators to guess timezone.
Desktop planetarium exports often include JDN columns — map back to civil dates for newsletter readers using this page.
Dendrochronology and ice cores
Paleoclimate datasets referencing year plus day index benefit from JDN when correlating ice-core layers with historical sunspot records — convert publication dates to JDN before joining cross-disciplinary tables.
Tree-ring labs storing sample dates as year plus DOY should validate DOY against month-day via ordinal date before exporting to JDN pipelines.
Citizen science uploads
Citizen science apps uploading observation timestamps should include JDN in API payloads when projects merge global datasets — volunteers see civil dates locally while servers sort on JDN.
Software archaeology on legacy Fortran ephemeris code validates one JDN output against this page after recompilation on modern hardware.
High school astronomy clubs plotting planet positions export JDN from software and decode observation nights with this page for parent newsletters.
Planetarium gift shop star charts listing JDN for eclipse paths should include civil date translation in parenthetical text for general audiences buying impulse items.
Open source maintainers document one JDN golden test vector in README files linking to this converter so contributors reproduce noon convention in CI.
Science fair judges accept JDN verification printouts from this page when students compare computed values to software output in astronomy projects.
Related tools
See modified Julian date, Unix timestamp, and the converters hub.
Frequently asked questions
What is Julian Day Number?
Julian Day Number (JDN) is an integer day index for civil dates on a continuous scale used in astronomy and historical software, with consecutive days incrementing at the noon UT boundary in standard definitions referenced by almanacs and planetarium tools.
Is this the Julian calendar?
No. Julian calendar pages cover Old Style civil dates still used by some churches. Julian Day Number is unrelated naming — a scalar day count for science, not the historical calendar reform itself that shifted European civil dates centuries ago.
Why noon instead of midnight?
Observatories historically logged nights under one Julian day starting at noon UT to avoid splitting an observing session across two midnight civil days. Software using midnight civil time should document its offset when comparing to published JDN tables and textbooks.
How do I get Modified Julian Date?
Modified Julian Date equals Julian Date minus 2400000.5. Use the modified Julian date converter for shorter numbers common in pulsar timing, VLBI logs, meteor camera CSV interchange, and twentieth-century Fortran ephemeris printouts still cited in papers. Always confirm edge cases against primary sources when results affect legal, medical, or financial decisions.
Can I subtract two dates with JDN?
Yes. Difference of Julian Day Numbers on the same convention equals whole days between dates — useful in code before month-length loops. Cross-check civil inclusive counts with days between dates when stakeholders expect calendar wording in footnotes. Always confirm edge cases against primary sources when results affect legal, medical, or financial decisions.
What calendar rules apply?
Proleptic Gregorian leap rules for modern dates unless noted. BCE labeling may follow astronomical year numbering in some libraries — confirm sign convention before joining datasets spanning era boundaries in archaeology and manuscript databases. Always confirm edge cases against primary sources when results affect legal, medical, or financial decisions.