The string =?UTF-8?B?...?= is technically called "Encoded-Word syntax." It is used in email headers (like the Subject line) to allow non-English characters to pass through older email servers safely.
If you see the code instead of the text, it means your email app failed to decode that string into readable text. This is often a temporary glitch in the email client software.
There are three primary culprits for this frustrating error. You are likely experiencing one of the following:
As of 2025, Ubisoft Connect sends emails correctly in UTF-8 for new users. However, the search volume for "uplay user get email utf 8" persists because:
If you are a new user, you will likely never see this error. If you are an old user, change your username to ASCII and the problem vanishes. uplay user get email utf 8
Sometimes, the email isn't fully broken, but the characters look "scrambled." This happens when a UTF-8 email is mistakenly interpreted as a different encoding standard (like Windows-1252 or Latin-1).
Look at the email. Do you see these patterns?
If yes, your email client is reading UTF-8 bytes as if they were Windows-1252.
When documenting UTF-8 email issues in Uplay: The string =
Example report snippet:
Issue: Uplay API returns email "müller@example.com" instead of "müller@example.com"Root cause: API layer decodes UTF-8 bytes as ISO-8859-1 before JSON serialization.
Hex evidence:
Fix: Set charset=utf-8 on Content-Type header and disable automatic ISO-8859-1 fallback.If you see the code instead of the
Uplay/Ubisoft Connect uses UTF-8 for international email addresses and usernames. However, many backend systems and APIs historically had issues with non-ASCII characters in emails.
Key standards:
import requests
import json