Blog
Apellidos means surname(s) or family name(s). Primer apellido means first surname, and segundo apellido means second surname when the document separates those fields. Translate each label and reproduce its name value in the source field and order. Do not automatically convert primer apellido to “paternal surname” or segundo apellido to “maternal surname”: country rules, chosen order, family circumstances and the record itself can differ. If the source shows only an unlabeled full name, do not invent a split. A receiving form may group names differently, so its current instructions control data entry; a translation does not decide legal identity or guarantee acceptance.
Scope
Use this guide when a Spanish civil, identity, academic, legal, medical or business document labels one or more surname fields that must remain understandable in English. It explains terminology, source-field boundaries and translation review. It does not complete an application, decide a legal name, establish parentage, reconcile conflicting records, correct an issuing record, or provide legal, immigration or government advice.
Customers reading birth, marriage, identity or school records with Apellidos, Primer apellido or Segundo apellido fields.
Teams comparing Spanish source-field structure with an English translation or a separate receiving form.
People requesting a quote for one document or a packet in which surname fields are labeled or grouped differently.
Table of contents
Step-by-step explanation
Apellidos is a label for the surname portion of a name and may head one box containing one or more surname elements. Primer apellido and segundo apellido are ordinal field labels: they tell the reader which surname field comes first and which comes second on that record. Translate the labels in context, then keep each visible value in its source field. Do not use a familiar cultural pattern to manufacture fields the document does not show.
Original fictional example: “Nombre(s): Ana Lucía / Primer apellido: De la Vega / Segundo apellido: Ríos” can be rendered “Given name(s): Ana Lucía / First surname: De la Vega / Second surname: Ríos.” The labels change language; the fictional values and field order do not.
Check whether the document says Apellido, Apellidos, Primer apellido, Segundo apellido, Apellido paterno, Apellido materno, Nombre(s) or Nombre completo. Record which value sits under each heading and whether lines, columns or punctuation separate the fields.
Original fictional example: a card places “Apellidos” above “Luna Torres” in one box. Preserve that one-box relationship instead of inventing separate first- and second-surname rows.Surname and family name are common English equivalents. Use a consistent term that fits the document and requested English variety. A plural Spanish label can be rendered surname(s) when the field may contain more than one surname element; do not force every Apellidos box into a single “last name.”
Original fictional example: “Apellidos: Cordero Paz” becomes “Surname(s): Cordero Paz” in a translation that uses surname terminology throughout.Render Primer apellido as First surname and Segundo apellido as Second surname when those are the printed labels. Do not replace ordinal labels with paternal or maternal unless the source explicitly uses Apellido paterno or Apellido materno. A country rule or common pattern is context, not permission to change the label.
Original fictional example: “Primer apellido: Salas” remains “First surname: Salas”; the translation does not add “father’s” when the source does not.Spaces, hyphens, articles, prepositions and conjunctions can be part of the visible surname value. Preserve the complete value assigned to the labeled field. Do not split De la Fuente, Del Río or García y Vega into extra surname fields merely because they contain spaces or connecting words.
Original fictional example: “Primer apellido: De los Santos” is one first-surname field value, not three separate surnames.Keep the first and second fields in the source order, preserve a blank or crossed-out field according to the approved notation, and compare headers, body text, stamps and signature blocks. Never move the second value into the first field or populate a blank from another record. If a separately supplied record is relevant, identify it through a distinct, clearly labeled approved treatment that does not attribute its value to the blank source field.
Original fictional example: a form shows “Segundo apellido: —”. The translation preserves the displayed dash or approved blank-field notation; it does not borrow a surname from a passport.When the source presents one Nombre completo or full-name line, reproduce that full value and translate only the label. A translator should not guess where given names end and surnames begin from word count, capitalization or a presumed national convention. Ask for a labeled supporting record only when the project genuinely needs clarification.
Original fictional example: “Nombre completo: María Paz del Valle Cruz” stays one full-name value; the translation does not decide whether “Paz” is a given name or surname.An English application may offer one surname box, separate family-name fields or character limits that do not mirror the source. Keep the translation source-faithful. For data entry, follow the current instructions from the actual receiver or ask that organization how it wants multiple surnames entered. Record any approved project presentation without rewriting the source.
Original fictional example: a certificate has two surname fields while a school portal has one Family name box. The certified translation preserves both source fields; the applicant checks the school’s instructions before entering portal data.Decision table
Keep the complete box value and choose terminology consistently; do not invent a split.
Translate the printed label without claiming the person has only one legal surname.
Preserve each value and its ordinal position; do not replace the labels with parent-based terms.
Translate the relationship label because it is in the source; do not generalize it to ordinal fields elsewhere.
Use the field boundary, not spaces or particles, to determine the value.
Do not infer given-name or surname boundaries that the record does not label.
Never insert a value from another page or document into the blank source field; treat separately supported information as distinct and clearly labeled.
Ask the receiver how to enter multiple surnames; the translation provider cannot decide or guarantee acceptance.
Checklist
Document type, issuing country and issuing organization.
A complete readable image of every content-bearing page and side.
Exact labels: Apellido, Apellidos, Primer apellido, Segundo apellido or another term.
Visible field, column, line and punctuation boundaries.
Spaces, hyphens, particles and conjunctions inside each surname value.
Blank, dashed, crossed-out, handwritten or unclear fields.
Accents, ñ, capitalization and spelling in every occurrence.
Differences across pages, stamps, attachments and related records.
The actual receiver and any current written data-entry or translation instruction.
Service, certification, formatting, delivery and deadline needed for the quote.
Sources and workflow references
The current consolidated text says parents agree the order in which each parent’s first surname is transmitted when both lines of parentage are established. BOE identifies its consolidated text as informational; it is cited here only as a Spain-specific source. Translation takeaway (our inference): preserve the recorded labels and order instead of applying a universal father-first assumption.
Boletín Oficial del Estado
Open the current consolidated Article 49The Spanish Ministry of Justice Central Civil Registry data sheet for birth registration visibly separates Nombre, Primer apellido and Segundo apellido for the registered person and each parent. It is one concrete Spain-specific form, not a template for every Spanish-language record.
Ministry of Justice of Spain
Open the official surname-field formThe current profile for HM Passport Office operational staff describes Spain’s two-parent-surname convention, notes that parents can choose their order and identifies circumstances in which a single surname can appear. It supports reading the actual record instead of treating a common pattern as a universal parsing rule; it is not Spanish law or universal form-entry guidance.
HM Passport Office
Open the current Spain names guidanceThis companion guide owns spelling, accents, passport variants, initials and cross-document mismatches. The present post stays focused on what the surname labels mean and how their field relationships are preserved.
SpanishToEnglishTranslations.com name-handling guide
Open the name spelling and mismatch guideThis document-specific guide shows why labels, field relationships, names, identifiers and marginal notes must be read in the context of the issuing record. It is the country-and-document owner; this post remains the reusable surname-label explainer.
SpanishToEnglishTranslations.com document guide
Open the Mexican birth certificate field guideThe service page explains the managed Spanish-to-English path for source review, certification scope, formatting, delivery and corrections. A quote still needs the actual document, receiver, deadline and requested output; the service cannot guarantee recipient acceptance.
SpanishToEnglishTranslations.com service workflow
Review the certified translation serviceAuthor and reviewer
Reviewed for Spanish-to-English surname-label meaning, field-boundary preservation, compound-name handling, source-vs-form separation and narrow attribution of the cited Spain examples. The review does not determine legal identity, parentage, record correction, application data entry, authority requirements or recipient acceptance.
Blog FAQ
Apellidos usually means Surname(s) or Family name(s) on a personal-data document. Choose the English term that fits the document and requested variety, then preserve the complete value and field boundary. The plural label does not authorize a translator to invent separate fields if the source uses one box.
Primer apellido means First surname when it is an ordinal field label. Reproduce the value that appears in that field. Do not silently rename it Paternal surname unless the source itself uses a parent-based label or a documented project instruction requires separate explanatory treatment.
Segundo apellido means Second surname when that is the printed field. It describes the field’s position, not a universal statement about which parent supplied the value. Preserve a blank, dash or visible entry rather than completing the field from another record.
No universal assumption is safe. Spain’s current cited rule allows parents to agree the order of the first surname transmitted by each parent, and other countries and family circumstances can use different systems. Translate the actual labels and values on the record; use a current official country source only when a country-specific explanation is needed.
That is a receiving-form question, not a translation rule. A source-faithful translation preserves the original field structure. If an application offers only one Last name or Family name box, follow its current instructions or ask the responsible organization how it wants multiple surnames entered. A translation provider cannot decide the person’s legal identity or guarantee acceptance.
Not merely because it contains spaces, a particle or punctuation. Preserve the complete visible value within its labeled source field. If the scan or layout makes the boundary uncertain, request a clearer copy or use the approved uncertainty workflow instead of guessing from the words.
A translator should report the source accurately, flag the discrepancy and follow any documented presentation instruction that does not misrepresent the record. Correcting the issuing record, deciding legal identity or establishing that two versions belong to one person is outside translation scope and belongs to the relevant issuer or competent authority.