The Unfortunate Truth About Translating "Hello"
Most people treat multilingual greetings as a trivial exercise, and for casual purposes they're close enough. I say close enough because the gap between textbook accuracy and what actually happens when you open your mouth is where most mistakes live. I spent years dealing with international support escalations that literally started with a greeting misunderstanding, and the root cause was rarely the word itself. It was the context around it. The straightforward answer depends on which languages you're targeting, but here's what you actually need to know before you commit anything to a script or a translation glossary. "Hello" isn't a single concept. It's a family of concepts that split along lines of formality, time of day, geographic region, and digital versus face-to-face register. If you treat it as one word, your translations will look wrong even when they're technically correct. I learned this the hard way in 2019 when we launched a customer-facing FAQ module for our platform. We'd pulled a standard phrasebook set for Spanish, Portuguese, French, German, Japanese, and Korean. The Spanish content read buenos días as the universal greeting regardless of when someone contacted us. A user in Buenos Aires wrote in at 7 PM and got told "good morning." The escalation wasn't about the error itself. It was about the implicit assumption that the system couldn't understand context. That one mistake cost us roughly three weeks of rework because we had to factor in time-zone detection, regional dialect preferences, and a fallback system for after-hours hours where a neutral placeholder like saludos actually worked better than a time-specific greeting.
The fix was simple in theory and annoying in practice. We built a lookup table keyed by locale and time window, with priority ordering that let regional variants override the default. Spanish-es-ar got its own afternoon/evening entry instead of inheriting from Spanish-es-419. Portuguese-pt-br separated from Portuguese-pt-pt on formality levels. The whole update took about ten hours for someone who already knew the localization stack, maybe two days for someone doing it blind.
Practical Translation Considerations
Here's where the shortcuts break down. When you're deciding how to handle greetings across languages, the first thing most people miss is that register matters more than literal meaning. A direct translation of "hello" into Japanese is not a one-size-fits-all solution. Konnichiwa is daytime and somewhat formal. Hajimemashite is for first meetings. Oyasumi nasai means goodnight and would be ridiculous as an opening line at any hour except late evening. If you're building a chatbot or an automated response system, using the wrong register makes your product sound either aggressive or confused, and users will notice within the first three sentences. Arabic has the same problem but amplified because Modern Standard Arabic differs significantly from the dialects people actually speak. Salam alaykum works universally in writing and formal speech, but in Morocco people commonly open with sabah al-khayr or just merhba, which is a totally different register. If you localize for Morocco and serve MSA content, you'll get the same response you'd get serving a formal legal document at a family BBQ. It's not wrong. It's just wrong for the setting. One counter-intuitive thing nobody tells you: sometimes the best translation for "hello" is not a greeting at all. In Korean customer service contexts, starting with (annyeonghaseyo) is polite but can feel stiff in digital channels where (thank you) as an opener reads more naturally and accomplishes the same relational goal. I've seen B2B SaaS companies in Seoul adopt this pattern deliberately and see a measurable drop in first-response friction. The data was anecdotal but consistent across three separate accounts we managed.
Get the Full Details
Language-Specific Notes That Actually Matter
Here's a quick rundown of the ones I encounter most often, with the things that trip people up: Spanish: Buenos días, buenas tardes, and buenas noches are time-gated. Using buenas noches as a greeting after 9 PM is correct. Using it at 4 PM is not. The regional variation is also significant: in Mexico qué tal is common and informal, while in Spain hola dominates casual conversation. Don't mix these without a locale switch. German: Guten Tag is the standard formal greeting. Hallo works in most digital and informal contexts. Guten Morgen and Guten Abend are time-specific like Spanish. The trap here is that German business culture treats informality as a trust signal, so Hallo in a B2B context is increasingly acceptable, but you shouldn't assume it everywhere. Default to Guten Tag until the other party switches to Hallo.
French: Bonjour is mandatory in professional and retail interactions before roughly 6 PM. Bonsoir takes over after that. is informal and should never be used with strangers or in formal writing. The critical detail most English speakers ignore: bonjour is both a greeting and a politeness marker. Walking into a French shop without saying it is considered rude, regardless of what you say next. Japanese: This is the hardest one to get right because the language encodes hierarchy directly into the greeting. Konnichiwa, ohayō gozaimasu, konbanwa — each carries different formality levels and time windows. In customer-facing automation, I recommend (the kanji version of konnichiwa) as the safest default because it's visually formal even when the pronunciation is neutral. Avoid (yaa) unless you're going for anime character energy, which your users did not ask for. Korean: is the most formal option and appropriate for institutional communications. is the standard polite form used in almost all digital customer interactions. is too casual for any professional context. The key insight: Korean honorifics extend beyond vocabulary into verb endings, so a greeting that looks correct in isolation can still produce a grammatically inconsistent message if the rest of the copy doesn't match the politeness level.
Mandarin: Nǐ hǎo () is the standard, but it can sound mechanical or even sarcastic depending on tone and context. In customer service automation, nǐ hǎo is acceptable but ín hǎo ma ( / "how are you") as a follow-up line adds naturalness that pure translation misses. Note that nǐ hǎo alone as an opener in a long-form message reads like a robot, which is ironically accurate but not strategically useful.
What Breaks in Production
The thing that actually destroys localization projects isn't the translation. It's the edge cases. Here's what I've seen fail repeatedly: Timezone detection based on IP address is unreliable. A user in Madrid connected through a VPN in Lisbon will get the wrong time window and the wrong greeting. The workaround is to let the user's account settings override geolocation, and fall back to the system timezone only when no preference exists. This added maybe forty-five minutes to our implementation but prevented a whole class of support tickets. Platform-specific character encoding issues. Korean and Japanese greetings with proper honorific particles render fine in modern browsers but break in legacy email clients and some SMS gateways. If your product sends greetings via SMS in those languages, test with actual device emulators, not just a browser. I wasted two days debugging what turned out to be a UTF-8 encoding mismatch in an SMTP configuration.
Formality mismatches between modules. Your email template might use formal Bonjour while your in-app notification uses casual Salut. Users notice this inconsistency and interpret it as a tone-deaf brand. The fix is a single style guide that maps every greeting variant to a specific channel and context, not a collection of independent translation sheets. Cultural assumptions baked into defaults. Some languages don't have a direct equivalent to "hello" as a standalone greeting. Arabic marhaban functions differently than English "hello." Mandarin chī le ma (literally "have you eaten?") is a traditional greeting that carries social weight far beyond its literal meaning. Using it in a modern customer service context is awkward and dated. The safe move is to stick with nǐ hǎo and avoid cultural fossils unless you're intentionally targeting a specific demographic that expects them.
A Realistic Approach
If you're building something that needs multilingual greetings, start with a decision tree rather than a flat list. Locale first, then channel, then time window, then formality level. Test the output on actual devices in the target region. Budget extra time for the timezone and encoding edge cases because they always show up. And don't treat "hello" as a solved problem just because you have a dictionary entry. The word is easy. The context is the hard part.
