Korean Name Generator

The installed Faker 9.9.0 Korean locale has 301 male and 300 female given-name entries, plus 112 surnames. Every entry is written in Hangul. Sixty-one given names sit in both gender lists, including 지우, 하윤 and 지민. Choosing a gender picks a source list; it does not make a name exclusive to that gender. Most entries have two syllables; seven male and six female entries have one.

Each surname has the same chance of being drawn, so 김 (Kim) comes up about once in 112 names. Real Korean surnames are far more concentrated. In Statistics Korea’s 2015 census results, linked in Sources, 21.5% of people were named Kim, 14.7% Lee and 8.4% Park. The census counted 5,582 surnames in all. Those figures are a reference for your research. They do not weight this generator, so a rare surname such as 피 (Pi) appears as often as Kim.

The surname list has no two-syllable surnames, such as 남궁 (Namgung) or 제갈 (Jegal). If your form must handle them, add them to your own test cases. Check that Hangul survives copying, CSV import and a JSON round trip. Downloads keep the full name in one field, surname first. For separate columns, use the bulk test data generator. The name validation test cases cover name order and other edge cases.

South Korea's road-name address system separates the road name, building number and additional details. Juso, the government's address information service, provides the authoritative lookup. The current postcode has five digits; the UPU records the replacement of the former six-digit system in August 2015. In its Roman-alphabet examples, the postcode follows the locality. Apartment building and unit components can appear as dong and ho. Keep those components distinct from the main building number instead of collapsing every number into a generic apartment field.

A useful Korean address test set includes a road with a simple building number, a number with an extension, and a building complex with a separate unit line. The example diagram is an invented fixture showing those roles, not a Juso-verified destination. Check that commas, hyphens and the leading zero in a postcode such as 04542 survive CSV imports. Also check the Korean-script version of a label separately from its romanized representation; a system can render one correctly while truncating the other. A postcode input should remain a text field, even when all accepted characters are digits.

On this page the name pool is Korean, but the geographic anchors are romanized city records. The engine samples from fifteen configured city records, including Seoul, Busan and Incheon, and chooses a code from the selected record's list. Street details are generated separately rather than looked up in the government's road-name database. Consequently a generated profile is a format fixture and a rough geographic example, not proof that its road, building and postcode agree at delivery-point level. Coordinates are scattered near the selected city; they do not locate the invented building.

Korean names and English-oriented form assumptions are another useful boundary. Our engine preserves Korean-script given names and surnames and suppresses an ASCII fallback middle name when the given name is non-Latin. The combined profile shows the surname first with no space, as Korean names are written. Use the exported fields rather than splitting that display string, because it has no separator to split on. Run a generation, a profile copy and a JSON import through your own application, then compare field values before and after. The methodology page explains why rendering tests and address-verification tests need different fixtures.