Skip to content

Use Built-in Capabilities

Float Translate includes extensions for more than translation alone. Their capabilities can polish or summarize text, search the web, read text aloud, look up words, send vocabulary to another tool, perform OCR, or connect to different translation services.

“Built in” means the extension ships with Float Translate. It does not always mean the capability is ready without configuration: a provider API, account, local application, or service credential may still be required.

TaskExamples
Translate textGoogle Translate, Bing, DeepL, local agent translation
Work with AITranslate, polish, summarize, explain
Search the webSearch with a configured website preset
Read text aloudSystem speech or a configured TTS provider
Look up wordsYoudao Dictionary and available external dictionary actions
Save vocabularyEudic, Shanbay, Maimemo
Recognize imagesTencent OCR
  1. Open Extensions and find the built-in extension that owns the task.
  2. If it needs a provider, first add the service and complete its credentials or local connection settings.
  3. Create or enable the capability instance and finish its required options.
  4. Add the capability to the surface where you want to use it, such as the floating capsule or translation panel, or bind it to a shortcut or workflow.

See Extensions, Services & Capabilities for the relationship between these objects, and Configure Capabilities for the configuration steps.

Select or capture suitable input, then choose the capability from the capsule or panel where you placed it. For a frequently used action, assign it under Shortcuts. Use a workflow when the output of one step should feed another step.

Not every capability accepts the same input. For example, a text action cannot process an image until OCR has produced text, and a vocabulary action may only accept a word or short phrase.

Check these items in order:

  1. The extension is enabled.
  2. Its required service exists and has complete credentials or connection settings.
  3. The capability instance is enabled and its options are valid.
  4. The capability has been added to the capsule, panel, shortcut list, or workflow where you expect it.
  5. The current input type, language, app, and platform match the capability conditions.