Translation Questions, Answered in Full

The elements required by law are the translator's identifying data: the decree-law obliges the registered translator to associate their registration number and the translation house name with documents they produce, and omitting the name or number is now a fineable violation. Beyond that, requirements are set by the recipient. The DIFC Courts give the clearest published example: a certified translation accompanying a claim form served onshore must carry the translator's statement that it is a correct translation, plus the translator's name, address and qualifications. The familiar package — translation bound to a copy of the source, stamped on each page, with a signed accuracy declaration — is well-established professional practice that receiving officers expect, though no UAE instrument we can cite prescribes that exact presentation.

In sound professional practice, nothing on the page is silently dropped: stamps, seals, letterheads, footers, marginal notes and the reverse side are all rendered or described. A seal in a third language needs translating like any other text. Where an element genuinely cannot be read — a faded circular stamp, an illegible signature — the honest convention is to describe it as illegible rather than guess, because an invented name is far worse than a transparent note. Signatures are described, never reproduced as images, so the translation cannot be mistaken for an original.

No UAE authority we can cite publishes a layout-replication rule, so treat this as professional practice, not law. That said, the practice exists for a practical reason: a receiving officer checks the translation against the source, and when tables sit where tables were, and page breaks correspond, verification takes moments instead of minutes. A translation delivered as an unstructured wall of text is technically a translation; it is also an invitation for the counter to slow down. We mirror structure because it serves the person whose approval you are waiting for.

Exactly as it appears on your existing official documents — and this is worth a moment of your attention before work starts. Transliteration between Arabic and Latin script has no single correct answer: the same Arabic name can be romanised several defensible ways. What matters to authorities is consistency: the translation must match the passport, Emirates ID and trade licence spellings already on file, because a single divergent letter is among the most common causes of counter-level rejection. Send us those reference spellings with the document; where your own documents disagree with each other, we flag it before certifying rather than choosing silently.

For a quotation, usually yes. For the certified work itself, quality matters more than convenience: a photo that crops the edge of a stamp, blurs a security feature or cuts the QR code creates problems that surface at the worst moment — the submission counter. A flat scan at adequate resolution is the safe standard. Where the original genuinely cannot be improved — an old certificate, a faded seal — we translate what is legible, describe what is not, and tell you before submission that the receiving authority may query it. What we will not do is guess at unreadable content to make a document look cleaner than it is.

Because a legal document mixing Arabic and English is genuinely bidirectional text, and display order is governed by a formal standard — the Unicode Bidirectional Algorithm — not by the typist's eye. Arabic runs right to left while digits and Latin words run left to right, and characters like brackets and hyphens are directionally ambiguous. Passport numbers, IBANs, case references and dates are exactly the fragments that flip or reorder when this is mishandled — and in a legal filing, a reversed case number is a substantive error, not a cosmetic one. Competent Arabic typesetting uses the standard's directional controls so every mixed fragment reads correctly in both languages.

The default rule is no. Arabic is the language of the courts under the Civil Procedure Law, and the UAE Government portal states that documents presented to the courts must be in Arabic or translated by a legal translator approved by the Ministry of Justice. There is a narrow exception: since early two thousand twenty-three the law allows proceedings to run in English in specified cases, but only by a specific decision of the President of the Federal Judicial Council or the head of the relevant local judiciary — it is not something a party can simply request. Unless such a decision exists in your case, plan for certified Arabic translation of every foreign-language exhibit. In criminal matters the Criminal Procedures Law likewise requires proceedings in Arabic, with interpreters provided where a party does not speak it.

Partly, and only there. Circular No. (8) of 2023 of the Abu Dhabi Judicial Council exempts bank statements and invoices containing solely numerical data from the mandatory Arabic-translation requirement, on the reasoning that figures explain themselves. Two limits matter. First, where English narrative text accompanies the numbers and could affect comprehension, the court keeps discretion to require a translation anyway. Second, this is an Abu Dhabi measure; we know of no published equivalent in Dubai or the other emirates, so do not assume it travels. For heavy financial exhibits outside Abu Dhabi, budget for translation until the receiving court says otherwise.

Inside those jurisdictions, English rules: the DIFC Courts conduct all proceedings in English and require all filed documents in English, and the ADGM Courts state the same. But Arabic returns the moment a matter touches the rest of the UAE. A DIFC claim form served onshore must be accompanied by a certified Arabic translation with the translator's statement, name, address and qualifications attached. A DIFC judgment to be served or enforced outside the centre needs Arabic. And even inside ADGM, the Notary Public requires documents in dual-language Arabic and English within the same document, with the translation certified by a licensed legal translator. The free zones are English islands, but the boundary crossings are frequent and each one is an Arabic-translation event.

Three translation-related things, in sequence. First, Dubai Law No. (12) of 2004 requires the judgment to be translated into Arabic where enforcement is outside the DIFC. Second, the DIFC Courts' own rules add a deadline: where a judgment or order is to be served outside the DIFC within the UAE, the parties must agree and lodge an Arabic translation with the courts within two days of it being handed down — failing which the court may accept one party's version or even suspend or revoke the order. Third, the judgment goes to the execution judge of the Dubai Courts, who enforces without reviewing the merits. One drafting comfort: where the Arabic and English versions conflict, the rules provide that the English prevails. The practical lesson is to arrange translation before judgment, not after.

