Quick answer

Almost all clinical care uses gestational age. If a figure is about two weeks off what you expected, the two measures are the likely reason.

Why the clock starts before conception

Gestational age is counted from the first day of the last menstrual period — a date that can actually be observed and recorded. Conception cannot be, in a spontaneous pregnancy, so the convention anchors on the event that can be dated and accepts a systematic offset in exchange for reliability.

The offset is roughly two weeks, because conception typically occurs around day 14 of a 28-day cycle. So at the moment of conception a pregnancy is already dated at about two weeks gestational age, and a "12-week" pregnancy involves an embryo that has been developing for around ten.

Use this guide with the right tool: Open the Gestational Age Calculator for gestational age from the first day of the last menstrual period. If the question shifts, compare it with the Fetal Age Calculator or the Conception Date Calculator.

Which one you will actually encounter

Gestational age is the clinical standard almost everywhere: appointment schedules, screening windows, growth assessment, viability thresholds and the 40-week due-date model all use it. If a midwife, obstetrician or scan report gives a number in weeks and days, it is gestational age unless it says otherwise.

Fetal age appears mainly in embryology, in some IVF contexts where the conception date is known, and in general-audience material that finds "time since conception" more intuitive. It is not wrong, but reading it as gestational age puts a pregnancy two weeks ahead of where care is scheduled.

An expectant mother resting with hands on her belly
Gestational age starts two weeks before conception — fetal age is the younger number.

The two-week rule is an approximation

The offset assumes ovulation on day 14 of a 28-day cycle. Real cycles vary in length, and the variation sits mostly in the follicular phase before ovulation — so someone with a 35-day cycle may ovulate around day 21, making the true gap closer to three weeks.

This is one of the reasons LMP-based dating gets revised after a dating scan. Ultrasound measures the embryo directly rather than inferring from a cycle assumption, which is why scan dating supersedes LMP dating when the two disagree beyond a defined tolerance.

Reading a number safely

When you see an age in weeks, check three things: whether it is gestational or fetal, what date it was measured on, and what it was derived from — LMP, a scan, or an IVF transfer date. Those three make the figure interpretable and comparable with anything else in the notes.

Where two sources disagree, the difference is very often exactly the two-week offset or a dating revision, not an error. Bringing both figures to an appointment is more useful than trying to reconcile them yourself.

Worked example

A pregnancy at 12 weeks 0 days gestational age has an estimated fetal age of about 10 weeks. Both describe the same pregnancy on the same day. A scan report giving 12+0 and an app giving 10 weeks are not in conflict — they are using different starting points.

At 12 weeks 0 days, fetal age is about 10 weeks, two weeks behind because the starting points differ. Try your own dates and check which start each figure uses.

One pregnancy at three checkpoints

The worked example compares the two ages at a single moment: 12 weeks gestational, about 10 weeks fetal. Pinning that comparison to actual dates, across the whole pregnancy, shows the offset being created, holding steady, and following the pregnancy to its end. Take a last menstrual period of 21 May 2026, the standard model throughout: ovulation and conception estimated on day 14, and a 280-day span to the estimated due date.

The first checkpoint is the moment the offset is born. On 4 June 2026, the estimated conception date, the pregnancy is already dated at 2 weeks 0 days gestational age — while the fetal age is zero, because development has only just begun. Nothing has been measured twice or rounded. The two-week gap is present in full before there is anything to measure, because it is a property of where the gestational clock starts, not of how the pregnancy develops.

The second checkpoint is the worked example with a date attached. On 13 August 2026, 84 days after the LMP, the gestational age is exactly 12 weeks 0 days — the figure a scan report would carry. The fetal age, counted from the estimated conception, is 70 days: 10 weeks 0 days. Same pregnancy, same day, two correct numbers, differing by precisely the fortnight built into the model on day one.

The third checkpoint is the end. On 25 February 2027, the estimated due date, gestational age reaches 40 weeks 0 days — the full term of the conventional model. The fetal age on that date is 266 days, or 38 weeks: the embryo and fetus have been developing for thirty-eight weeks inside a pregnancy the records describe as forty. Anyone comparing a "weeks pregnant" figure from a clinical source against a "weeks of development" figure from an embryology source will find this same two-week seam at whatever point they compare them, because it was stitched in at the start and never widens or closes.

The seam can move, though — once, at dating. The checkpoints above assume ovulation on day 14. With a 35-day cycle, ovulation falls around day 21, putting conception near 11 June 2026. On 13 August 2026 that pregnancy reads 12 weeks 0 days gestationally, like the other, but its fetal age is 63 days — 9 weeks, not 10. The offset is three weeks rather than two, and this is the discrepancy a first-trimester dating scan exists to find: it measures the fetus directly, and where the measurement disagrees with the LMP model, the dates are re-anchored. After that revision the two ages settle back into a fixed relationship — but around the scan's starting point, not the cycle's.

Common mistakes to avoid

  • Using the two terms interchangeably. They differ by about two weeks by definition. Label which measure a figure uses.
  • Assuming conception happened on day 14. Cycle length varies, and so does the offset. This is why scan dating supersedes LMP dating.
  • Treating an estimate as a substitute for clinical dating. Ultrasound and clinical assessment set the working dates. A calculator explains how a figure was derived.

Use the right calculator

Gestational Age Calculator counts from the last menstrual period, Fetal Age Calculator derives fetal age, and Conception Date Calculator estimates the conception window.

Gestational Age Calculator
Pregnancy & PediatricGestational Age Calculatorgestational age from the first day of the last menstrual period
Fetal Age Calculator
Pregnancy & PediatricFetal Age Calculatoran approximate fetal age derived from gestational age
Conception Date Calculator
Pregnancy & PediatricConception Date Calculatoran estimated conception window from LMP or due date
Pregnancy dates stay private here: the period and scan dates you enter are calculated in your browser, no account is required, and nothing is sent to a server.

Frequently asked questions

Which age do scan reports use?

Gestational age, in completed weeks and days, unless the report explicitly states otherwise.

Why is a pregnancy 'two weeks along' at conception?

Because the count starts at the last menstrual period, which precedes conception by roughly two weeks under the standard model.

Can I convert between them reliably?

Only approximately. Subtracting two weeks is the convention, but the real offset depends on cycle length and ovulation timing.