Namsor

Split name - Separate first names from their last names

Namsor's software offers a name separation technology. We are able to split a full name into a first name and last name structure.

A full name is the set of names by which a person is known. It is often composed of two elements: a first name (given name) and a last name (surname). It can sometimes include middle names.
The order of the first name and the last name differs according to the different regions of the world and the alphabets.

Split a full name into a first and last name structure

Separate an unsplit full name into a first name and surname structure. Improve the accuracy when splitting the full name by adding a country of residence.

Local context improves accuracy.

Split name: full name

Ideal feature for dividing a complete name:

Full name (first name and last name).

information

How to interpret the returned values

Use our Full Name Splitter, available via API or a simple web interface, to accurately break down a full name into first and last name components. Here's how it works:

  • First name indicator

    First name (extracted from the submitted full name) A first name is the part of a personal name that identifies a person and differentiates them from other members of a group. It is also called a given name. The first name may also include middles names.

  • Last name indicator

    Last name (extracted from the submitted full name) A last name is the part of a personal name that usually indicates a person's family, tribe or community. It is also called surname or family name.

  • Name structure indicator

    Name structure (FN1LN1, LN2FN1, etc.) The most likely arrangement of the name components, where FN = first name and LN = last name. The numbers indicate the position of each component when multiple first or last names are present.

  • Writing system indicator

    Script (Latin, Cyrillic, etc.) Detects the script used, offering linguistic and cultural insights.

Find the right tool to process names

Process names using our comprehensive API documentation, CSV and Excel tools, or developer resources. Choose the method that best fits your name analysis needs.

A group of people from different backgrounds processing an Excel file using software.

CSV and Excel Tool

Upload your document using our CSV and Excel file processor and select your preferred classification type.

Download comprehensive name analysis results including gender, country of origin, ethnicity, diaspora and additional demographic insights.

Process a CSV or Excel file
Two people interacting with computer servers.

API Documentation

Integrate name processing capabilities into your systems using our fully documented API.

Access Namsor's name analysis features efficiently with integration examples for JavaScript, Python, Java, and Shell.

Explore the API Documentation
Groups of invdividuals building software using different modules.

Developer Tools

Access advanced name processing capabilities using our SDK and CLI options for Java, Python, GoLang, and JavaScript.

These tools integrate name analysis technology directly into your applications for comprehensive demographic insights.

Download Developer Tools

Frequently asked questions about name parsing

How does Namsor's name parser handle non-Western naming conventions?

Namsor's Split Name feature relies on predictive AI models capable of correctly splitting a full name into given name and family name, regardless of the order or cultural structure of the name. The model has learned the patterns specific to each onomastic tradition from billions of names, and adapts the split to the detected cultural context, without applying hard-coded rules.

Here are some examples that illustrate the diversity of conventions correctly handled.

East Asian names: reversed order

In Chinese, Japanese and Korean, the family name comes first. Namsor recognizes this convention and reverses the order:

  • 毛泽东 (Chinese) → 泽东 (given name) + 毛 (family name)
  • 山田太郎 (Japanese) → 太郎 (given name) + 山田 (family name)

Arabic patronymic names

Arabic naming conventions use patronymic markers like "bin" (son of) or "bint" (daughter of). Namsor identifies the structure and places each element correctly:

  • محمد بن سلمان → محمد (given name) + بن سلمان (patronymic family)

Icelandic patronyms

Icelandic names use patronyms (son/daughter of) rather than hereditary family names:

  • Björk Guðmundsdóttir → Björk (given name) + Guðmundsdóttir (patronym)

Hispanic compound names

Hispanic naming conventions combine a compound given name with a double family name (paternal + maternal). Namsor preserves both:

  • Gabriel García Márquez → Gabriel (given name) + García Márquez (double family name)
  • María del Carmen López García → María del Carmen (compound given name) + López García (double family name)

Native scripts, no transliteration required

The feature handles names in their native writing systems without requiring transliteration to Latin first. Whether the input is in Han, Arabic, Cyrillic, Devanagari or any of Namsor's 22 supported scripts, the model splits the name directly.

These examples are only a glimpse: the model relies on patterns learned at scale and continues to perform well on rare or mixed conventions it has never explicitly encountered.

How does geographic context improve name parsing accuracy?

Namsor's name parser works well from a name alone, but adding a country code helps resolve structurally ambiguous names where the same sequence of words could be parsed differently depending on the cultural context.

Why name structure can be ambiguous

Different cultures structure names differently: some place the family name first, others last. Some use compound given names, others use compound family names. Some include patronymic markers or particles that change position by convention.

When a name could plausibly follow more than one convention, the country code tells the parser which set of cultural expectations to prioritize.

Two parsing modes, same cost

Namsor offers two parsing modes at the same cost (1 credit per name):

  • Standard mode (Split Name): parses using the globally most likely convention
  • Geo mode (Split Name Geo): parses using the locally expected convention when a country code is provided

When to use Geo mode

  • Your dataset mixes names from multiple cultural backgrounds and you know each person's country
  • You work with an international CRM or HR system with a global workforce
  • You process research datasets that combine names from different regions

When country data is unavailable, Standard mode remains highly accurate thanks to Namsor's morphological analysis, which detects cultural patterns directly from the name structure.