This is one of the genuinely unsettled questions, and we would rather say so than invent an answer. The statutory rule addresses documents issued in a foreign language; no official source we could locate addresses a bilingual original where Arabic is already one of the two texts. In principle the Arabic text should be usable as filed, and many bilingual contracts state which language prevails. In practice, courts and case-management offices differ in what they ask for. Our honest guidance: raise it with the case-management office or your counsel before filing, and if certified translation of any part is requested, the request will define its scope. Treat any provider who gives you a categorical answer to this question with caution.

The inbound chain in reverse. The UAE issuing authority attests first — unless the document is a digital government document or already electronically attested, which MOFA exempts — then MOFA attests it for international use, then the destination country's embassy or consulate in the UAE legalises it. The Spanish Embassy in Abu Dhabi, for example, states plainly that it legalises UAE documents only after UAE MOFA has done so. After the stamps, the destination country applies its own translation requirements in its own language, under its own rules — which brings us to the next question.

Yes, and they differ materially — never generalise one country's rule to another. Two published examples make the point. The UK Home Office requires a certified translation of supporting documents to carry confirmation of accuracy, the date, the translator's full name and signature, and their contact details. Canadian immigration requires supporting documents in English or French, and where they are not, the applicant must supply the translation together with an affidavit from the translator and a certified photocopy of the original — a three-part deliverable in which a bare translation is not accepted. When a document leaves the UAE, we prepare the certification block to the destination's published specification, not to a generic template.

We cannot point to an official UAE page that settles this, so here is the honest picture. The rules that do exist pull the other way: courts require translation by a legal translator approved by the Ministry of Justice, and the regulated profession is built around translators registered and working inside the UAE. MOFA's attestation requirements speak of a legally certified translation without defining whose certification qualifies. In practice, receiving authorities in the UAE commonly expect the Arabic version to carry a UAE-registered translator's stamp, and a foreign sworn translation — however valid at home — often ends up retranslated or re-certified here. Before paying twice, ask the specific receiving authority in writing whether your foreign certification is acceptable; if the answer is unclear, a UAE legal translation is the safe route.

In the country that issued it — a public document is authenticated where it was created, because only that country's authorities can verify the seals on it. The UAE Embassy in London illustrates the rule at its sharpest: it states it will not legalise academic certificates that are not British, Irish or Icelandic, so an Indian degree held by a UK resident must go through the chain in India, not London. For non-academic documents some missions offer longer third-country routes, but procedures are mission-specific and published per mission. Plan the attestation geography before you plan the translation, and read the exact UAE mission's page for the country of issue.

Yes, on two fronts. The UAE Government portal states that foreign court decisions intended for enforcement in the UAE require attestation from the Ministry of Foreign Affairs before implementation — so the judgment must complete the legalisation chain like any other foreign public document. And because enforcement proceedings run in Arabic before mainland courts, the judgment and its supporting documents need certified Arabic translation by a registered legal translator. The two requirements are separate and cumulative: attestation authenticates the foreign court's seals, translation makes the content usable in Arabic proceedings. Neither substitutes for the other.

Only the people working on your matter — assignment is need-to-know, which for a typical certified job means the translator and the second linguist who checks the work. Confidentiality is not only our policy: the decree-law places a statutory confidentiality duty on registered translators personally, and the current penalty schedule makes disclosure of confidential information one of the most heavily fined violations. For sensitive sets — family matters, medical records, shareholder disputes — tell us at intake and we restrict handling further and agree written confidentiality terms before any file moves.

Confidential client documents are not pasted into public machine-translation or free AI tools — once text enters such a service you no longer control where it is stored or reused, which is incompatible with legal-document confidentiality and with the UAE Personal Data Protection Law's expectations of anyone processing personal data. The professional tools we do use — translation memories, terminology databases — are consistency instruments under our control, and which tools touch a matter is something we will state plainly if you ask. The translation and its revision remain human work by named linguists.

Yes. For corporate and law-firm clients this is not a favour but the correct legal shape of the relationship: under the UAE Personal Data Protection Law, a client sending personal data for translation is a controller engaging a processor, and the law contemplates written terms setting out the scope, duration, nature and purpose of the processing with security obligations attached. We work under your template or ours, and we put our retention and deletion position in writing as part of it, so the file's afterlife is agreed before the work starts.

First we establish why, because the remedy depends on the cause. If the fault is ours — a name mismatch, an omitted stamp, a certification block missing an element the authority requires — we correct and re-certify it as our responsibility. If the cause sits outside the translation — an incomplete attestation chain, an underlying document past the authority's freshness window, a requirement the authority applies that was not disclosed to us — we tell you exactly what is missing and what order fixes it. What you will not get is a shrug: every rejection has a stated or discoverable reason, and identifying it is part of the service, not an extra.