To translate a webpage in Google Chrome, open the page and use the **Translate icon** beside the address bar on desktop, or right-click and choose **Translate to [language]**. On iPhone or Android, Chrome may show a translation bar at the top; otherwise open **More → Translate**. Choose the language you want, then check the original for important figures, deadlines and conditions.
This guide covers **Google Chrome translate website**, **how to translate a webpage to English**, **Chrome Translate not working**, and the controls on Windows, Mac, Android, iPhone and iPad. It also explains selected-text translation, Always translate, language preferences, and the limits of translating images, PDFs and live website behavior.
Quick answer: Chrome Translate on desktop and phone
Computer: visit webpage → click Translate near the address bar or right-click → Translate to [language]. Android: select the language from the top translation notification or More → Translate. iPhone: choose the language in the top translation control, or More → Translate. For the exact controls, see Chrome computer, Chrome Android and Chrome iPhone.
Sixteen principles for accurate Chrome page translation
Translate an entire webpage on Chrome for desktop
Open Chrome on a Windows, Mac or Linux computer and navigate to a site written in another language. Google’s current Chrome Help says you can select the Translate icon to the right of the address bar or right-click on the page and choose Translate to your desired language. In the translation panel, choose the target language. If nothing happens, refresh the page and check whether the site and language are supported.
The page text can become easier to read, but the source remains the website’s author-created content. Machine translation does not verify a merchant, confirm that an offer is live or rewrite a signed document into a certified target edition. Use the translated view for comprehension while checking important dates, amounts and instructions against the source. See Google Chrome desktop translation help.
Translate a webpage in Chrome on iPhone and iPad
Open Chrome on iPhone or iPad and load the foreign-language page. Chrome may display translation controls at the top; choose the language you want to read. Google’s iOS help also documents using More → Translate when the banner does not appear. For repeated use, the translation banner can offer Always translate for that source language, subject to the current settings.
Do not confuse Chrome’s interface and Safari’s Page Menu: both browsers can translate webpages, but the controls differ. On an iPhone, being able to translate a page does not mean that text inside every image or downloaded PDF will change. Check source context and use a separate appropriate workflow for actual attached files. See Chrome iOS translation help.
Translate a webpage in Chrome on Android
Open the page in Chrome on Android. Google’s documentation describes a translation notification near the top; tap the target language or open More → Translate to request it manually. You can choose a different target language through the translation options and set certain source languages to translate automatically. If the page doesn’t translate, refresh and confirm that the requested language is supported.
A browser-language preference is not the same as the language a website originally published. A translated retail page may still send you to a source-language checkout and may not support delivery to your location. Language comprehension should be followed by practical verification of actual service availability. See Google Chrome Android translation help.
Translate only a selected sentence
Sometimes you need just one paragraph or unfamiliar word rather than the whole page. On desktop Chrome, highlight the text, right-click and choose Translate selection to the preferred language. Google’s Android help describes selecting text and using the contextual Translate action. On iPhone, highlight the phrase and tap Google Translate where the option is available.
This is useful for short definitions, product descriptions and technical phrases, but it reduces surrounding context. A word like charge could refer to a price, an electrical property or an allegation. Keep the larger paragraph visible when choosing meaning, especially for conditions or a quote. If the selection omits ‘not’, a translated instruction can reverse what the author intended.
Set the default destination language
On Chrome desktop, open More → Settings → Languages and find Google Translate. Choose Translate into this language to select the preferred destination where offered. On Android, Google’s help describes Settings → Languages → Advanced → Translate into this language for appropriate app versions; iPhone provides language settings and choices through its own translation interface.
Selecting a target doesn’t make every original webpage display that language, nor does it guarantee every source language is supported. The browser may also use your preferred website languages for deciding which source-language site to request. Make the distinction between choosing an authored version of a website and machine translating the version you have open.
Turn translation prompts on or off
Google’s desktop Chrome Help documents switching Use Google Translate on or off under Languages. Android and iPhone have translation settings in their Languages menus, including whether to offer translation and whether certain source languages should be handled automatically. If Chrome stopped suggesting translations, check these controls before assuming the website itself is broken.
A user who reads Spanish comfortably may disable offers for Spanish while keeping prompts for Japanese. Always translate and Never translate are preferences, not guarantees about accuracy or browser support for every webpage. A site’s dynamic design can still prevent the expected translation of particular elements.
Always translate and Never translate need clear intent
Chrome can remember when you want a particular source language translated automatically, or when you never want to be prompted for that language. That is helpful for repetitive reading across travel sites or reference material. But an automatic translated view may hide the fact that a site has switched to a different language or that a term is culturally specialized.
If a page begins translating in an unwanted way, review the banner and language preferences to undo the rule. Do not treat a setting change as proof the website’s original text has been edited. Return to the source when an exact phrase matters for a legal condition, safety warning or financial instruction.
Page language detection can be wrong
Webpages may contain several languages, quoted source material, brand names and short fragments that do not clearly identify one language. Automatic language detection can choose the wrong source or fail to recognize a phrase. Chrome’s available manual options may let you choose the actual source and destination. Review the webpage before interpreting a strangely worded output.
For language learning, compare translated text against the original rather than only reading the target. When a page includes both English and Chinese paragraphs, a single page-wide translation setting may not preserve all nuances. Professional terminology and speech register often need additional human context.
Images, screenshots and scanned documents are not ordinary page text
A Chrome webpage can include words baked into photos, charts, advertisements and images. Page translation does not guarantee that text inside every image changes, even when surrounding HTML text becomes English. A downloaded scanned PDF also may require a separate document or image translation workflow.
Identify where the essential information lives. If a photograph contains a medicine warning, don’t invent missing words based on the surrounding page. Use an authorized image translation method and check the source. A page with readable translated navigation can still contain crucial untranslated instructions in a poster graphic.
Forms, buttons and checkout workflows need testing
A translated page may include form labels, input hints, navigation, error messages and destructive actions. A button labelled Submit should still submit, not merely save a draft. A machine-translated warning may describe an action differently from what the website actually does. Chrome’s page translation is a user convenience and does not change the site’s underlying code or permissions.
Before entering private details or making payment, verify the actual merchant, URL, required fields, language support and checkout conditions. A translated page may continue into a different-language payment service. A clear-looking label does not make an unknown site trustworthy or create rights the source never offered.
Links and URLs must remain literal
A site can contain account names, order codes, phone numbers and URLs. These are identifiers rather than everyday words, and changing one character can send someone elsewhere or break a lookup. If you copy translated content into a document, preserve exact URLs and codes while translating their surrounding explanations.
In right-to-left pages, Latin links and numbers may appear visually reordered. Do not manually reverse their characters. Test the actual clickable destination and check that a label such as Download the French guide opens an actual French resource. Translation of an anchor label does not translate its separate file.
Chrome page translation is different from Live Translate for audio
Google’s Chrome desktop help now refers users to Live Translate for audio content on a page. That is distinct from translating written webpage text and depends on the audio and relevant browser capabilities. Do not claim a translated article creates dubbed audio or that every embedded video receives accurate subtitles.
For educational videos, check the actual captions, their language and any timing error. A browser may show translated text while the media itself remains in the source language. Treat written prose, audio transcription, subtitles and downloadable files as separate deliverables.
Preserve dates, numbers and real locations
A translated travel website may describe an event at 8 p.m. in a named time zone, a train fare in local currency and a station name. Translation should not change the event instant, currency or actual destination. A target language commonly used in another country does not automatically imply a different fare or service area.
Relative words such as tomorrow depend on when the source page was updated, and stale content can persist online. For live reservations, official schedules or product prices, confirm current status through the authorized source before making decisions. Machine translation does not independently supply real-time verification.
Privacy and authenticity are separate from language
A website requesting a password, payment card, health detail or identity document remains subject to the same security and privacy risks after being translated. Check its domain, known account provider, actual processing notice and other evidence of legitimacy. Do not enter credentials merely because the page looks natural in your language.
Before copying confidential page content into another translation service or an extension, evaluate the service’s access and data handling. Built-in translation and third-party browser extensions may operate differently. No language feature grants permission to share someone else’s private records or bypass the source website’s access controls.
Compare the original and target for high-impact claims
A webpage can be fluent yet mistranslated about ‘up to’, ‘unless’, ‘not’, ‘under review’ or ‘only for eligible users’. Those phrases affect whether a reader can apply, pay, cancel or continue safely. When a decision has significant consequences, review the source sentence and seek a competent bilingual or subject review rather than treating page translation as a legal certification.
For an academic source, preserve author, publication date, evidence and citations. For a product, keep model versions, sizes and actual warranty restrictions. For a school, preserve syllabus level and registration requirements. Equivalent comprehension means a reader in either language will make the same legitimate choice.
Check the page after navigation and dynamic updates
Some websites render or update content after scrolling, logging in, changing filters or entering data. A translation performed earlier may not cover newly loaded text or user-specific errors consistently. Refresh or request translation again where necessary, and confirm what the actual page now displays.
If a website offers an official localized version, consider using it when the business specifically supports that region and language, while still checking product and policy differences. A browser-generated translation of the source site and a merchant’s separately published localized site are not automatically identical services.
Official guides: Chrome Website Translation · Android Translation · iPhone Translation · Translate Google Drive Files · Master Art of Translation.
Forty worked Chrome website translation cases
These examples show where browser translation may be technically available yet still require judgment about context, safety, linked files or actual website behavior. They are fictional and intended for practical checking.
1. The translation icon is absent on desktop
A user opens a French website in Chrome but sees no Translate icon at the right of the address bar. Google’s Help offers another route: right-click the webpage and choose Translate to [language] where supported. Check Languages and Google Translate settings, then try refreshing. If the page’s source language or current content is unsupported, do not claim one hidden switch will always make translation possible. Verify actual content and browser version before making a stronger assertion.
2. The user has turned translation off
A colleague previously disabled translation prompts because they already read several languages. Now they expect Chrome to offer every foreign webpage automatically. On desktop, Google documents Settings → Languages → Use Google Translate; mobile has comparable but differently arranged translation controls. Enable the appropriate option where permitted, or request manual translation. A preference about when to prompt does not change the site’s original words or confer factual accuracy on translated content.
3. The site is on the Never translate list
A person once selected Never translate for Japanese pages, then wonders why Chrome does not offer translation on a new Japanese website. Review the language preference in Chrome and change the applicable setting, rather than blaming that particular website. Test one supported public page afterward. Never translate and Always translate are browser choices, not evidence the source language is unimportant or that all future results will necessarily be correct.
4. Always translate hides an unfamiliar phrase
A learner sets Chrome to always translate Spanish pages, then forgets that an assignment requires analyzing the source Spanish wording. The translated view can conceal idioms and original grammar. Use the translation control or source view to return to the original, and compare both versions. Automatic convenience is useful for reading, but a foreign-language class, quotation or legal question may depend on exactly what the original author wrote.
5. The destination language differs from the reader’s needs
A user living in Singapore prefers Mandarin for interface menus but needs to read a particular webpage in English. Chrome initially chooses another target based on language preferences. Use the translation panel’s language choice and review what appears. Do not infer someone’s desired translation language from their location or nationality. In multilingual Singapore, the language of the page, browser interface and desired output may all differ.
6. A source webpage mixes two languages
An academic page includes paragraphs in English and Japanese, with some Latin scientific names. Chrome’s page detection may focus on one language. A machine-translated paragraph can mistranslate terminology or leave some text unchanged. Identify the actual source of each relevant passage and check important wording against the original. A single page-wide choice should not be represented as proof that every sentence and script was translated correctly.
7. Selected text excludes a crucial not
A user highlights only the words ‘take the medicine’ from a longer source sentence that begins ‘Do not’. Translating the cropped selection changes the action to an instruction rather than a prohibition. When a phrase controls safety, eligibility or payment, include its entire condition and parent paragraph. Confirm the original with a qualified person for high-stakes decisions. Selected-text translation is convenient but can remove essential meaning through the selection boundary.
8. A website’s pricing currency is mistaken for a conversion
A product page shows SGD 80. After translation into French, the customer assumes the amount is eighty euros, despite the original currency. Chrome changes language, not the checkout denomination. Keep the actual amount and units, verify shipping availability and use a separate approved conversion if necessary. A translated ecommerce page cannot independently guarantee final fees or tax terms for another region.
9. The original says up to half price
A retailer offers ‘up to 50% off selected lines’ and a translated banner says ‘everything is half price’. It loses both the maximum and selection restriction. Review the original promotion and the actual cart price. A customer should know which products qualify and when the offer expires. If the translated web page overstates it, rely on the merchant’s approved terms and seek clarification rather than assuming Chrome authorized a larger discount.
10. An order is not yet delivered
A logistics webpage says a parcel is in transit and has not been delivered. A target sentence omits ‘not yet’ and appears to say the package arrived. The delivery state is operational data separate from grammar. Keep dispatched, in transit, attempted delivery and delivered distinct. Use the official carrier tracking record for current confirmation rather than treating a machine-generated phrase as proof of receipt.
11. A registration page is only an application
A school offers limited workshop places. The page invites families to apply, but Chrome’s translated button sounds like confirmed admission. A request to apply, application received and actual place booked are different stages. Check the real form and its confirmation messages. Do not skip payment, eligibility or guardian consent because the target language suggests an automatic guarantee. A useful translated site lets applicants understand exactly what remains to do.
12. A date is ambiguous across regions
A foreign website lists an event as 04/05/2026 with no month name. A reader translates the page and interprets the date using their local convention. The digits may have meant another month. Confirm the website’s source locale or an official structured calendar record before making travel plans. Use a month name in your own target summary when a verified date is needed. Translation alone does not establish the original date’s interpretation.
13. A named time zone disappears
A conference page announces 8 p.m. Central European Time. The translated target says 8 p.m. without a zone. Attendees in Singapore could join at the wrong time. Preserve the source zone and date or calculate an accurate local equivalent separately. Daylight-saving rules may change the offset. A browser translation should not silently create a new instant for every user who shares one target language.
14. A country name changes geographic scope
A travel website recommends a museum in a specific town. The translated page replaces that town with a nearby larger city because its name is familiar. The reader might take the wrong route or book a different attraction. Preserve official location and address, and verify the linked map. Translation should make an unfamiliar place understandable, not substitute a false destination.
15. A technical code is translated into prose
An IT documentation page includes error E-4012 and a configuration key that looks like an English word. A model-generated translation changes the code, preventing a developer from finding the actual error. Keep machine-readable code, file paths, API tokens and version numbers literal while translating explanatory language. Test the same bug reproduction in a safe environment. A fluent guide with broken identifiers is not operationally correct.
16. A heading hides a copied URL
A translated page displays an inviting local-language link label, but its destination remains a source-language PDF or outdated download. The anchor words do not translate the file or update the URL. Click the link, verify which version and language it contains, and state the limitation honestly. If you need a reviewed translation of an attachment, handle that as a separate artifact with its own approval and privacy rules.
17. A PDF is treated as webpage text
A browser displays a PDF in a tab, and the reader assumes Chrome’s website translation necessarily covers every page of the PDF, including scanned image text. These are different content formats and may require a separate translation workflow. Check actual result and file type, particularly for nonselectable scans, signatures and technical diagrams. Do not describe a document as fully translated without confirming coverage page by page.
18. Words in a screenshot are unchanged
An article includes a screenshot of a software application’s menu. Chrome translates the article prose, but the UI labels shown in the photograph remain English. A target reader may still need the source-language menu names to locate controls. Prepare a carefully verified description or localized image where authorized, and do not invent a current menu path without confirming the actual software version.
19. A dynamic error message appears after translation
A translated booking webpage shows English again when a user submits an incomplete form. New validation text was generated after the initial page translation. Translate or interpret that message separately, keeping the actual rule and field name. Avoid ignoring errors because the earlier page looked completely localized. A successful browser translation is not proof every future dynamic state will use the target language.
20. A checkout button promises a different operation
A site’s source button means Save draft, while a target page renders it as Pay now. The user’s expectation and real action disagree. Before entering sensitive information or confirming payment, check the actual context and merchant terms. A reader who knows only the target should not be tricked into a purchase or misled into thinking a draft has been published. For consequential controls, prefer an officially supported localized site or competent review.
21. A website’s region selection is not just language
A merchant offers an English Singapore site and an English US site with different shipping and taxes. Translating one into French does not mean the same store supports France. Region availability, currency, products and policies are separate operational facts. Check the real destination, market selection and checkout. Language alone cannot authorize cross-border service, and the same words may conceal different market-specific terms.
22. A privacy warning is weakened
An account page says users must not share recovery codes. A target phrase reads like a casual suggestion, potentially encouraging unsafe behavior. Treat mandatory and prohibited actions as essential to meaning. Compare the original and check the actual security procedure rather than following a weak machine rendering. Never disclose passwords or codes to unknown sites simply because their instructions are now in a familiar language.
23. A website is mistaken for legitimate after translation
A phishing page contains awkward foreign-language text and asks for banking credentials. Chrome translates it into professional English, making it seem more credible. Language quality does not authenticate the domain or publisher. Verify the site through an existing trusted source and avoid entering sensitive data in response to an unfamiliar link. Translation and security assessment are independent tasks.
24. A browser extension asks for broad access
A user installs a third-party translator extension that requests permission to read all websites, even though Chrome has built-in translation. Such permissions can be consequential when private accounts or customer data appear on screen. Review the developer and requested data scopes before installation. Do not claim every extension uses the same safeguards as Chrome’s official feature. A trustworthy language tool is selected according to real data handling, not only attractive results.
25. An academic citation is misattributed
A research article quotes a second scholar and then disputes that scholar’s conclusion. The translated version loses quotation boundaries and seems to attribute the claim to the main author. Preserve source identity, reported speech and the argument’s actual stance. Follow the DOI or publication record when verification matters. A translation should not invent support or opposition from the wrong academic source.
26. A source result becomes a causal promise
A study webpage reports a small pilot result. The target says every student will improve if they use a particular method. Evidence scope and certainty have changed. Keep study size, observed outcome and conditional language. If the original webpage is incorrect or oversimplified, correct the facts through a separate research process rather than silently revising only the target. A fluent summary cannot replace statistical reasoning.
27. A website is updated after translation
A support article loads in English, Chrome translates it, and the company later updates its instructions for a newer product version. A saved screenshot of the target may then be stale. Check the current official source and supported software version before giving step-by-step guidance. Translation does not freeze a website’s changing facts, and a target-language screenshot should not be used indefinitely as current documentation.
28. An old offer says tomorrow
A historical article includes a discount ending tomorrow relative to an old publication date. A new browser translation doesn’t renew the offer. Keep source date context and check current seller terms, stock and regional availability. Do not publish a target summary saying the discount is live unless it has been verified. A clear language rendering should preserve the difference between historic announcements and active commercial opportunities.
29. A code-switched post is mistranslated
A Singapore education page mixes English, Mandarin and Malay terms, including a subject-specific abbreviation. Chrome may produce one target-language page but flatten a culturally specific word into the wrong concept. Check each important term in actual academic or social context. A human reader may need a short glossary rather than a literal replacement. Do not infer personal identity or nationality from a mixed-language expression.
30. A link is visually reversed in right-to-left prose
An Arabic translated website displays Latin URLs and numbers with punctuation that appears out of order. Manually reversing the literal characters to fix the appearance can break the link. Use appropriate bidirectional rendering while keeping URLs, mathematical notation and product IDs unchanged. Test actual destinations and copied strings from the target page, rather than trusting their visual balance alone.
31. The translated page hides a visual accessibility issue
A website uses icons and color alone to distinguish important options. Translating the visible text does not guarantee its screen-reader labels, input descriptions or chart alternatives are accessible in the target language. Verify the actual user interface and source descriptions where available. A person using assistive technology should have the same meaningful action and warning, not a misleading control name.
32. A warranty exclusion disappears
An ecommerce page explains a two-year warranty but excludes accidental damage. The target text highlights the headline while losing a small disclaimer. This changes product terms. Read the original conditions and confirm them against merchant policy before claiming coverage. Browser translation is a reading aid, not an independent legal amendment. A buyer should know the same scope and exclusions as a source-language customer.
33. A translated review hides dissatisfaction
A customer says a product works but customer support was slow. A target-language repost includes only the praise, creating a stronger testimonial. Translate both positive and negative content and keep proper attribution. Do not use an edited translation to fabricate an independent endorsement. Review reuse permissions before publishing someone else’s words commercially.
34. A search result displays one language, destination another
A search result’s title appears translated while the actual landing page is in another language. A visitor assumes the whole resource has been localized. On the page, check the actual text, embedded documents and links before claiming full coverage. Search snippets and webpage contents are distinct artifacts. A translated headline is only helpful when the destination actually provides the promised information.
35. A form asks to delete when the target says archive
A user management site offers permanent deletion, but machine translation describes it as hiding an account. This changes a consequential operation and may cause unintended data loss. Confirm the exact source-language action and official help before clicking. A target that sounds polite is not accurate when it conceals irreversibility. For account controls, use verified support or a competent translator if there is any doubt.
36. A mobile browser’s menu differs from desktop
A user follows instructions to right-click a webpage on an iPhone and cannot find the desktop contextual translation. Chrome iOS uses its own More → Translate and selection actions. Match steps to actual platform and interface version. A correct explanation should not fabricate an absent control or send the user through settings that apply only to another operating system.
37. A page translation unexpectedly stops on a login screen
A public article translates, but its protected member area requires a sign-in and opens in the source language. Translation cannot bypass a login or create an account. Verify the legitimate service provider, credentials and permissions before proceeding. Treat text on the authenticated page as new content to interpret separately, and avoid pasting private records into an unknown translation extension.
38. A live video is confused with written page translation
Chrome translates the page around an instructional video; the spoken audio remains in the source language. The target summary claims the course has a translated recording. Chrome’s separate Live Translate capability for supported audio should be checked explicitly rather than inferred from page translation. A correct accessibility statement names which track or subtitles exist and does not invent dubbed audio.
39. A long source page contains unreviewed critical details
A complex official instruction page translates successfully, so the reader acts without checking a small condition in the final section. Machine translation may still err with domain terms, exceptions and dated regulations. Use an approved original, read the whole relevant procedure and verify requirements through the responsible institution. High-stakes decisions need more than a successful Chrome translation indicator.
A reliable six-step Chrome translation workflow
Choose browser and page
Identify Chrome desktop, Android or iPhone, and the actual page URL and source language. Use its supported Translate control rather than a menu from another browser.
Select the target preference
Choose a destination language and determine whether to translate once, always for that source language or not at all. Confirm the content actually displayed.
Check complete source meaning
Review the original where numbers, negative instructions, dates, prices, links or legal and technical language control decisions. Identify material embedded in images or media separately.
Test the real user action
If the page is a form or checkout, check genuine website identity, product, market, account access and what its buttons actually do. Translation cannot change the merchant’s own software behavior.
Translate other assets only as needed
Handle images, PDFs, audio, video and linked resources in their own suitable authorized workflows. Do not claim the browser localized everything automatically.
Preserve a valid record when needed
For consequential information, note source URL, publication or access date and the exact verified statement. Label machine translation separately from independently checked facts.
Frequently asked questions
How do I translate a website in Chrome on PC?
Open the site and click Translate near the address bar, or right-click and select Translate to the language you need.
How do I translate in Chrome on iPhone?
Open the webpage and use the translation control at the top, or More → Translate if the prompt is not visible. Supported settings can remember a source language.
How do I translate in Chrome on Android?
Use the top translation notification or More → Translate, then choose a language. You can configure Languages settings for preferred translations.
Why isn’t Chrome offering translation?
Check the Use Google Translate setting, any Never translate choices and whether the page language is supported. Try refreshing and manually requesting translation.
How do I change the default target language?
On desktop, Chrome Settings → Languages → Google Translate → Translate into this language. Mobile controls are in their corresponding language and translation settings.
Can I translate just one paragraph?
Yes. Select text and use Chrome’s Translate selection action on supported desktop and mobile clients. Include enough context to preserve negation and meaning.
Does Chrome translate PDFs and screenshots?
Do not assume webpage translation handles every embedded image or downloaded document. Those materials may require separate authorized translation and checking.
Does Chrome translate audio automatically?
Page text translation is separate from Live Translate for audio. Check the actual feature and supported content; translated page text does not create dubbing.
Is translating a page the same as changing its country?
No. Language, region availability, checkout, currency and live services are different properties of a website.
Can I trust a translated payment or medical instruction?
Verify the original, source identity and relevant professional guidance before acting. Automatic translation is not authentication or certification.
What if a page has several languages?
Review detected source languages and translate relevant passages with context. A single page-wide result may not capture code-switching or technical phrases.
What is the final quality test?
A reader using the target should understand the same factual claim, conditions, link and next action as someone reading the original.
Final Chrome translation checklist
Check the browser and device, real page source, source and target language, translation preferences, important numbers, names, links, qualifiers and dates, embedded image or media text, genuine site identity, form actions, privacy and any current service conditions. Chrome can make foreign-language information easier to read; a reliable decision still depends on the truth and meaning of the underlying source.
Official Google Chrome help: Chrome Computer Translation · Chrome Android Translation · Chrome iPhone Translation · Translate Drive Documents.