How to convert a Shamsi (Jalali) date to Gregorian (Miladi)

If you have a date written in the Persian Solar Hijri calendar (Shamsi, also called Jalali) and you need the matching date in the Gregorian calendar (Miladi), this guide walks you through it. The quickest route is to type or paste your date into the converter and read the result. The steps below explain what is happening so you can trust the answer and check it by hand if you ever need to.

The quick way

1. Open the Timeyard converter.
2. Enter your Shamsi date as year, month and day — for example 1403/01/01. You can type Western digits or paste Persian digits such as ۱۴۰۳/۰۱/۰۱.
3. Read the Gregorian (Miladi) date shown in return.

The conversion runs entirely in your browser. There is no server call, nothing is uploaded, and it works offline once the page has loaded. For the reverse direction, see converting a Gregorian date to Shamsi.

Understanding the two calendars

The Shamsi calendar is a solar calendar: its year tracks the seasons, just like the Gregorian one. That is why the two stay roughly aligned year after year, unlike a lunar calendar that drifts. The key difference is where the year starts. The Persian year begins on Nowruz — 1 Farvardin — which falls on or around 20–21 March. So a single Shamsi year always straddles two Gregorian years: it starts in one March and ends in the next.

Because of that overlap, the most common slip when converting is choosing the wrong Gregorian year. Knowing roughly where Nowruz sits is the anchor that keeps you on track.

The Nowruz anchor

To convert by reasoning rather than by tool, start from Nowruz. The first day of the Persian year lands in late March, so any Shamsi date from 1 Farvardin up to the end of Esfand maps onto a Gregorian span that runs from one March into the following year.

A few anchor pairs are worth memorising because they pin the whole year down:

Notice that Nowruz is not always on the same Gregorian day — it shifts by a day depending on leap years. The converter handles this for you; the anchors above are simply useful reference points.

A worked example

Suppose you want to convert 15 Mehr 1403. Mehr is the seventh Persian month, so this date sits well after Nowruz 1403 (which was 20 March 2024). The Persian months Farvardin through Shahrivar each have 31 days, and Mehr begins the run of 30-day months. Counting forward from Nowruz lands you in early October — and the converter confirms the exact day. The fastest, most reliable approach is to let the tool compute it: enter 1403/07/15 and read the Gregorian date back.

For a date near the start of the year, the year choice matters most. 5 Farvardin 1404 falls just after Nowruz 1404, so it lands in late March 2025 — not 2024. Mixing those up is the classic off-by-one-year error. When in doubt, anchor to the nearest Nowruz first.

Why the result is reliable

The converter uses the well-established jalaali-js library, which implements the proven 33-year arithmetic leap-year cycle — Persian leap years do not follow the simpler Gregorian rule. It works with a date-only model (no clock time), so time zones never shift the answer, and it cross-checks every result against the browser's built-in Persian calendar. A date is accepted only when both calendars agree on it and the converted year falls within the supported range: Shamsi years 1–1700 and Gregorian years 622–2322. To learn more about how leap years differ, see the leap years guide, and for the full list of month names and lengths, the Persian months guide.

Tips to avoid mistakes

• Watch the year at the boundary. Dates in Farvardin or Esfand sit right at the March changeover — double-check which Gregorian year you land in.
• Keep the order consistent. Enter year, then month, then day. The tool reads Persian and Arabic-Indic digits, so pasting an official date works fine.
• Check it both ways. Convert your result back with the Gregorian-to-Shamsi guide to confirm you return to where you started.

For everyday conversions — birthdays, documents, history — the converter is the simplest path. If you run into a tricky case, the common mistakes guide and the FAQ cover the edge cases in more detail.