← Blog

Pythagorean vs Chaldean numerology — what actually differs

·2 min read

Most numerology you encounter in English is Pythagorean. The older Chaldean system is still widely practised, and the two are not variations on a theme — they disagree at the level of the alphabet.

The letter grids

Pythagorean assigns 1–9 in order, straight through the alphabet:

1 2 3 4 5 6 7 8 9
A B C D E F G H I
J K L M N O P Q R
S T U V W X Y Z

Chaldean assigns 1–8, with no letter valued 9, and the order is not alphabetical:

1 2 3 4 5 6 7 8
A I J Q Y B K R C G L S D M T E H N X U V W O Z F P

Nine is held back deliberately — it is treated as sacred in the Chaldean tradition and not assigned to any letter, though it can still appear as the result of a calculation.

What that does to a name

Take SARAH.

Pythagorean: S=1, A=1, R=9, A=1, H=8 → 20 → 2

Chaldean: S=3, A=1, R=2, A=1, H=5 → 12 → 3

Same name, same method of reduction, different number. Neither is a mistake.

The deeper disagreement: which name?

The grids get the attention, but the more consequential difference is about input.

Pythagorean numerology uses the full name as recorded at birth. The name on the birth certificate, including middle names and both surnames, is treated as the fixed datum — a married name or a chosen name does not replace it.

Chaldean numerology weights the name in current use. The name people actually call you by is the one that matters, so it changes when you change.

This is a bigger practical difference than the letter values. It means the two systems will often be reading two different strings before any arithmetic begins.

Master numbers

Pythagorean recognises 11, 22 and 33 as master numbers that halt reduction. Chaldean practice commonly recognises 11 and 22 and treats compound numbers (the two-digit total before final reduction) as carrying meaning in their own right — so a Chaldean reading often quotes something like “37/1”, keeping both.

Which should you use?

If you are building something, the honest answer is: whichever your audience expects, and say which.

  • English-language, Western, mass-market numerology content is overwhelmingly Pythagorean. If you are matching what a reader will find elsewhere, that is the safe default.
  • If your audience comes from a tradition where Chaldean is standard, matching Pythagorean will produce numbers they consider wrong.

What does not work is picking one and staying quiet. The results differ enough that a user comparing your output against another source will conclude one of you is broken.

What this API does

Simple Numerology API is Pythagorean, and specific about it: the grid above, the full birth name including middle names and compound surnames, Y always a consonant, master numbers 11/22/33 preserved through reduction.

Those choices are published and treated as frozen, because changing one would silently alter every chart previously computed.

It does not compute Chaldean charts. If your audience expects Chaldean numbers, a Pythagorean result will look wrong to them however correct it is, so it is better to know that before you integrate.

Compute this properly, in one request

47 Pythagorean fields from a name and a date of birth, to the conventions described above. 100 charts a month free, no card. Quickstarts for Python and JavaScript.

Get a free key

Keep reading