DIY guide · The manual method
How to make a certified translation in a word processor — every step, honestly
Yes, you can do this with free software and an evening. Here's the real procedure, including the parts most how-tos skip — because those are the parts that go wrong.
The short answer
The by-hand method: (1) transcribe every element of the original, (2) translate all of it — fields, seals, stamps, annotations, (3) rebuild it as a clean, labeled English document, (4) add a certification page whose wording tracks 8 CFR § 103.2(b)(3), (5) have a competent bilingual person review and sign it, (6) file it with a copy of the original.
Plan for 45 minutes to a few hours per document depending on density, and be strict about completeness — the typical self-prepared translation fails on skipped seals and marginal notes, not on vocabulary.
The six steps
1. Transcribe before you translate
Work from a good scan at 100%+ zoom and type out the original language first — every field label, every value, every stamp caption, every marginal note. Transcribing first forces you to actually look at each element; translating on the fly is how seals get skipped.
2. Translate everything, in place
Translate each transcribed element, keeping the document's structure. Names stay spelled as the source document spells them (match the passport where both exist). Dates convert to an unambiguous format. Registry numbers, codes, and identifiers copy through exactly.
3. Handle seals, stamps, and handwriting explicitly
Convention: describe and translate each in square brackets where it appears — "[Round seal: Civil Registry, State of ——]", "[Rubber stamp: CERTIFIED COPY]", "[Handwritten: entry corrected per resolution 14/2011]". If you truly can't read something, write "[illegible]" — never guess. An invented word in a legal filing is a much bigger problem than an honest gap.
4. Rebuild a reviewer-friendly layout
You're not forging a lookalike — you're producing a clear English rendering an officer can compare against the original. Use labeled lines ("Field: value"), keep the reading order of the original, and add a heading identifying the document.
5. Write the certification page
One page, at the end: a statement that the signer is competent to translate from the source language into English and that the translation is complete and accurate; then signature, printed name, date, and contact details. Track the regulation's own concepts — competence, completeness, accuracy. Don't copy a random forum template with notary blocks and case numbers it doesn't need.
6. Review, sign, and assemble
Your bilingual signer reads the translation against the original — actually reads it — then signs. File translation + certification + a copy of the original together, per your form's instructions.
The five mistakes that sink self-prepared translations
- Skipping the "boring" elements — seals, stamps, registry numbers, and marginal notes are the most-skipped and most-checked items.
- Guessing at illegible text. Mark it illegible; guessed names and dates create contradictions with your other evidence.
- Summarizing instead of translating. "States that the applicant was born on…" is a summary; the requirement is a full translation.
- Certification wording that promises the wrong thing — notarial language, "sworn before me", or copied templates naming another country's rules.
- Name and date drift — the translation spelling a name differently than the passport, or converting a date wrong, invites a mismatch query on the whole filing.
Where the engine fits (and where it doesn't)
Steps 1–4 are mechanical diligence — exactly what software does without fatigue. Our engine reads the full document, translates every field and marking, flags illegible text, and outputs the formatted translation plus the certification page as a fillable PDF: $11.99 per page, ready in 2 hours or less.
Steps 5–6 stay human, and should: a competent person reviews and signs. If you enjoy the by-hand method and your document is simple, it genuinely works — this page is the honest version of how. The engine is for when you'd rather spend 5 minutes than an evening, at a price that's still a rounding error next to agency fees.
By-hand method questions
Is a translation I make in Word actually valid for USCIS?
The regulation cares about completeness, accuracy, and a signed certification by a competent person — not about what software produced the document. A careful by-hand translation with a proper certification meets the same standard as anything a company produces.
Do I need special certification wording?
There's no single mandated sentence. The certification should state the signer's competence to translate from the source language into English and that the translation is complete and accurate, and carry signature, name, date, and contact details. Keep it aligned with 8 CFR § 103.2(b)(3) and skip notarial language that doesn't apply.
Should the translation look identical to the original?
No — it should be clearly organized so a reviewer can match it to the original. A labeled, structured English rendering reads better than a strained visual imitation, and it's what survives review in practice.
How long does the by-hand method take?
A simple one-page certificate: roughly 45–90 minutes done carefully. Dense documents with tables, stamps, and annotations can take several hours. The engine's job is to compress exactly that time.
Can I use machine translation as a starting point?
As a drafting aid, with a genuinely bilingual reviewer, it can be — the certification is only honest if the signer verified the result. Raw machine output signed unread is a false attestation and tends to fail on exactly the structural elements (seals, annotations, layout) generic tools ignore.
Or skip to the review-and-sign part.
Upload the document; the engine does steps 1–4 and hands your signer a clean package. $11.99 per page.
Upload My Document →Sources
Compiled from the official resources below. Requirements change — the receiving authority's current instructions always control.
Last reviewed 2026-08-24 · DIY Certified Translations editorial team