Arabic to English Certified Translation: Names Matter

If you have ever hesitated over whether to write Mohamed, Mohammed, or Muhammad on a US form, you already understand the central problem with Arabic documents. Nothing is wrong with your birth certificate. Nothing is wrong with your passport. They simply disagree, because each was romanized by a different person, in a different country, at a different time, with no shared rulebook. Then an immigration officer or an admissions reviewer lines them up and sees two names that do not match. Most Arabic translation problems that reach a US agency are not translation errors at all — they are transliteration mismatches, and they are preventable before the file is submitted.

Why one Arabic name produces six English spellings

Arabic script writes consonants and long vowels. Short vowels are marked with diacritics (حركات) that almost never appear in printed civil documents, so anyone converting a name to the Latin alphabet has to supply the missing vowels themselves.

Several other features multiply the possibilities:

• The definite article (ال) attaches to many family names and can be written Al-, El-, or dropped. Abdel Rahman, Abd al-Rahman, and Abdulrahman are the same name.
• Emphatic and guttural consonants have no English equivalent. The letter (ق) becomes q, k, g, or an apostrophe depending on dialect and convention.
• The feminine ending (ة) appears as -a, -ah, or -at inside a compound.
• Regional pronunciation. Egyptian records often render the letter (ج) as g — Gamal rather than Jamal — while Levantine and Gulf records use j.
• French colonial spelling. Documents from Morocco, Algeria, Tunisia, and Lebanon often use French orthography: Chérif rather than Sharif, ou for the w sound.

None of these variants is wrong. All are defensible. That is exactly why they cause trouble: there is no authority a reviewer can consult to decide which one is correct.

A reviewing officer is not evaluating your transliteration scholarship. They are checking whether the name on this page is the same person as the name on that page.

The rule that governs the translation itself

For USCIS, the requirement lives in 8 CFR 103.2(b)(3): a document in a foreign language must be filed with a full English translation, and the translator must certify that the translation is complete and accurate and that they are competent to translate from Arabic into English.

That is the entire rule. It does not require a government-licensed translator, an accreditation, a notary, an embassy stamp, or an apostille. Those requirements exist in other countries and are often attached to Arabic documents by consulates abroad, which is why so many people assume USCIS wants the same thing. Our overview of USCIS certified translation covers the certification language in detail.

What the rule does imply is that the translation must be faithful — which raises the question of what faithfulness means when the source gives you six legitimate options.

How a translator should actually handle your name

The working principle is simple: the translation should use the spelling that appears on your primary government identification, normally your passport, and should not invent a competing one.

A translator who romanizes your name from scratch using an academic standard is being technically rigorous and practically unhelpful. If your passport says Khaled Abdelaziz and the translated birth certificate says Khālid 'Abd al-'Azīz, you have handed the reviewer a discrepancy to resolve. The correct approach:

1. Tell the translator the passport spelling before work begins — yours, your spouse's, your parents', anyone named in the document.
2. The translator uses that spelling throughout the translated document.
3. Where the Arabic original already carries a different printed romanization, the translator adds a bracketed translator's note rather than hiding one version.
4. Names that appear on no US document — a grandparent, a witness, a registrar — are transliterated using one convention, applied identically across every page.

That fourth point matters more than it sounds. If your father's name is Hassan on page one and Hasan on page three of the same file, that looks like carelessness even though both spellings are correct. When you order, the order details step is where to put your passport spellings so the translator has them from the start.

What a translator must never do

There is a line between matching a spelling and altering content. A translator may align the romanization of a name with your identification. A translator may not:

• Change a date of birth because the Hijri and Gregorian calendars produced different values on different documents.
• Change a place of birth because the town was renamed or spelled differently on a visa application.
• Drop a paternal or grandpaternal name because US forms have three fields and the document has five.
• Add a surname that does not exist on the original.

Many Arabic documents record a name as a chain — given name, father's name, grandfather's name, family name. The translation must show the full chain as it appears. How you distribute those elements across "First," "Middle," and "Last" is a question for your form, not for your translator, and your passport is again the safest guide.

If the underlying facts genuinely conflict, the remedy is an explanation — a cover letter, an affidavit, a corrected civil record — not a translation that quietly papers over the difference. A translation that does not match its original is no longer complete and accurate, which is a far worse problem than a spelling variant.

Dates, places, and the other Arabic-specific traps

• Two calendars. Documents from Saudi Arabia and some other states carry Hijri dates (هجري); others carry both. The translation should show what the document shows and label each calendar rather than converting silently.
• Eastern Arabic numerals. Many documents use the numeral set ٠١٢٣٤٥٦٧٨٩. These must be rendered as Western digits, and a misread digit in a date of birth is a serious error.
• Right-to-left layout. Columns and headers sit opposite to where an English reader expects, so a mirrored layout can attach a value to the wrong field.
• Place names with established English forms. Aleppo, not Halab. Cairo, not Al-Qahira. For smaller towns, transliterate consistently and consider a bracketed note with the governorate.
• Seals and signatures. Every stamp must be accounted for — [Round seal: Ministry of Interior, Civil Status Department], [Signature], [Illegible]. Omitting a seal makes the translation incomplete.

These issues cluster on exactly the documents where identity is the point: birth certificates, marriage contracts (عقد الزواج) that name both spouses plus fathers and witnesses, police clearance certificates that often carry their own printed romanization, and diplomas issued under a years-old student record.

What you should check when the translation arrives

Five checks catch nearly everything:

1. Your name, letter for letter, against your passport.
2. Every other person's name, spelled the same way on every page.
3. Dates — digits in the right order, calendar labeled, no silent conversion.
4. Seals and signatures described in brackets, with nothing left unaccounted for.
5. The Certificate of Translation Accuracy attached, signed, naming Arabic as the source language.

At eVerbary, certified translation is $24.95 per page, where a page is up to 250 words including numbers, and revisions are included — so if the passport spelling was not communicated up front, correcting it is not a new order. Most one- to three-page documents come back within 24 hours, and Arabic to English translation is handled by human translators rather than machine output that would romanize your name differently on every page.

Frequently asked questions