Screen Translator Apps Compared

Most lists of screen translator apps rank them. This one does not. Ranking would mean scoring translation quality, and we have no way to measure that objectively enough to put our own app at the top without it being a conflict of interest. Instead, this page compares the things every app has to disclose anyway: the permissions it asks for, and what it does with your screen and your text.

The reason this matters is that a screen translator sits in a sensitive position. To do its job it needs to see your screen, read the text on it, and put a translation back on top. How it gets that text — and where that text goes afterwards — differs a lot between apps, and it is rarely something the store page tells you up front.

The comparison

Accessibility and listener services

An Accessibility Service is an Android capability designed to let an app help a user with disabilities. It is powerful: an app holding it can read text from other apps, observe taps, and watch for content changes across the whole device. Android requires it to be enabled deliberately, through a settings screen, and it stays active until you turn it off.

Two of the apps in this table name it openly on their Play listings, which is more disclosure than most apps give. A third uses a different system service — Bubble's privacy policy describes a Notification Listener Service for its chat translation feature, which reads incoming notifications rather than the general UI. Whether that matters more or less to you is a judgement call, but at least it is written down.

There is a narrower mechanism available too. Android's MediaProjection API hands an app a single screen frame after a system dialog you approve, and the capture ends when you stop. The app never receives a persistent handle to your screen. The cost is that it receives an image rather than a view hierarchy, so it has to run OCR to read the text at all. HandyXlate uses that path and does not declare the AccessibilityService API.

It would be dishonest to present that as free. Reading a view hierarchy can be more precise for some apps and can pick up text that is rendered but not visible. OCR works from the pixels that are actually on screen, so it depends on legibility — very small, low-contrast, or heavily stylized text gives it less to work with.

Where OCR runs

Once an app has an image, something has to recognize the text in it. Where that happens is a separate question from where the translation happens, and the two are often conflated.

• On-device OCR means the image is read on your phone. The screenshot does not need to leave the device for the text to be recognized.
• Cloud OCR means the image is sent to a server to be read. This is usually more accurate on hard images — manga, stylized type, dense layouts — because the server can use bigger models.
• Apps that offer both usually default to on-device and let you opt into cloud. Gaminik does exactly this, and names the trade-off in its own listing.
• If an app supports both, the setting you have chosen matters more than the app's default. A screenshot that never leaves your device in one mode can leave it in another.

Bubble's privacy policy does not say where its text recognition runs, so that cell is blank rather than assumed.

What leaves your phone

This is the column where the differences are largest, and where the word 'screenshot' is most often misused. Keeping the image on your phone is not the same as keeping the text on your phone. A screenshot is a picture of whatever else was on your screen — messages, account numbers, notifications. Recognized text is just the words. They are very different amounts of information to hand to a server.

• Never transmits the image: HandyXlate, Bubble, and Offline Screen Translator all state their screenshots do not reach a server.
• May transmit the image if you opt in: Gaminik uploads it when you select its cloud OCR engine.
• Not stated: we could not find a public statement from Instant Translate describing where screen-capture data goes.
• Sends recognized text onward: several apps send the recognized text to a translation provider. Bubble names Google Translate, Bing Translator, DeepL, and Yandex Translator. Gaminik names Google as an example of its third-party translation providers.

So 'we do not upload your screenshots' and 'nothing about your screen leaves your phone' are two different promises, and plenty of apps make only the first one.

Ads, analytics, and tracking

Ad SDKs and analytics SDKs are separate from each other, and both are separate from ads actually being shown. An app can show no banner and still ship a crash reporter and an analytics SDK — those still run on your device, and they still carry identifiers.

Two apps in this table list Firebase Analytics, Crashlytics, and Facebook SDKs in their privacy policies while showing no ads. One lists AdMob alongside those. One shows ads and lists nothing in its policy. One states it uses no analytics or tracking at all. Ours is the fifth: no ads, and no analytics SDK — the only third-party code is Play Billing, which exists to process the in-app purchase.

Where HandyXlate is not the best option

A comparison written by an app developer has an obvious incentive to flatter that app, so here is the part that cuts the other way. Three things are true about HandyXlate and none of them are flattering.

• If you select an online translation engine, HandyXlate sends the recognized text to our servers and on to a translation provider. The screenshot still never leaves your device, but 'nothing leaves your phone' would be false in that mode. Switch to on-device translation and every step stays local.
• HandyXlate does not declare an Accessibility Service, which also means it cannot read text that is rendered but not visible on your screen. Accessibility-based apps can catch things this approach cannot.
• If you add the in-app purchase, the merged manifest ends up declaring eight permissions, not the six the app ships with. Two of them come from Play Billing. We are not going to round that down to look tidier.

We also did not compare translation quality, speed, or language coverage in this table. Those are real differences between these apps. They are also the ones we have the least standing to judge, and a page that scored them would mostly be an advertisement.

How to check any app yourself

You do not have to trust a table like this one. Everything in it can be checked in about two minutes.

• Open the app's Play Store page and read the description and the privacy policy section. Two apps in this table disclose their Accessibility use in the description itself — search the page for 'accessibility'.
• On your phone, go to Settings, then Apps, then See all apps, then the app you want, then Permissions. That list is what the app actually requests, not what its marketing says.
• For accessibility specifically, go to Settings, then Accessibility, then the installed-services list. Nothing should appear there unless you personally enabled it.
• Open the privacy policy and search for 'screenshot', 'screen capture', 'transmit', and 'third party'. Apps that upload usually say so somewhere, even if not in the first paragraph.
• If a cell in our table says 'Not publicly stated' and you find an answer, tell us and we will correct the row.

Questions people ask when comparing these apps