💡 French-to-Vietnamese localization is a strategic market decision before it is a technical one. Vietnam has 78 million internet users who expect content in Vietnamese. The essentials: UTF-8 encoding, hreflang=vi, and a staged workflow - basic UI first, marketing copy last. The linguistic distance is predictable: six tones, no plural forms, and strings that run 25-35% shorter than French.
Key takeaways
- Stage 0 (day one): configure UTF-8 end-to-end and add
hreflang="vi"to your pages - no linguist needed, blocks ranking damage from day one. - Stage 1 (MVP): translate core UI strings and error messages with MT plus native post-editing - most B2B teams can launch a usable Vietnamese version in 2-4 weeks.
- Stage 2 (conversion): localize marketing copy, landing pages, and onboarding with a native Vietnamese specialist - this is where conversion lifts happen.
- Vietnamese has no plural forms (Unicode CLDR: "other" category only), no grammatical gender, and no verb conjugation - string templates often simplify rather than complicate.
- Sino-Vietnamese vocabulary covers roughly 60% of Vietnamese; technical and financial terms often have natural equivalents, but register still requires a native reviewer.
Vietnam's digital market: why French companies are moving in now
Vietnam has 78.44 million internet users, a 79.1% penetration rate, and 72.7 million active social media users (DataReportal 2024). The median age is 33. The EU-Vietnam Free Trade Agreement (EVFTA), in force since August 2020, reduced tariffs and opened government procurement to European companies. French brands - retail, hospitality, finance - already operate in Vietnam. Localization is their bridge from French corporate headquarters to Vietnamese end users, not an optional upgrade.
Vietnam is also mobile-first: 168.5 million cellular connections for 99 million people, and 92.7% of internet users access at least one social platform every day. TikTok has 67.72 million users, YouTube 63 million, Facebook 72.7 million. A French-language interface is not a neutral default - it is a barrier that depresses adoption, sign-up, and trust.
What makes Vietnamese harder to localize than it looks for French teams?
Both languages use Latin script, so French teams assume the gap is small. It is not. Vietnamese is tonal (six lexical tones marked as diacritics), isolating (no inflections at all), and monosyllabic. A wrong diacritic is not a typo - it produces a different word. No spell-checker catches tonal errors. Machine translation makes tonal errors silently, especially in domain-specific vocabulary.
The technical essentials apply before anything else: declare UTF-8 on every page (the W3C standard for all web content) and add hreflang="vi" in your HTML head so Google links the Vietnamese version to Vietnamese search queries. Vietnamese characters require the Unicode Latin Extended Additional block (U+1E00-U+1EFF), beyond the range French needs. Any pipeline carrying ISO 8859-1 encoding will silently corrupt Vietnamese text without warning.
String length changes direction: French is 15-20% longer than English; Vietnamese is 10-15% shorter. French-to-Vietnamese moves strings 25-35% shorter on average. Buttons and containers designed for French will have extra whitespace in Vietnamese. Some compound noun phrases expand (Vietnamese needs an explicit classifier or auxiliary verb), but the net effect on UI layouts is shortening, not overflow.
What do French companies typically underestimate about Vietnamese?
The most common mistake is treating Vietnamese localization as pure word-for-word translation. It involves three layers translation alone does not cover: register, terminology strategy, and social proof.
Register: Vietnamese has a pronoun system tied to social relationships. The word for "I" shifts with the relationship: tôi (neutral-formal), em (junior), mình (informal). For B2B software, the standard convention is first person tôi and second person bạn. Write this into a Vietnamese style guide before the first string is translated.
Terminology: Sino-Vietnamese vocabulary (from classical Chinese borrowings) accounts for about 60% of Vietnamese vocabulary, including most technical and financial terms. Teams entering from French have no Sino-Vietnamese intuition. For fintech, medical, or legal content, a glossary session with a native specialist early in the project saves months of inconsistent output.
Social proof: Vietnamese B2B buyers are strongly community-driven. Vietnamese-language case studies and testimonials convert significantly better than translated French ones. Plan one round of Vietnam-specific evidence for the product launch.
How should you stage Vietnamese localization for a French B2B product?
Staging localization avoids both extremes - waiting for a 100% translated product before launch, and translating everything at once only to have it go stale. A four-stage model for a French B2B SaaS or e-commerce product entering Vietnam:
- Stage 0 - Technical foundation: UTF-8,
hreflang="vi", vi-prefixed URL path (/vi/), locale registration in your i18n library. Pure engineering. Do this in the first sprint. - Stage 1 - Minimum viable localization: translate 2,000-5,000 core UI strings and error messages using MT with native post-editing. Target: a Vietnamese user can navigate and troubleshoot without English. Timeline: 2-4 weeks.
- Stage 2 - Conversion-ready localization: landing pages, pricing page, onboarding flow, support documentation. These need a native Vietnamese specialist - Vietnamese marketing copy that converts uses idioms and register that MT consistently misses. Timeline: 4-6 weeks post-launch.
- Stage 3 - Vietnam-native presence: Vietnam-specific case studies, local event content, and social media voice. Timeline: 3-6 months after Stage 2.
At Stage 1, engage a Vietnamese website localization specialist for a glossary and style guide session before the first string is translated. That 3-4 hour investment prevents months of inconsistent terminology across all subsequent stages.
Which terminology register works for Vietnamese professionals: Sino-Vietnamese or plain Vietnamese?
For professional B2B contexts - finance, legal, medical, software - Sino-Vietnamese is the professional register. Pure-Vietnamese alternatives often exist but sound informal or even condescending in a business context. Examples: "phần mềm" (software), "bảo mật" (security), "tài khoản" (account), "hợp đồng" (contract) are all Sino-Vietnamese and are the only professional terms. For a French fintech or SaaS team, defaulting to Sino-Vietnamese professional vocabulary and having a native specialist validate key terms is the most cost-effective approach.
For consumer-facing products targeting a younger urban Vietnamese audience (social commerce, gaming, lifestyle apps), pure-Vietnamese or hybrid registers are more natural. Identify your target segment before setting terminology guidelines in your style guide.
When does investing in professional Vietnamese translation pay off?
French teams can confidently handle the technical foundation in-house: UTF-8, hreflang, URL structure, and i18n library setup are engineering tasks. MT with post-editing is viable for Stages 0-1: UI strings, error messages, and FAQ content.
The return on professional Vietnamese translation investment is highest in three areas: (1) marketing and onboarding copy, where tone and cultural register determine whether Vietnamese users trust and adopt the product; (2) legal and compliance documents, where Vietnamese regulatory terminology is specific; (3) the initial glossary and style guide session, which is a one-time investment that makes all subsequent MT+MTPE work consistent and faster.
Vietnam's B2B buyers are sophisticated. A Vietnamese product that feels translated rather than localized - correct words in the wrong register, missing social proof, pronouns that feel off - signals that the vendor does not understand the market. That signal is expensive to reverse after launch.
FAQ
What hreflang tag should I use: vi or vi-VN?
Use hreflang="vi" for a single Vietnamese version targeting all Vietnamese readers globally. Add hreflang="vi-VN" only if you have a distinct version for Vietnam-resident users that differs from an overseas Vietnamese version. For most B2B products, vi is correct and simpler to maintain.
How long does a French-to-Vietnamese B2B SaaS localization project take?
Stage 1 (MVP, 2,000-5,000 strings with MT+MTPE including glossary setup): 2-4 weeks. Stage 2 (marketing and onboarding copy, human translation): 4-6 weeks depending on volume. Total from decision to launch-ready: 6-10 weeks for a mid-size product. The bottleneck is usually internal engineering setup and review cycles, not translation speed.
Should I use DeepL or Google Translate for French-to-Vietnamese?
Both support FR-to-VI and are suitable for Stage 1 UI strings and FAQ content. DeepL tends to produce grammatically cleaner output on this language pair. Neither is production-ready without native post-editing for marketing copy, legal content, or anything customer-facing with brand implications.
Do Vietnamese B2B buyers prefer English or Vietnamese interfaces?
LinkedIn Vietnam has 7.5 million members (DataReportal 2024), so educated professionals are comfortable in English. However, for broader adoption beyond internationally-focused firms, Vietnamese interfaces significantly outperform English-only. For SMB and enterprise sales outside Ho Chi Minh City and Hanoi, Vietnamese localization is essentially required.
What is the minimum Vietnamese localization to launch with?
Minimum viable: UTF-8 configured, hreflang="vi" live, and core UI and error strings translated (Stage 1 above). This prevents Google from treating the Vietnamese version as duplicate content and gives Vietnamese users a navigable experience. Everything else can follow in stages. Do not delay launch waiting for 100% translated content.
Official Sources
- DataReportal - Digital 2024: Vietnam - Internet users (78.44M), mobile connections, social media platform data, population demographics. Verified November 2026.
- Google Search Central - Managing multi-regional and multilingual sites - hreflang implementation, URL structure for multilingual sites. Verified November 2026.
- W3C Internationalization - UTF-8, UTF-16, UTF-32 and BOM - UTF-8 without BOM recommendation for multilingual HTML including Vietnamese. Verified November 2026.
- Unicode CLDR - Plural Rules - Vietnamese plural category: "other" only, no inflected plural forms. Verified November 2026.
Written by Dao Huy (Lucas), Vietnamese translator and localization specialist (English, Chinese and French into Vietnamese). See translation services →