Russian Romanization (Transliteration)

Cyrillic to Latin under GOST, ISO 9, BGN/PCGN, or Passport schemes

Transliterates Russian Cyrillic into Latin script under four official schemes — GOST 7.79 System B, ISO 9, BGN/PCGN, and the Russian passport rules — each handling ъ, ь and й differently. Runs entirely in your browser. It runs free in your browser on Gera Tools, with nothing uploaded.

Last updated Source: Gera Tools

Which scheme should I use?

For official Russian travel documents use the Passport scheme. ISO 9 gives a strict reversible one-letter-per-letter mapping for libraries and databases. BGN/PCGN is the readable English-oriented standard used on maps. GOST 7.79 System B is an ASCII-only reversible system for technical use.

The Russian Romanization tool converts Cyrillic into the Latin alphabet under four widely used standards. There is no single correct way to romanize Russian — libraries, mapmakers, and passport offices each chose different rules — so the same name can be spelled several ways. This tool lets you pick the scheme your form, database, or document requires.

Why four different schemes exist

Each standard was designed for a different purpose and audience, which is why they diverge:

  • ISO 9:2005 is an international library standard built for unambiguous, reversible transliteration. Every Cyrillic letter maps to exactly one Latin letter (sometimes with diacritics), so a machine can convert back to Cyrillic without ambiguity. Librarians and database architects use it.
  • GOST 7.79 System B is the Russian national standard equivalent of ISO 9, but uses only ASCII — no diacritics. Where ISO 9 uses ž for ж, GOST System B uses zh. This makes it safe for legacy systems that cannot handle Unicode Latin characters. It is still reversible.
  • BGN/PCGN (Board on Geographic Names / Permanent Committee on Geographical Names) was designed by anglophone cartographers to produce spellings that English speakers pronounce correctly on first attempt. It sacrifices reversibility for readability: ы becomes y, щ becomes shch, and х becomes kh.
  • Russian Passport rules are used by the Russian government on international travel documents. They resemble BGN/PCGN but drop the hard and soft signs entirely and make a few different choices (е → e, ю → yu, я → ya).

The per-letter mapping tables

Each scheme is a per-letter mapping table applied across your text. The interesting differences live in a handful of letters:

LetterISO 9GOST System BBGN/PCGNPassport
йjjyi
ъ (hard sign)ʺʺdropped
ь (soft sign)ʹʹdropped
щŝshhshchshch
хhxkhkh
жžzhzhzh
шšshshsh
чčchchch
цccz / ctsts
эèe`ee

ISO 9 and GOST System B are strictly reversible (one Latin token per Cyrillic letter), while BGN/PCGN and the passport rules trade reversibility for English readability.

The same name across four schemes

Take the name Щербаков as a concrete illustration:

  • ISO 9: Ŝerbakov
  • GOST System B: SHHerbakov
  • BGN/PCGN: Shcherbakov
  • Passport: Shcherbakov

Or Александр Ельцин (Alexander Yeltsin in English):

  • ISO 9: Aleksandr Elʹcin
  • GOST System B: Aleksandr El’czin
  • BGN/PCGN: Aleksandr Yel’tsin
  • Passport: Aleksandr Eltsin

The same person can appear as four different strings across a passport, a library catalogue, a map, and a database record — which is why any matching system that spans these sources needs to be aware of all four schemes.

Tips

  • For a name on an official Russian travel document, choose Passport — using ISO 9 there will produce a spelling the authorities do not recognise.
  • For catalogues and databases that must round-trip back to Cyrillic, use ISO 9 or GOST System B.
  • For English-readable transliteration of place names or personal names in prose, BGN/PCGN produces spellings that English speakers are most likely to pronounce correctly.
  • Letter case is preserved: an upper-case Cyrillic letter yields an upper-case (or title-case) Latin equivalent, so proper nouns stay capitalised.

Reversible vs readable: pick by purpose

The single most important choice is whether you need to get the Cyrillic back or just want an English-readable spelling — the two goals are mutually exclusive past a point:

  • Need a round-trip? Use ISO 9 or GOST 7.79 System B. Each Cyrillic letter maps to a unique Latin token, so a program can reconstruct the original unambiguously. This is why library and archive systems standardise on them.
  • Need a name a reader can pronounce? Use BGN/PCGN. It collapses several Cyrillic letters onto the same Latin spelling (е and э can both surface as e), which is fine for a map or an article but breaks automated reversal.
  • Filling an official Russian form? Use the Passport scheme and nothing else — an ISO 9 spelling of your own name will not match the document the authorities expect.

Why this causes real-world data problems

Because a single person can legitimately appear as four different Latin strings, any system that ingests names from mixed sources — a passport scan, a library record, a map gazetteer, a legacy database — must either normalise everything to one scheme or match across all four. Failing to do so is a classic cause of duplicate customer records and failed identity matches. Running text through each scheme here is a quick way to see which variant a given source is likely using.

Sources