Babylonian Numerals

Overview

The Babylonian Numerals converter turns ordinary base-10 integers into their Babylonian cuneiform equivalent — the wedge-mark numerals used in Mesopotamia roughly four thousand years ago. The output is rendered with Unicode cuneiform characters so you can copy and paste the result straight into a document or slide.

History students writing about Hammurabi, museum docents preparing exhibit labels and tabletop game designers building flavour text for ancient-world settings all run into this need. The converter handles long-tail queries like "convert number to Babylonian cuneiform", "base 60 sexagesimal numeral converter" and "Mesopotamian numeral system online".

How it works

The Babylonian system is sexagesimal, meaning it uses base 60 rather than base 10. Numbers are written as positional digits where each digit takes a value from 1 to 59 and is itself composed of vertical wedges for ones and chevron wedges for tens. There is no proper zero — the Babylonians left a gap or, later, used a placeholder — so the converter inserts a small separator between place values.

The algorithm divides the input by 60 repeatedly, collecting remainders, then renders each remainder as the appropriate combination of ten-wedges and one-wedges. Inputs above 60 produce a multi-place expression; inputs from 1 to 59 produce a single cluster of wedges.

Examples

1   →  𒁹

12  →  𒌋𒁹𒁹

60  →  𒁹 𒑊

3661  →  𒁹 𒁹 𒁹  (1 × 3600 + 1 × 60 + 1)

FAQ

Why is there no Babylonian zero?

Early Babylonian scribes left a literal space where a place value was empty. Later scribes used a double-wedge placeholder, but no symbol functioned as our modern zero with arithmetic meaning until the Indian numeral system centuries afterwards.

What range of numbers does the converter accept?

Any positive integer up to several million. Very large inputs produce long strings of wedges that can be hard to interpret visually, even though they are arithmetically correct.

Are negative numbers supported?

No. Babylonian arithmetic recorded magnitudes in context; signed numbers as a unified concept did not exist. The converter requires a non-negative integer.

Why base 60?

The exact origin is debated. The leading theory is that 60 has many divisors (1, 2, 3, 4, 5, 6, 10, 12, 15, 20, 30) which made fractions easy to express, useful for astronomy, trade and timekeeping. We still inherit base 60 in minutes, seconds and angle measures.

Will the cuneiform characters render in any browser?

Modern browsers with a Unicode cuneiform-capable font handle them. If you see boxes, install Noto Sans Cuneiform or a similar font.

Try Babylonian Numerals