Secondary converter
Convert between Gregorian dates and the modern Hebrew calendar with deterministic civil calendar rules.
Enter a value and run the converter.
Guide
The Hebrew Calendar Converter changes Gregorian dates into Hebrew calendar dates and converts Hebrew input back into Gregorian dates.
Hebrew input uses numeric YYYY-MM-DD format with Tishri as month 01. The result includes the Hebrew month label so you can verify the numeric month basis.
This page is designed for civil date conversion and repeatable lookup. It does not decide local sunset boundaries, candle-lighting times, or other observance timing details.
What it handles
Enter a Gregorian date and return the matching Hebrew year, month number, day, and month label.
This direction is useful when your source date comes from the common civil calendar but you need a Hebrew calendar equivalent for comparison, labeling, or data entry. The result includes both a numeric month and a readable Hebrew month label.
The conversion treats the Gregorian input as a whole civil date and does not adjust it for local sunset.
Enter a Hebrew date using the page's Tishri-first month order and convert it to Gregorian.
Use this direction when your source already gives a Hebrew year, month, and day. The page expects the numeric month to follow its Tishri-first order, so the displayed month label is an important confirmation step.
If a source uses month names or a different numbering convention, translate it into this page's numeric order before submitting the date.
The converter validates common years and leap years, including Adar I and Adar II behavior.
Hebrew leap years add a month, which means some month/day combinations only make sense in certain years. The converter checks those rules before returning a Gregorian result.
This is especially useful when debugging copied dates from forms, calendars, or databases where the month number may not make the leap-year assumption obvious.
How to use
Use Gregorian to Hebrew for a Gregorian source date, or Hebrew to Gregorian when you already have a Hebrew numeric date.
The direction determines which validation rules apply. Gregorian input uses the standard date field, while Hebrew input uses numeric year, month, and day values with the page's civil Hebrew month order.
If you are unsure which calendar your source date uses, confirm that first; similar-looking numeric dates can represent very different days.
Month 01 is Tishri, month 02 is Heshvan, and the sequence continues through Elul.
This numbering makes civil Hebrew year boundaries explicit and keeps the form consistent with the labels shown in the result. It also avoids ambiguity with month-number systems that begin with Nisan.
When entering a date from a named-month source, convert the name to this Tishri-first number before using the form.
Leap years include Adar I and Adar II. Common years do not accept every leap-month combination.
A date involving Adar can be easy to misread because leap years and common years label the period differently. The converter helps catch invalid combinations before a Gregorian date is produced.
After conversion, compare the returned month label with your source to make sure the intended Adar form was used.
Examples
The Gregorian date 2026-07-01 converts to Tammuz 16, 5786 AM in this implementation.
This example shows the page returning a Hebrew year, numeric month, day, and month label for a standard Gregorian input. The label Tammuz helps verify that month 10 is being interpreted in the page's Tishri-first order.
For observance contexts, remember that this is a civil date conversion and does not decide local evening transitions.
The Hebrew input 5786-10-16 converts back to Gregorian 2026-07-01.
The reverse example is useful for checking copied Hebrew numeric dates. It confirms that the same day-number basis is used whether the lookup starts from Gregorian or Hebrew input.
If your source uses Nisan-first numbering, convert the month number before comparing it with this example format.
FAQ
The input uses civil Hebrew order beginning with Tishri as month 01, then Heshvan, Kislev, Tevet, Shevat, and onward through Elul.
The converter uses this order so that the Hebrew year begins with month 01 in the input format. The result label is shown to help confirm that the numeric month matches the intended named month.
If another reference starts its month numbering with Nisan, its month numbers cannot be entered directly without conversion.
No. The converter treats dates as civil calendar dates and does not model local sunset transitions or observance times.
Hebrew calendar observance can depend on evening boundaries, but this page intentionally works with whole civil dates. It does not know the user's location, sunset time, or community practice.
Use a location-aware Jewish calendar or local authority when candle-lighting, holiday start times, or halachic timing matters.
Reference
The converter applies fixed Hebrew calendar arithmetic with a 19-year Metonic cycle, leap months, and year-length rules, then maps dates through a Julian Day Number reference.
The Julian Day Number acts as a neutral bridge between Gregorian and Hebrew calendar calculations. It helps keep both conversion directions aligned and gives technical users a stable comparison point.
Because the page uses civil date arithmetic, it should be treated as a date lookup tool rather than an observance-time calculator.
Use cases
Convert between Gregorian dates and numeric Hebrew dates when a system needs year, month, and day fields.
Numeric fields are common in databases, imports, and internal tools, but they can hide month-order assumptions. This converter pairs the number with a visible month label so the date is easier to audit.
Keep the original source date and converted date together when cleaning data or building reference tables.
Use the displayed Hebrew month label to confirm that your numeric month maps to the intended Hebrew month.
The label is particularly valuable when a source was copied from a named-month calendar or from a system that uses another numbering convention. It gives a human-readable check before the result is used elsewhere.
If the label does not match your expectation, revisit the source month numbering rather than forcing the result.
Check whether a Hebrew date is valid in a common year or leap year before entering it elsewhere.
Leap-month handling is one of the easiest places to introduce data-entry errors. The converter can help identify whether the year supports the entered month and whether the day exists in that month.
This makes it useful for QA checks, calendar imports, and debugging user-submitted Hebrew dates.
More questions
The converter uses civil Hebrew month order to make year-boundary and leap-month behavior explicit in numeric input.
Tishri-first numbering keeps the numeric input aligned with the civil Hebrew year used by this page. It also makes the result labels predictable across common years and leap years.
Other Hebrew calendar references may choose a different month-order convention, so always check the expected numbering before entering a date.
No. Convert the month to this page's Tishri-first numbering before entering the date.
Entering Nisan-first numbers directly would point the converter at a different month than intended. Convert the month number first, then use the displayed month label to verify the result.
This extra step prevents subtle errors in datasets where only numeric Hebrew dates are stored.
No. It converts civil calendar dates only and does not calculate sunset, candle-lighting, or local observance times.
Halachic timing depends on location and time of day, while this converter only maps whole dates between calendars. It cannot determine when a holiday begins in a specific city.
For observance planning, pair this date lookup with a trusted local Jewish calendar or authority.
