Name Parser
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.4 is out. It uses letter case to read post-nominal credentials much more reliably — Jack MA is Jack with an MA and Jack Ma is the surname Ma, and Jane Smith, PhD MA keeps both credentials together — recognizes more naming conventions (Catalan, Irish, Finnish, Malay and others), and writes credentials the usual way when it repairs case. The release log has the details.
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.
Existing HumanName code from 1.x keeps working through 2.x, and most of it needs no changes; see Coming from 1.x below. Please open an issue for anything that parses wrong.
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("Jack MA").suffix # capitals mark a credential
'MA'
>>> parse("Jack Ma").family # and a surname
'Ma'
>>> parse("Jane Smith, PhD MA").suffix
'PhD MA'
>>> 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. Later 2.x releases add a few breaks of their own. Migrating from HumanName covers all of them, 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.
1 maintainer
Metadata
1 maintainer
Release files for nameparser 2.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| nameparser-2.4.0.tar.gz | 1.2 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nameparser-2.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.5 MB
Release files / nameparser-2.4.0.tar.gz
| Download URL | nameparser-2.4.0.tar.gz |
|---|---|
| Size | 1.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e5e56006d342a3d54ce09b5a91476ddbfb04ea0c9038b2649f7ba26c90c982e3
|
|
BLAKE2b-256 checksum How to use checksums |
527bf4ba4a0568325955ba936ca7c9ea27273478720de2180bc301695037cc02
|
| Upload date | |
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.
Transparency logRelease files / nameparser-2.4.0-py3-none-any.whl
| Download URL | nameparser-2.4.0-py3-none-any.whl |
|---|---|
| Size | 362.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
662e5ef60d040b60c32d4328396e5e8238c8ec44e66cfbebb18439cb89fea6da
|
|
BLAKE2b-256 checksum How to use checksums |
153958294b6273b0554e3ea68a68851409be8652556db5ec83b50b61092f0e8a
|
| Upload date | |
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.
Transparency log
