Translating Documents for USCIS: Requirements and a Faster Workflow
The rule itself is short. The mistakes people make around it — partial translations, missing seals, uncertified machine output — are what generate RFEs.
Every foreign-language document you submit to USCIS must be accompanied by a full English translation, and the translator must sign a certification stating that the translation is complete and accurate and that they are competent to translate from that language into English. That's the requirement in one sentence. Machine translation output on its own does not satisfy it — no one has signed anything — and neither does a partial or summarized translation, no matter how accurate. The practical question for most applicants isn't what the rule says; it's how to meet it without paying full human-translation rates for every page of a document set that might run to dozens of pages.
What the certification actually is
The certification is a short signed statement attached to the translation. In substance it says: I certify that I am competent to translate from [language] into English, and that this translation is complete and accurate. It includes the translator's name, signature, and date, and typically contact information. A few points that surprise people:
- The translator does not need to be "sworn," court-appointed, or accredited by any particular body for USCIS purposes — they need to be competent in both languages and willing to sign to that.
- In principle a bilingual friend or family member can translate and certify, though many applicants prefer a professional so competence isn't questioned; applicants generally should not certify translations of their own documents.
- Notarization is not required by USCIS for the translation certification itself.
- "Complete" is literal: everything on the page, including seals, stamps, marginal notes, and boilerplate — not just the fields that seem relevant.
Which documents typically need translating
Any document in a foreign language that supports your filing. In practice the common set is:
- Birth certificates — the single most requested document, needed for family-based petitions, adjustment of status, and naturalization.
- Marriage and divorce certificates, and death certificates where relevant.
- Academic records — diplomas and transcripts for employment-based petitions and some visa categories.
- Police clearance certificates and court or prison records.
- Financial and civil documents — bank records, property documents, household registries, military records, depending on the case.
Most of these arrive as scans or phone photos of stamped, sealed, table-heavy originals — which is exactly the format that's slowest to translate from scratch.
The workflow that's become standard
Professional translators rarely type a translation from zero anymore, and the efficient version of the workflow is available to applicants too:
- 1Produce a machine draft with the layout intact. Run the scanned document through a translator that preserves the page layout, so the draft English sits where the original text sat — same table cells, same certificate fields, seals still visible. A draft that mirrors the original page is dramatically faster to review than a wall of extracted text, because the reviewer can compare source and draft position by position.
- 2A qualified translator reviews and corrects. The human pass catches what machines get wrong on civil documents: name spellings (which must match your other filings exactly), transliteration choices, date formats, official titles, and the text under stamps and seals that OCR can't read reliably.
- 3The translator signs the certification. The certification attaches to the reviewed translation. What USCIS receives is a complete English rendering of the document plus the signed statement — the machine draft was scaffolding, and the signature is what makes it submissible.
This is where a layout-preserving tool earns its place, and it's the role Reglyph is built for: it reads the scan with OCR, erases the original text from the page image, and typesets the draft English translation back in position, so seals, tables, and certificate formatting stay where they were. The first 5 pages are free without a card, paid use starts at $5, and a bilingual side-by-side export puts original and draft on facing halves — a convenient format to hand a reviewing translator. To be explicit: Reglyph produces the draft and the layout. It is not a certified translation and doesn't claim to be — a human translator must review the draft and sign the certification before anything goes to USCIS.
Cost and time, in general terms
Certified translation services typically price per page for standard documents like certificates, with short documents turned around in a day or two and larger sets taking longer. Rush service usually costs more. Two levers actually move the total:
- Page count and density — a one-page birth certificate is the cheap case; a multi-page transcript or court record with dense tables costs more because review takes longer.
- How much work the reviewer starts with — a clean, laid-out draft to verify is a smaller job than translating a raw scan from zero, and services and independent translators generally reflect the difference in what they charge or how fast they deliver.
If a bilingual person you know will certify, the draft-then-review workflow reduces their job from hours of typing and formatting to a careful read-through — which is also the version of the favor people actually say yes to.
Mistakes that generate RFEs
A Request for Evidence adds months. The translation-related triggers are consistent and avoidable:
- Partial translations — translating only the "important" fields of a certificate, or summarizing ("this document is a birth certificate showing...") instead of translating. The requirement is a full translation.
- Untranslated seals, stamps, and marginal text — the registrar's stamp, the annotation in the margin, the boilerplate at the foot of the certificate all count as content on the page. A translation that skips them is incomplete.
- Missing or defective certification — a translation with no signed statement, or one missing the competence-and-accuracy language, doesn't meet the requirement regardless of quality.
- Illegible source copies — if the officer can't read the original scan, the translation can't be checked against it. Submit a clean, complete copy of the original alongside the translation.
- Inconsistent names and dates — a transliteration that doesn't match the spelling on the rest of your filing invites questions. Fix consistency at the review step, before signing.
This article describes the standing USCIS translation requirement and common practice. Requirements for specific forms and categories can differ in details, and an attorney or accredited representative is the right source for case-specific questions. When in doubt, check the instructions for your specific form.
The short version
Full English translation, every element on the page, plus a signed certification of completeness, accuracy, and competence. Machine translation gets you a fast, correctly laid-out draft; a human translator's review and signature make it submissible. Skip neither half: an uncertified machine translation and an expensive-but-partial human translation fail the same requirement from opposite directions.
Translate your scanned document now
Upload a scanned PDF or a photo — Reglyph OCRs it, translates it, and rebuilds the page so tables, stamps, and figures stay exactly where they were.
Translate 5 pages freeFrequently asked
Does USCIS accept machine translation?
Not on its own. USCIS requires a full English translation accompanied by a translator's signed certification of completeness, accuracy, and competence. A machine draft becomes submissible only after a qualified human reviews it and signs that certification.
Who can certify a translation for USCIS?
Anyone competent in both languages who signs the certification — no specific accreditation or notarization is required by USCIS. Many applicants use a professional translator so competence isn't questioned, and applicants generally shouldn't certify their own documents.
Do stamps and seals need to be translated?
Yes. "Complete" means everything on the page — seals, stamps, marginal notes, and footer boilerplate included. Untranslated seals are one of the most common translation-related reasons for an RFE.
How long does a certified translation take?
Short standard documents like a birth certificate are commonly turned around in a day or two; larger or denser document sets take longer. Starting the reviewer from a laid-out machine draft rather than a raw scan generally shortens the job.
Reglyph