How do you translate multiple WhatsApp exports as one I-130 marriage-evidence packet?
TL;DRA client submitted four WhatsApp chat exports from Haitian Creole into English for an I-130 marriage filing. Each export covered a different facet of the relationship: recent-month communication, prior-year continuity, extended-family integration, and financial support. We translated all four with identical structural conventions for voice messages, reply threads, and mixed-language lines. The same Translator’s Note was repeated on every packet.
Case Specifications
- Document
- Personal correspondence — multi-export WhatsApp chat bundle (4 separate PDF exports)
- Foreign Name
- Konvèsasyon WhatsApp ant mari ak madanm — kat eksportasyon separe (Multi-export WhatsApp conversation bundle)
- Country
- Haiti
- Languages
- Haitian Creole, English (code-switching), French (code-switching) → English
- Submitted To
- USCIS (I-130 family petition, bona fide marriage evidence)
What We Received
A client preparing an I-130 marriage-based petition submitted four separate WhatsApp PDF exports for [certified relationship-evidence translation](/documents/relationship-evidence). All four were chats from the applicant's WhatsApp history. Each covered a different period or contact pairing.
The first export was recent-month chats with the spouse (early 2026). The second was older chats with the same spouse from the prior summer. The third was a chat thread with the spouse's cousin. The fourth was a focused thread between the spouses on financial support. Primary chat language was Haitian Creole, with English and French code-switching woven through the messages. The translation was needed for an [I-130 family-petition filing](/immigration/family-petition).
Why This Required Special Handling
USCIS adjudicators look at chat-message evidence for two things. First: is the communication pattern consistent with a bona fide marriage? Second: is the evidence structurally trustworthy — properly translated, dated, and showing real chat-app metadata rather than a hand-edited transcript? A bundle of four separate translations done in four different styles fails the second test even when the underlying chats are real.
The four WhatsApp exports also contained more than message text. Each export had voice-message markers, reply-thread indicators, system-event lines, screenshot navigation counters, per-message timestamps, and day-of-week tags. Some messages were Haitian Creole with English words mid-sentence. Others were mostly English with a single Kreyòl phrase. The chat with the cousin used French in places where the spouse's chat used English. A translation that collapses these structural elements or smooths the mixed-language passages loses the evidentiary value the bundle was built to provide.
USCIS publishes general guidance on what counts as bona fide marriage evidence in the [I-130 petition workflow](/immigration/green-card). The guidance recognizes chats and correspondence as supporting evidence, but the translation has to preserve the original record — not paraphrase it.
How We Handled It
We treated the four exports as one ordered packet. The same speaker-label convention was used across all four PDFs: the applicant as [You], the petitioner-spouse as [Hubby ❤], the cousin as a separate labeled contact, and [System] for app-generated events. The labels were applied identically on every packet so a reader does not have to relearn the convention between exports.
Voice messages were rendered as [Voice message, 0:23] — preserving the duration without paraphrasing audio we could not access. Reply-thread indicators kept the chat-app's '↪ Replying to [Speaker]: [quoted excerpt]' structure rather than being flattened into prose. System events appeared on their own indented line, marked [System]. Screenshot metadata — including the back-navigation counter visible at the top of each screenshot — was preserved with a brief in-line note so an adjudicator can see which screenshot a given block belongs to.
Mixed-language messages were translated with the original Kreyòl or French phrase first, followed by an English gloss in square brackets — "Bjr chéri ! [Good morning, darling!]". Messages that were already in English passed through verbatim. The intent was to keep the source visible so an adjudicator can confirm what was actually written, while still making every line readable in English.
The same Translator's Note was placed at the foot of all four packets, explaining the language mix, the voice-message convention, the speaker labels, and the reply-thread rendering. Each packet carried the same order number on the footer. The four PDFs were then bound and delivered as a single submission.
"This certified translation is one of four separate WhatsApp chat exports translated for the holder's I-130 marriage-based petition. The source language is Haitian Creole with English and French code-switching. Mixed-language messages are reproduced with the original Kreyòl or French phrase followed by an English gloss in square brackets. Voice messages are marked [Voice message, mm:ss] without audio transcription, as the source PDF preserves only the message header. Reply-thread indicators ('↪ Replying to ...') and system events ('[System]') are preserved on their own lines. Per-message timestamps, day-of-week tags, and screenshot back-navigation counters are reproduced from the source. The four packets in this bundle use identical structural conventions and the same speaker labels throughout."
The Outcome
The four-PDF bundle was delivered as a single I-130 evidence submission. Each packet carried the same order number on the footer so the four documents are recognizable as one delivery. The client's attorney included the bundle in the petition packet.
We have used the same multi-export approach on every WhatsApp-based bona fide marriage evidence job since 2024. The rule is simple. When the client curates more than one chat, every chat must use the same structural conventions. That means the same speaker labels, the same voice-message and reply-thread markers, and the same Translator's Note text at the foot.
What This Means for You
If your I-130 filing depends on chat-message evidence, you generally need more than one export. Recent communication shows ongoing contact. Older chats show continuity. Extended-family chats show integration. Financial threads show co-mingling. All of those exports should be translated as one consistent bundle, not as four independent jobs. The same speaker labels, voice-message markers, and Translator's Note should appear on every packet. See our [certified relationship-evidence translation](/documents/relationship-evidence) and our [I-130 translation requirements](/uscis-forms/i-130) for related work.
Have a similar situation?
We translate WhatsApp, iMessage, Facebook Messenger, and SMS chat exports for I-130, I-485, K-1 (fiancé), and I-751 (removal of conditions) filings. Multi-export bundles handled as one consistent packet, speaker labels and voice-message markers preserved, mixed-language messages glossed in brackets, and a Translator’s Note repeated on every PDF. $24.95/page, delivered in 24 hours.
Related Cases & Resources
Sources & References
- USCIS — Petition for Alien Relative (I-130)·U.S. Citizenship and Immigration Services·Verified 2026-05-23
Explore the Hub
Documents
Immigration
All identifying information has been removed from this case study. The applicant's name, the spouse's name, the cousin's name, phone numbers, contact-list metadata, and the original chat screenshots are not displayed. Case details are shared with client permission.