For reading a message in another language, try Telegram's built-in translation before forwarding it to a bot. Telegram documents individual-message translation for all users and whole-chat translation for Premium. A bot is worth considering only if it meets a separate need, such as a particular output workflow that you have checked.
Translate one message
The official announcement gives the setup path Settings → Language, where enabling translation adds Translate to the message's context menu. Open the message menu in your client and choose the translation action. The gesture can differ; do not assume one long-press instruction applies to every desktop and mobile app.
In language settings, inspect the languages excluded from translation. If a language is marked as one you understand, Telegram can hide its Translate option. Test with a short foreign-language text message rather than a photo of text or a voice note; those are different input types.
The launch documentation notes operating-system differences in available languages and specified iOS 15 or later for its implementation. It is not a current compatibility matrix for every Telegram build. If the option is missing, update an official app, check language settings and compare the same message on another supported client. This review did not test each platform's menu.
Translate a whole chat
The whole-chat announcement says Premium users can translate chats, groups and channels through the Translate bar at the top. Its options control translated languages and can hide the bar. Individual-message translation remains available without buying this whole-chat feature.
Use this when you regularly read a foreign-language channel rather than translating every post separately. Do not confuse your translated view with posting translations to everyone in a group. Adding a bot to generate new messages is a different workflow with separate permissions.
What is verified about @TranslateBot
The public profile displays “Google Translate” and describes itself as a language translator bot. A display name is not proof of Google ownership, a Google API contract, a particular number of languages or automatic group translation. The checked page does not document those details.
If you inspect the bot, read its current instructions, operator identity, data policy and cost before sending text. Try an invented sentence containing a date, a negation and a proper name. Specify the target language and check whether all three survive. Do not trust a bot's own back-translation as the only quality check; ask a competent speaker for consequential text.
For group use, first establish whether the bot supports that workflow and which messages it will receive. Do not make it an administrator merely to see whether it starts translating. Obtain the group's agreement before exposing conversations to another operator.
Translation is still data processing
Telegram’s Privacy Policy, section 8.4 says text selected for built-in translation may be shared with Google or Microsoft. Meanwhile, the official FAQ about AI features says translation runs on Cocoon and never sends data to third parties. These official sources conflict. They do not establish which statement applies to a particular client or translation mode; this article does not resolve that discrepancy. Neither statement is a guarantee of offline or on-device processing.
The privacy policy separately explains that bots receive messages sent to them and may receive group messages depending on access.
For a private contract or a customer's medical details, resolve permission and processing requirements before using either route. Avoid forwarding the entire thread when a short non-sensitive excerpt would answer your question.
Review dates, currencies, negation, names and terminology before replying. If an ambiguous translation would change a booking or payment, ask the sender to clarify instead of silently guessing. For related controls, see Telegram privacy settings; if choosing a subscription, see the Premium guide.
Sources and verification
Documentation and public profiles checked on 28 September 2026. This article does not report hands-on testing. The translation-processing statements in Privacy Policy section 8.4 and the AI FAQ were rechecked on 29 September 2026; the conflict remains unresolved.
