Skip to main content
Your plug-in

Offer your card in other languages

Add a language switch to your plug-in's card: BizPlug translates the card's own buttons and screens, and you provide the translations of your data in a CSV file.

Browse all topics

Your card can be shown in up to 14 languages as well as English: Arabic, Korean and Japanese from plug-in version 0.38.0, and Hindi, Spanish, French, Bengali, Portuguese, Russian, Indonesian, Urdu, German, Italian and Dutch from 0.39.0. The card's own buttons and screens are translated by BizPlug. Your data (your services, questions and answers, items and their descriptions, members' descriptions, your agenda and the rest) is shown in the translations you provide, so customers read what you wrote. BizPlug does not translate your data: you translate it yourself, or with your own AI account through the CLI (below).

Add a language

  1. 1Open your plug-in under My plug-ins and open the Look tab, then Card languages.
  2. 2Under 1. Languages next to English, tick the languages you want and press Save languages. A language marked *needs plug-in 0.39.0* is offered once you upgraded.
  3. 3Under 2. Your translations, press Download your card's texts (CSV). The file has one row per text of your card and per language you ticked, with three columns: language, english and translation. It is made from your latest accepted files, so upload your data first.
  4. 4Open the file in a spreadsheet and fill in the translation column. Leave a row empty to keep that text in English. Save it as CSV in UTF-8, so text in every script is kept.
  5. 5Choose the file and press Upload translations. The message says how many texts of your card each language now covers. Each language in the file replaces the translations you saved for it before; the other languages are kept.
  6. 6Ask for a deploy on the Data tab. Your translations reach your card when your plug-in is published again, on test first.
  7. 7If your plug-in is on an older version, press Upgrade on its Overview tab first.

What customers see

  • A language switch under your card's header, with English and each language that has translations. A language you ticked but did not translate is not offered.
  • The card opens in the customer's own language when ChatGPT or Claude says which one it is and your card offers it. Otherwise it opens in English, and the customer can switch.
  • Arabic and Urdu are shown right to left.
  • Names, prices, addresses and links stay as you wrote them: your business's name and your members', speakers' and exhibitors' names are not in the file. A text you did not translate shows in English.
  • Requests still reach you in your own language: what a customer picks in Korean arrives with your own item and service names.
  • In the chat, ChatGPT or Claude answers in the customer's language as it always does; your card is what changes.

Translate with your own AI, from a terminal

If you would rather not translate every text by hand, the BizPlug CLI can do it with your own Anthropic account. It runs on your computer: the texts go from your computer to Anthropic with your API key, which BizPlug never sees, and the cost is on your Anthropic account.

  1. 1Install the CLI and sign in: npm install -g @bizplug/cli, then bizplug login.
  2. 2Set your own key: export ANTHROPIC_API_KEY=<your key>.
  3. 3Run bizplug translate <plugin> --languages ar,ko. It translates the texts that have no translation yet and writes them to a CSV.
  4. 4Open the CSV and check the translations: customers read them as yours. Correct what needs it.
  5. 5Save them: bizplug translations <plugin> --languages ar,ko --upload <file.csv>, then ask for a deploy.

When you change your data, download the file again: new texts appear with an empty translation, and texts you removed are left out. Translations of texts that did not change are kept.

From a terminal or a script: put "languages": ["ar", "ko", "ja"] and "translations": { "ko": { "<English text>": "<translation>" } } in the business profile you send with bizplug push. See the BizPlug CLI.

Last reviewed 22 November 2026

Was this page helpful?