nameparser

nameparser parses human names into seven fields — title, given, middle, family, suffix, nickname, maiden. Results are immutable, configuration is composable, and locale packs are opt-in.

📣 nameparser 2.0 is out. Existing HumanName code keeps working through 2.x, and most 1.x code needs no changes. The migration guide has the field-by-field map. Please open an issue for anything that parses wrong.

2.1 adds East Asian name support. Chinese, Japanese and Korean names written in their own scripts are read family-first, unspaced Korean names are split against the census surname list, and CJK honorifics are recognized. See East Asian names.

Installation

pip install nameparser

Requires Python 3.11+.

Quick Start Example

>>> from nameparser import parse
>>> name = parse("Dr. Juan Q. Xavier de la Vega III (Doc Vega)")
>>> name
<ParsedName: [
    title: 'Dr.'
    given: 'Juan'
    middle: 'Q. Xavier'
    family: 'de la Vega'
    suffix: 'III'
    nickname: 'Doc Vega'
]>
>>> name.family_base, name.family_particles
('Vega', 'de la')
>>> name.given_names, name.surnames
('Juan Q. Xavier', 'Q. Xavier de la Vega')
>>> name.render("{family}, {given}")
'de la Vega, Juan'

>>> parse("김민준").family                     # Korean: unspaced, split on the census list
'김'
>>> parse("高橋 みなみ").family                 # Japanese: kanji with kana, family first
'高橋'
>>> parse("김민준씨").suffix                   # an honorific written against the name
'씨'
>>> parse("г-н Иван Петров").title             # Cyrillic title
'г-н'
>>> parse("محمد بن سلمان").family              # Arabic: بن chains onto the family name
'بن سلمان'

>>> from nameparser import locales, parser_for
>>> chinese = parser_for(locales.ZH)           # Han text does not say which language
>>> chinese.parse("毛泽东").family              # so splitting it is opt-in
'毛'
>>> russian = parser_for(locales.RU)
>>> russian.parse("Сидоров Иван Петрович").family
'Сидоров'
>>> locales.available()
('ja', 'ru', 'tr_az', 'zh')

Learn more

Using the parser — the full tour: input shapes, aggregates, rendering, comparison, ambiguities, tokens
Customizing the parser — vocabulary, behavior, and presentation
Locale packs — opt-in bundles for East Slavic patronymics, Turkic markers, and more
There’s also a CLI: python -m nameparser --json "Doe, John"

Coming from 1.x

HumanName and CONSTANTS keep working in 2.0 — same imports, same attributes, same mutation API. What 2.0 removes is the batch of deprecations 1.3 and 1.4 announced, so if your test suite runs clean on 1.4 under python -W error::DeprecationWarning, you are nearly done. Two things that check will not catch: four removals 1.4 never warned about (three raise on contact, the fourth only warns), and one that changes results silently — name == "John Smith" is now False. Migrating from HumanName covers both, and translates a v1 customization into the new API whenever that’s convenient for you.

See the release log for the full list of changes in the 2.0 series.

License

LGPL licensed. See LICENSE for details.

Release files for nameparser 2.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for nameparser 2.3.0
File	Size	Uploaded
nameparser-2.3.0.tar.gz	751.5 kB	Sep 12, 2026	Details

Built distribution (wheel)

Table of built distributions (wheels) for nameparser 2.3.0
File	Interpreter	ABI	Platform	Reset
nameparser-2.3.0-py3-none-any.whl 256.4 kB Sep 12, 2026	Python 3	none	any	Details

Total release size: 1.0 MB

Release files / nameparser-2.3.0.tar.gz

Download URL	nameparser-2.3.0.tar.gz
Size	751.5 kB
Tags	Source
SHA-256 checksum How to use checksums	`ae169bcd35d817908644e7ab580cb999a85191414e870c02bda1c52364c9e1f0`
BLAKE2b-256 checksum How to use checksums	`5b1a9b4b5d076a7bec1c50b3eeb67f06ca413d7b8770ae07b78a62d816607db2`
Upload date	Sep 12, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/derek73/python-nameparser
Publishing commit: github.com/derek73/python-nameparser/tree/1c89e2ed96644c55c587bfb79402c0dc190dd396

Workflow

Publishing configuration: github.com/derek73/python-nameparser/blob/1c89e2ed96644c55c587bfb79402c0dc190dd396/.github/workflows/python-publish.yml
Publishing logs: github.com/derek73/python-nameparser/actions/runs/34716146880/attempts/1

Artifact

Subject: nameparser-2.3.0.tar.gz
SHA-256 checksum: ae169bcd35d817908644e7ab580cb999a85191414e870c02bda1c52364c9e1f0 Verifying attestations

Release files / nameparser-2.3.0-py3-none-any.whl

Download URL	nameparser-2.3.0-py3-none-any.whl
Size	256.4 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`0960c101716aba9e4fbbe51fa94ad57d5d010b550ff3dba5a7b7e6a1331bb05c`
BLAKE2b-256 checksum How to use checksums	`88993c9396b487cdfc88b7b4ca4c4c041552924b4b5e2070835ab2df2e4d7194`
Upload date	Sep 12, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/derek73/python-nameparser
Publishing commit: github.com/derek73/python-nameparser/tree/1c89e2ed96644c55c587bfb79402c0dc190dd396

Workflow

Publishing configuration: github.com/derek73/python-nameparser/blob/1c89e2ed96644c55c587bfb79402c0dc190dd396/.github/workflows/python-publish.yml
Publishing logs: github.com/derek73/python-nameparser/actions/runs/34716146880/attempts/1

Artifact

Subject: nameparser-2.3.0-py3-none-any.whl
SHA-256 checksum: 0960c101716aba9e4fbbe51fa94ad57d5d010b550ff3dba5a7b7e6a1331bb05c Verifying attestations