--- title: "Autolanguage plugin" --- # Autolanguage plugin ## Install the plugin Before installation please check that the below system requirements are met. You can ask your webhoster if the server you are working on supports them. You can also find the information in the Joomla! backend under System > System information. ## General requirements - Joomla! 5.x of 6.x ## Preparations - Create a full backup of the website. You can use [Akeeba Backup](http://www.akeeba.com) to create a quick one - Upgrade to the latest version of Joomla! ## Installation (upload & install) The installation of our extensions is done with the Joomla! installer. Anyone that is already using Joomla! shouldn't have any problem, for those that are somewhat new in Joomla! we'll explain the steps required to make the installation of the extensions in your website. 1) After downloading the installation file from our website, go to your Joomla! administration and go to **System > Install > Extensions** ![install 01](https://joomill-templates.com/images/documentation/general/install-01.jpg) 2) Then select the file in the tab **Upload Package File**, after a few moments you'll get a message saying the extension is installed. ![install 02](https://joomill-templates.com/images/documentation/general/install-02.jpg) 3) The plugin will be published automaticly. Go to **Extensions** » **Extension Manager,**find the Autolanguage plugin (System - ) and see if the plugin to **Published**to check this. Now you're ready to start using our extension!   [Lees meer...](https://joomill-templates.com/autolanguage-plugin/install-the-plugin.md) ## Configuration - General TheAutolanguage plugin is packed with options, giving you control over how it works and behaves. Here is the full list of the options you can find in the **Autolanguage System plugin settings**. **Plugin Tab:** ![config 01](https://joomill-templates.com/images/documentation/autolanguage/config-01.png) | | | | --- | --- | | Translation method | You can choose: **Upon saving (Alert banner)**![config notification](https://joomill-templates.com/images/documentation/autolanguage/alert-banner.png) or **Batch (Overview button) ![mode overview](https://joomill-templates.com/images/documentation/autolanguage/mode-overview.png)** | | Show Notifications *(only visible when Translation method is set to Upon save (Alert Banner))* | Show a notification at the top of the edit screen if the item will be automatically translated upon saving. ![config notification](https://joomill-templates.com/images/documentation/autolanguage/alert-banner.png) You can select/unselect the target languages before saving. | | Active Source Language | Select the language used as the source. The plugin only works if the item being saved matches this language. '*' is ignored. | | Target Languages | Select which languages to translate to. | | Unselected Target Languages *(only visible when Translation method is set to Upon save (Alert Banner) and 1 or more Target Languages are selected)* | Determine whether languages not selected above should be shown when editing an item. E.g. when you only select English and don't select French and Spanish, the Alert Banner looks like: ![alert banner unselected languages](https://joomill-templates.com/images/documentation/autolanguage/alert-banner-unselected-languages.png) You can always manually select the Spanish and French languages before saving this item. | | Debug | Enable logging to help troubleshoot issues. Logs are stored in the Joomla log folder. | [Lees meer...](https://joomill-templates.com/autolanguage-plugin/configuration.md) ## Configuration - Service & API **Service & API Tab:** | | | | --- | --- | | Translation Service | Choose which service to use for translations. You can choose from - Google Translate API - Microsoft Azure API - OpenAI (ChatGPT) - Mistral AI - Deepl API (PRO Only) - Google Gemini API (PRO Only) - Anthropic (Claude) (PRO Only) - xAI / Grok (PRO Only) - 'Copy Only' duplicates content without translating.  | | DeepL API Key *(only visible when Translation Service is set to Deepl API)* | Enter your DeepL Authentication Key (ending in :fx for Free accounts). [Read how to get your Deepl API Key here](https://joomill-templates.com/index.php?option=com_content&view=article&id=311:deepl-api-key&catid=105:autolanguage-plugin&Itemid=5374). | | Glossary ID *(only visible when Translation Service is set to Deepl API)* | Optional: The ID of a specific DeepL Glossary to apply. | | Formality *(only visible when Translation Service is set to Deepl API)* | Choose whether the translation should lean towards formal or informal language (if supported by target language). | | Google Translate API Key *(only visible when Translation Service is set to Google Translation API)* | Enter your Google Cloud Translation API Key. [Read how to get your Google Cloud Translation API Key here](https://joomill-templates.com/index.php?option=com_content&view=article&id=309:google-cloud-translation-api-key&catid=105:autolanguage-plugin&Itemid=5374). | | Google Gemini API Key *(only visible when Translation Service is set to Google Gemini API)* | Enter your Google Gemini API Key. [Read how to get your Google Gemini API Key hereGoogle Gemini APIRead how to get your Google Gemini API Key here](https://joomill-templates.com/index.php?option=com_content&view=article&id=326:google-gemini-api-key&catid=105:autolanguage-plugin&Itemid=5374). | | Microsoft Azure API Key *(only visible when Translation Service is set to Microsoft Azure API)* | Key 1 or Key 2 from your Azure Translator resource. [Read how to get your Microsoft Azure API Key here.](https://joomill-templates.com/index.php?option=com_content&view=article&id=310:microsoft-azure-translator-api-key&catid=105:autolanguage-plugin&Itemid=5374) | | Region *(only visible when Translation Service is set to Microsoft Azure API)* | Required if you use a regional resource (e.g. 'westeurope'). Leave empty/global if using 'Global'. | | OpenAI API Key *(only visible when Translation Service is set to OpenAI (ChatGPT))* | Enter your OpenAI API key [Read how to get your OpenAI API Key here.](https://joomill-templates.com/index.php?option=com_content&view=article&id=312:openai-api-key&catid=105:autolanguage-plugin&Itemid=5374) | | Model *(only visible when Translation Service is set to OpenAI (ChatGPT))* | Select the AI model to use for translations. The list of models will be fetched after you enter the API key and click 'Save'. | | Anthropic API Key *(only visible when Translation Service is set to Anthropic (Claude))* | Enter your Anthropic API Key (from console.anthropic.com) [Read how to get your Anthropic API Key here.](https://joomill-templates.com/index.php?option=com_content&view=article&id=324:anthropic-api-key&catid=105:autolanguage-plugin&Itemid=5374) | | Model *(only visible when Translation Service is set to Anthropic (Claude))* | Select the Claude model to use for translations. The list of models will be fetched after you enter the API key and click 'Save'. | | xAI / Grok API Key *(only visible when Translation Service is set to xAI / Grok)* | Enter your Grok API Key (from console.x.ai) [Read how to get your Grok API Key here.](https://joomill-templates.com/index.php?option=com_content&view=article&id=327:xai-grok-api-key&catid=105:autolanguage-plugin&Itemid=5374) | | Mistral AI API Key *(only visible when Translation Service is set to Mistral AI)* | Enter your Mistral AI API Key (from console.mistral.ai) [Read how to get your Mistral AI API Key here.](https://joomill-templates.com/index.php?option=com_content&view=article&id=328:mistral-api-key&catid=105:autolanguage-plugin&Itemid=5374) |   [Lees meer...](https://joomill-templates.com/autolanguage-plugin/configuration-service-api.md) ## Configuration - Dictionary **Dictionary **is only available in the PRO version. Unlock this and other features by upgrading to **Joomill Autolanguage PRO** [Go PRO](https://joomill-templates.com/subscribe/order/product/autolanguage-pro) A solid technical dictionary is a must-have for translating any website. It keeps your terminology consistent and accurate, no matter which language your visitors speak. By sticking to a clear list of terms, you avoid the confusion of messy synonyms or awkward literal translations. This doesn't just look more professional—it also helps both human translators and AI tools work from a single 'source of truth.' In the end, it makes your site easier to use and helps your brand feel reliable all over the world. ### Why Some Terms Are "Sacred" In a technical dictionary, there are terms that should **never** be changed or swapped for synonyms. This is vital for: - **Safety:** In a manual, an 'Emergency Stop' should never be translated simply as a 'Stop Button.' - **Legal Liability:** In contracts or technical specs, a single wrong synonym can lead to a breach of contract. - **User Experience (UX):** If a button in the interface says "Log In," the help text shouldn't refer to it as "Sign In."   You can add unlimited terms to your own dictionary in the Autolanguage plugin. These terms applies to all translation services. ![dictionary 01](https://joomill-templates.com/images/documentation/autolanguage/dictionary-01.png)   [Lees meer...](https://joomill-templates.com/autolanguage-plugin/configuration-dictionary.md) ## Configuration - Articles ![config 01](https://joomill-templates.com/images/documentation/autolanguage/config-02.png) | | | | --- | --- | | Translate Articles | Enable to automatically clone and translate articles when saving. *The plugin only works if the item being saved matches the source language.* | | Active Categories | Limit translation to specific categories. Leave empty to allow all categories. | | Associated Category | If enabled, the plugin attempts to place the translated article in the category associated with the source category for the target language (via Category Associations). If no association exists, the original category is used. | | Associated Tags | If enabled, tags from the source article will be replaced by their translated counterparts (via Tag Associations). If disabled, original tags will be kept. | | Create Associated Links | If enabled, internal links in the content will be automatically updated to the corresponding items in the target language (if associations exist). | | Update Existing Translations | If 'Yes', existing translated items will be overwritten with a new translation when you save the source item. If 'No', only new items are created. | | Translatable Fields | Select which fields should be processed by the translation service. Unselected fields will be copied 1-to-1 and not translated. You can choose from: Title (aliases will be translated also), Text (Intro & Full), Images (Alt & Caption) (images itself won't be translated), Meta Description, Meta Keywords, Note and Custom Fields (Only Text, Textarea and Editor fields will be translated, other fieldtypes will be copied 1-to-1 and not translated) | | Default State for New Translations | Set the publication state for newly created article translations. 'Default' copies the state from the original article. You can choose from: Default (copy from original), Published, Unpublished, Archived, Trashed |   [Lees meer...](https://joomill-templates.com/autolanguage-plugin/configuration-articles.md) ## Configuration - Categories ![config 03](https://joomill-templates.com/images/documentation/autolanguage/config-03.png) | | | | --- | --- | | Translate Categories | Enable to automatically clone and translate categories when saving. *The plugin only works if the item being saved matches the source language.* | | Active Categories | Limit translation to specific categories. Leave empty to allow all categories. | | Update Existing Translations | If 'Yes', existing translated items will be overwritten with a new translation when you save the source item. If 'No', only new items are created. | | Associated Tags | If enabled, tags from the source category will be replaced by their translated counterparts (via Tag Associations). If disabled, original tags will be kept. | | Translatable Fields | Select which fields should be processed by the translation service. Unselected fields will be copied 1-to-1 and not translated. You can choose from: Title (aliases will be translated also), Description, Images (Alt & Caption) (images itself won't be translated), Meta Description, Meta Keywords, Note and Custom Fields (Only Text, Textarea and Editor fields will be translated, other fieldtypes will be copied 1-to-1 and not translated) | | Default State for New Translations | Set the publication state for newly created category translations. 'Default' copies the state from the original category. You can choose from: Default (copy from original), Published, Unpublished, Archived, Trashed |   [Lees meer...](https://joomill-templates.com/autolanguage-plugin/configuration-categories.md) ## Configuration - Menu ![config menu](https://joomill-templates.com/images/documentation/autolanguage/config-04.png) | | | | --- | --- | | Copy Menus | Automatically create translated menu types (e.g. mainmenu-nl -> mainmenu-en) when a menu is saved in Menus > Manage. | | Translate Menu Items | Limit translation to specific categories. Leave empty to allow all categories. | | Update Existing Translations | Enable to automatically clone and translate individual menu items to the correct target menu. | | Update Existing Translations | If 'Yes', existing translated items will be overwritten with a new translation when you save the source item. If 'No', only new items are created. | | Translatable Fields | Select which fields should be processed by the translation service. Unselected fields will be copied 1-to-1 and not translated. You can choose from: Title, Browser PAge Title, Page Heading, Meta Description and Note. | | Default State for New Translations | Set the publication state for newly created menu items translations. 'Default' copies the state from the original menu items. You can choose from: Default (copy from original), Published, Unpublished, Archived, Trashed | [Lees meer...](https://joomill-templates.com/autolanguage-plugin/configuration-menu.md) ## Configuration - Modules ![config modules](https://joomill-templates.com/images/documentation/autolanguage/config-05.png) | | | | --- | --- | | Translate Modules | Enable to automatically clone and translate modules when saving. *The plugin only works if the item being saved matches the source language.* | | Update Existing Translations | If 'Yes', existing translated items will be overwritten with a new translation when you save the source item. If 'No', only new items are created. | | Associated Menu Assignment | If enabled, the plugin attempts to assign the translated module to the translated menu items. | | Update Internal Links | If enabled, internal links (to articles/menus) in Custom HTML modules will be updated to their translated versions. | | Translatable Fields | Select which fields should be processed by the translation service. Unselected fields will be copied 1-to-1 and not translated. You can choose from: Title, Content (only in the Custom HTML modules) and Note. | | Default State for New Translations | Set the publication state for newly created module translations. 'Default' copies the state from the original module. You can choose from: Default (copy from original), Published, Unpublished, Archived, Trashed | [Lees meer...](https://joomill-templates.com/autolanguage-plugin/configuration-modules.md) ## Configuration - Tags ![config tags](https://joomill-templates.com/images/documentation/autolanguage/config-06.png) | | | | --- | --- | | Translate Tags | Enable to automatically clone and translate tags when saving. *The plugin only works if the item being saved matches the source language.* | | Update Existing Translations | If 'Yes', existing translated items will be overwritten with a new translation when you save the source item. If 'No', only new items are created. | | Translatable Fields | Select which fields should be processed by the translation service. Unselected fields will be copied 1-to-1 and not translated. You can choose from: Title, Description, Meta Description and Meta Keywords, Images (Alt & Caption) (The images itself won't be translated) and Note. | | Default State for New Translations | Set the publication state for newly created tag translations. 'Default' copies the state from the original tag You can choose from: Default (copy from original), Published, Unpublished, Archived, Trashed | [Lees meer...](https://joomill-templates.com/autolanguage-plugin/configuration-tags.md) ## Configuration - Mail Templates ![config mailtemplates](https://joomill-templates.com/images/documentation/autolanguage/config-07.png) | | | | --- | --- | | Translate Mail Templates | Enable to automatically clone and translate mail templates when saving in System > Mail Templates. *The plugin only works if the item being saved matches the source language.* | | Update Existing Translations | If 'Yes', existing translated items will be overwritten with a new translation when you save the source item. If 'No', only new items are created. | | Create Associated Links | Create Associated Links If enabled, internal links in the content will be automatically updated to the corresponding items in the target language (if associations exist). | | Translatable Fields | Select which fields should be processed by the translation service. Unselected fields will be copied 1-to-1 and not translated. You can choose from: Subject, Body (Text) and Body (HTML) | [Lees meer...](https://joomill-templates.com/autolanguage-plugin/configuration-mail-templates.md) ## Google Cloud Translation API Key Follow these steps to create and secure an API key for use in Joomla or other translation applications. ### Step 1: Create a New Project 1. Go to the [Google Cloud Console](https://console.cloud.google.com/). 2. Log in with your Google account. 3. Click the **Project Dropdown** in the top-left corner (next to the Google Cloud logo). ![google api 01](https://joomill-templates.com/images/documentation/autolanguage/google-api-01.png) 4. Click **New Project** in the top-right of the pop-up window.![google api 02](https://joomill-templates.com/images/documentation/autolanguage/google-api-02.png) 5. Enter a name (e.g., `Joomla-Auto-Translate`) and click **Create**. ![google api 03](https://joomill-templates.com/images/documentation/autolanguage/google-api-03.png) 6. **Important:** Ensure the new project is selected in the dropdown menu before proceeding. ![google api 04](https://joomill-templates.com/images/documentation/autolanguage/google-api-04.png) --- ### Step 2: Set Up Billing (Required) Google requires a linked credit card or bank account to activate APIs, even if you stay within the "Free Tier" limits. 1. Open the main menu (≡) in the top-left corner and select **Billing**. ![google api 05](https://joomill-templates.com/images/documentation/autolanguage/google-api-05.png) 2. Click **Link a billing account** or **Manage billing accounts**. 3. Follow the prompts to enter your payment information. --- ### Step 3: Enable the Translation API The API key won't work unless the specific "Cloud Translation" service is turned on. 1. In the top search bar, type: **"Cloud Translation API"**. ![google api 06](https://joomill-templates.com/images/documentation/autolanguage/google-api-06.png) 2. Select the result under "Marketplace" or "APIs". 3. Click the blue **Enable** button. ![google api 06](https://joomill-templates.com/images/documentation/autolanguage/google-api-07.png) --- ### Step 4: Create Your API Key 1. Navigate to **APIs & Services** > **Credentials** via the sidebar menu (≡). 2. Click **+ CREATE CREDENTIALS** at the top and select **API key**. ![google api 08](https://joomill-templates.com/images/documentation/autolanguage/google-api-08.png) 3. A pop-up will appear with your key (starting with `AIza...`). Copy this key for later use. ![google api 09](https://joomill-templates.com/images/documentation/autolanguage/google-api-09.png) --- ### Step 5: Secure Your Key (Highly Recommended) To prevent unauthorized use and unexpected costs, you must restrict your key. 1. In the Credentials list, click the **Name** of the key you just created. ![google api 10](https://joomill-templates.com/images/documentation/autolanguage/google-api-10.png) 2. Under **API restrictions**, select **Restrict key**. 3. Click the "Select APIs" dropdown, search for **Cloud Translation API**, and check the box. ![google api 11](https://joomill-templates.com/images/documentation/autolanguage/google-api-11.png) 4. Click **OK**, then click **Save**. > **[Visual: Screenshot showing the "Restrict key" radio button and the API selection dropdown]** --- ### Step 6: Integration in Joomla 1. Log in to your Joomla Backend. 2. Navigate to **Plugins** > **System - Autolanguage**. 3. Open the **Service & API** tab. 4. Select Google Translate API  5. Paste your key into the **Google API Key** field. ![google api 12](https://joomill-templates.com/images/documentation/autolanguage/google-api-12.png) 6. **Save & Close**. --- ### Usage & Costs at a Glance | **Usage Volume** | **Estimated Cost** | | --- | --- | | First 500,000 characters / month | **Free** | | Every 1 million characters after | ~$20.00 | [Lees meer...](https://joomill-templates.com/autolanguage-plugin/google-cloud-translation-api-key.md) ## Google Gemini API Key **Google Gemini** is only available in the PRO version. Unlock this and other features by upgrading to **Joomill Autolanguage PRO** [Go PRO](https://joomill-templates.com/subscribe/order/product/autolanguage-pro) Follow these steps to create and secure an API key for use in Joomla or other translation applications. ### Step 1: Create a New Project 1. Go to the [Google AI Studio](https://aistudio.google.com/api-keys). 2. Log in with your Google account. 3. Click the **Get API Key** in the bottom-left corner ![google ai studio](https://joomill-templates.com/images/documentation/autolanguage/google-ai-studio.png) 4. Click **Create API key** in the top-right. ![google ai studio button](https://joomill-templates.com/images/documentation/autolanguage/google-ai-studio-button.png) 5. Enter a name (e.g., `Joomla-Auto-Translate`), select or create a project and click **Create**. ![google ai studio key](https://joomill-templates.com/images/documentation/autolanguage/google-ai-studio-key.png) 6. Copy the API Key ![google ai studio copy key](https://joomill-templates.com/images/documentation/autolanguage/google-ai-studio-copy-key.png) --- ### Step 2: Integration in Joomla 1. Log in to your Joomla Backend. 2. Navigate to **Plugins** > **System - Autolanguage**. 3. Open the **Service & API** tab. 4. Select Google Gemini  5. Paste your key into the **Google API Key** field. ![google api 12](https://joomill-templates.com/images/documentation/autolanguage/google-api-12.png) 6. **Save & Close**. [Lees meer...](https://joomill-templates.com/autolanguage-plugin/google-gemini-api-key.md) ## Microsoft Azure Translator API Key Obtaining a Microsoft Azure API Key is slightly more complex than other services because of the extensive Azure interface. However, it is highly rewarding, as the **Free F0 Tier** allows you to translate up to **2 million characters per month for free**. --- ## Step 1: Account and Login 1. Navigate to the [Azure Portal](https://portal.azure.com/). 2. Log in with your **Microsoft account** (Outlook, Hotmail, Live, etc.) or create a new one. 3. **Note:** You must have an active **Subscription**. If you are new, you can sign up for a free account. Like Google Cloud, Microsoft requires a credit card or debit card for identity verification, even for the free usage tier. --- ## Step 2: Create the Translator Resource 1. In the Azure Portal, click **+ Create a resource** in the top-left corner. ![microsoft api 01](https://joomill-templates.com/images/documentation/autolanguage/microsoft-api-01.png) 2. In the search bar, type: `Translator`. 3. Select the result titled **Translator** (published by Microsoft). ![microsoft api 02](https://joomill-templates.com/images/documentation/autolanguage/microsoft-api-02.png) --- ## Step 3: Configure Project Details Fill out the form with the following details: - **Subscription:** Select your subscription (e.g., "Pay-As-You-Go" or "Azure subscription 1"). - **Resource Group:** Click **Create new** and give it a name, such as `JoomlaTranslation`. ![microsoft api 03](https://joomill-templates.com/images/documentation/autolanguage/microsoft-api-03.png) - **Region:** This is a crucial setting. - Choose **Global** for the simplest setup (standard for most plugins). - Choose a specific region (e.g., **West Europe**) if your data must remain within a specific territory for GDPR compliance. - *Note: Remember your choice; you will need to enter this in your plugin settings later.* - **Name:** Enter a unique name, like `MySite-Translator`. ![microsoft api 04](https://joomill-templates.com/images/documentation/autolanguage/microsoft-api-04.png) - **Pricing Tier:** - Select **Free F0 (Up to 2M characters...)**. - *Note: If you don't see F0, you may already have a free resource elsewhere. Azure allows only one F0 Translator resource per account.* Click **Review + create** at the bottom, then click **Create**. --- ## Step 4: Retrieve the API Key 1. Wait for the deployment to finish (usually about 30 seconds). 2. Click the **Go to resource** button once it appears. 3. In the left-hand menu, look under the **Resource Management** section. 4. Click on **Keys and Endpoint**. ![microsoft api 05](https://joomill-templates.com/images/documentation/autolanguage/microsoft-api-05.png) 5. You will see **Key 1** and **Key 2**. You can use either one. 6. Copy **Key 1**. --- ## Step 5: Configure in Joomla 1. Log in to the backend of your **Joomla site**. 2. Open the plugin: **System - Autolanguage**. 3. Go to the **Service & API** tab and Choose Microsoft Azure API. 4. **Microsoft API Key:** Paste the key you copied in Step 4. 5. **Region:** - If you chose **Global** in Step 3, enter `global` or leave it blank (depending on the plugin requirements). - If you chose **West Europe**, enter `westeurope` (lowercase, no spaces). - *Tip: You can find the exact "Region code" in the Azure portal on the "Keys and Endpoint" screen under "Location".* ![microsoft api 06](https://joomill-templates.com/images/documentation/autolanguage/microsoft-api-06.png) [Lees meer...](https://joomill-templates.com/autolanguage-plugin/microsoft-azure-translator-api-key.md) ## DeepL API Key **Deepl** is only available in the PRO version. Unlock this and other features by upgrading to **Joomill Autolanguage PRO** [Go PRO](https://joomill-templates.com/subscribe/order/product/autolanguage-pro) Getting a DeepL API key is a straightforward process. However, it is important to distinguish between the **DeepL API** (for software/code integration) and the **DeepL Pro** subscription (for manual translation via the website or app). ## Step 1: Choose the Right Plan First, determine which version suits your needs. Note that even the Free tier requires a payment method for identity verification. | **Feature** | **DeepL API Free** | **DeepL API Pro** | | --- | --- | --- | | **Cost** | Free (€0/month) | €4.99/month + usage costs | | **Limit** | Max. 500,000 characters/month | Unlimited (pay-per-character) | | **Data Privacy** | Texts may be used to train models. | **Maximum security:** Texts are never stored. | | **Best For** | Hobby projects, testing, low-traffic sites. | Businesses, confidential data, high volumes. | --- ## Step 2: Create Your Account 1. Visit the official DeepL API page: [https://www.deepl.com/](https://www.deepl.com/) 2. You will see two columns: **DeepL API Free** and **DeepL API Pro**. 3. Click **"Sign up for free"** (for the Free tier) or **"Buy now"** (for the Pro tier). --- ## Step 3: Registration and Verification *This is the stage where most users encounter issues. Please follow closely:* 1. **Account Setup:** Enter your email address and create a password (or log in if you already have a standard account). 2. **Contact Information:** Fill in your name and address details. 3. **Identity Verification (Crucial):** - **Credit Card Requirement:** Even for the **Free API**, DeepL requires a valid credit card (Visa, Mastercard, Amex, etc.). - **Why?** This prevents bot abuse and multiple account creation. You will **not** be charged on the Free plan unless you manually upgrade. - **No Credit Card?** Currently, it is nearly impossible to obtain a key without a credit card or a bank account that supports SEPA direct debit (available only in specific regions). --- ## Step 4: Locate Your API Key Once your registration is complete, your key is generated immediately. 1. Ensure you are logged in at [deepl.com](https://www.deepl.com/). 2. Click on your profile icon/name in the top-right corner and select **Account**. ![deepl api 01](https://joomill-templates.com/images/documentation/autolanguage/deepl-api-01.png) 3. In the top menu click on** API keys & limits ![deepl api 02](https://joomill-templates.com/images/documentation/autolanguage/deepl-api-02.png)** 4. Click on the blue button **"Create Key"**. ![deepl api 03](https://joomill-templates.com/images/documentation/autolanguage/deepl-api-03.png) 5. Give your Key a name and Save 6. You will see a long string of characters (e.g., `f63c02c5-....:fx`). Copy this key. Tip: If your key ends with :fx, it confirms you are on the Free tier. Pro keys do not have this suffix. ## Step 5: Integration in Joomla 1. Log in to your Joomla Backend. 2. Navigate to **Plugins** > **System - Autolanguage**. 3. Open the **Service & API** tab. 4. Select Deepl API  5. Paste your key into the **Deepl API Key** field. ![deepl api 04](https://joomill-templates.com/images/documentation/autolanguage/deepl-api-04.png) 6. **Save**. 7. After you have save the API key, you can see the API Usage and Status in the plugin ![deepl api 05](https://joomill-templates.com/images/documentation/autolanguage/deepl-api-05.png) [Lees meer...](https://joomill-templates.com/autolanguage-plugin/deepl-api-key.md) ## Deepl configuration **Deepl** is only available in the PRO version. Unlock this and other features by upgrading to **Joomill Autolanguage PRO** [Go PRO](https://joomill-templates.com/subscribe/order/product/autolanguage-pro) | | | | --- | --- | | DeepL API Key | Enter your DeepL Authentication Key (ending in :fx for Free accounts). [Read how to get your Deepl API Key here](https://joomill-templates.com/index.php?option=com_content&view=article&id=311:deepl-api-key&catid=105:autolanguage-plugin&Itemid=5374). | | Glossary ID | Optional: The ID of a specific DeepL Glossary to apply. A Glossary is a list of specific terms you have defined in your DeepL account. It ensures that a specific word is *always* translated in a certain way, regardless of context. *Example:* Your company always refers to a "client" as a "partner". By using a Glossary, DeepL will never use the word "client," but will consistently use "partner," ensuring brand consistency across all translated articles. [Read more on Deepl](https://support.deepl.com/hc/en-us/articles/360021634540-About-the-glossary) | | Formality | This option determines the tone of the address (e.g., formal "you" vs. informal "you"). This is particularly important for languages such as German, French, and Spanish. - **Default (Without Formality):** The AI automatically chooses the most likely tone based on context. Source (EN): "Can you send me the document?" Translation (DE): "Kannst du mir das Dokument schicken?" (May vary). - **Formal (**`prefer_more`**):** Uses polite forms of address. Translation (DE): "Können **Sie** mir das Dokument schicken?". - **Informal (**`prefer_less`**):** Uses friendly or casual forms of address. Translation (DE): "Kannst **du** mir das Dokument schicken?". | | Deepl Usage | Deepl shows you the API Usage & Status in the plugin configuration ![deepl api 05](https://joomill-templates.com/images/documentation/autolanguage/deepl-api-05.png) And shows you the remaining credits after each translation ![deepl usage 2](https://joomill-templates.com/images/documentation/autolanguage/deepl-usage-2.png) | ## Disable translation of elements To prevent the translation of elements in the HTML structure, the translation engine respects the `translate="no"` and `class="notranslate"` attributes. In the following example, the attribute is used to prevent translation of the paragraph: `

My first paragraph.

` [Lees meer...](https://joomill-templates.com/autolanguage-plugin/deepl-configuration.md) ## OpenAI API Key Getting an OpenAI API key allows you to integrate models like GPT-4 into this plugin. The process involves creating an account, setting up billing, and generating a key. ## Step 1: Create an OpenAI Account - Go to the [OpenAI Platform website](https://platform.openai.com/). - Click Sign up to create an account, or log in if you already have one. *Note: A regular ChatGPT subscription does not automatically give you API access; they are separate billing systems* ## Step 2: Access the API Dashboard - Once logged in, you will be in the OpenAI Platform dashboard. - Navigate to the**API keys**section on the left sidebar, or go directly to [platform.openai.com/api-keys](https://platform.openai.com/api-keys). ![openai api 01](https://joomill-templates.com/images/documentation/autolanguage/openai-api-01.png) - Click the**"+ Create new secret key"**button. - Give your key a name (optional, but helpful for identifying it later, e.g., "Development Key"). - Select the Project if prompted. - Click**Create secret key** - Please save your secret key in a safe place since **you won't be able to view it again**. ## Step 3: Integration in Joomla - Log in to your Joomla Backend. - Navigate to **Plugins** > **System - Autolanguage**. - Open the **Service & API**tab. - Select OpenAI (ChatGPT) API - Paste your key into the **OpenAI****API Key** field. ![openai api 02](https://joomill-templates.com/images/documentation/autolanguage/openai-api-02.png) - **Save**. - After you have save the API key, you can select the model you like to use. You can see the pricing of the models: [https://openai.com/nl-NL/api/pricing/](https://openai.com/nl-NL/api/pricing/) [Lees meer...](https://joomill-templates.com/autolanguage-plugin/openai-api-key.md) ## Anthropic API Key **Anthropic (Claude)**is only available in the PRO version. Unlock this and other features by upgrading to **Joomill Autolanguage PRO** [Go PRO](https://joomill-templates.com/subscribe/order/product/autolanguage-pro) Getting an Anthropic API key allows you to integrate models like Haiku, Opus or Sonnet  into this plugin. The process involves creating an account, setting up billing, and generating a key. ## Step 1: Create an Anthropic Account - Go to the [Anthropic Platform website](https://console.anthropic.com/). - Click Sign up to create an account, or log in if you already have one. *Note: a paid Claude subscription (Pro, Max, Team, or Enterprise plans) does not automatically give you API access; they are separate billing systems. Read more about this: [https://support.claude.com/en/articles/9876003-i-have-a-paid-claude-subscription-pro-max-team-or-enterprise-plans-why-do-i-have-to-pay-separately-to-use-the-claude-api-and-console](https://support.claude.com/en/articles/9876003-i-have-a-paid-claude-subscription-pro-max-team-or-enterprise-plans-why-do-i-have-to-pay-separately-to-use-the-claude-api-and-console)* ## Step 2. Set Up Your Workspace Anthropic organizes projects into **Workspaces**. This allows you to manage different teams or billing environments separately. - Verify which workspace you are in by checking the dropdown menu at the top of the screen. - The default workspace is usually titled "Default". ## Step 3: Access the API Dashboard - Once logged in, you will be in the Platform dashboard. - Navigate to the **API keys **section on the left sidebar, or go directly to [https://platform.claude.com/settings/keys](https://platform.claude.com/settings/keys) ![anthropic console](https://joomill-templates.com/images/documentation/autolanguage/anthropic-console.png) - Click the**"+ Create key"**button. - Select a Workspace and Give your key a name  - Click** Add** - Please save your secret key in a safe place since **you won't be able to view it again**. ## Step 4: Integration in Joomla - Log in to your Joomla Backend. - Navigate to **Plugins** > **System - Autolanguage**. - Open the **Service & API **tab. - Select Anthropic (Claude) - Paste your key into the **Anthropic ****API Key** field. ![anthropic key](https://joomill-templates.com/images/documentation/autolanguage/anthropic-key.png) - **Save**. - After you have save the API key, you can select the model you like to use. You can see the pricing of the models: [https://platform.claude.com/docs/en/about-claude/pricing](https://platform.claude.com/docs/en/about-claude/pricing) ## Known Issues: *Your credit balance is too low to access the Anthropic API. Please go to Plans & Billing to upgrade or purchase credits.* If you still encounter this error after topping up your account, the system may not have refreshed your existing keys. To resolve this, go to **Plans & Billing**, ensure your credits are added, then **delete your old API keys** and generate a **new one**. Using this new key should immediately restore your access.   [Lees meer...](https://joomill-templates.com/autolanguage-plugin/anthropic-api-key.md) ## xAI / Grok API Key **xAI / Grok **is only available in the PRO version. Unlock this and other features by upgrading to **Joomill Autolanguage PRO** [Go PRO](https://joomill-templates.com/subscribe/order/product/autolanguage-pro) Follow these steps to create and secure an API key for use in Joomla or other translation applications. ### Step 1: Create a New Project 1. Go to the [xAI Console](https://console.x.ai/). 2. Click the **API Keys** in the left menu ![xai 01](https://joomill-templates.com/images/documentation/autolanguage/xai-01.png) 3. Click **Create API key** in the top-right. ![xai 02](https://joomill-templates.com/images/documentation/autolanguage/xai-02.png) 4. Enter a name (e.g., `Joomla-Auto-Translate`), Restrict acces and Rate limits to your needs and click **Create API Key** ![xai 03](https://joomill-templates.com/images/documentation/autolanguage/xai-03.png) 5. Copy the API Key --- ### Step 2: Integration in Joomla 1. Log in to your Joomla Backend. 2. Navigate to **Plugins** > **System - Autolanguage**. 3. Open the **Service & API** tab. 4. Select xAI (Grok) 5. Paste your key into the **xAI (Grok) ****API Key** field. ![google api 12](https://joomill-templates.com/images/documentation/autolanguage/google-api-12.png) 6. **Save & Close**. [Lees meer...](https://joomill-templates.com/autolanguage-plugin/xai-grok-api-key.md) ## Mistral API Key Mistral AI offers a free experimental tier that allows you to test their models via API without immediate costs. Follow these steps to get your key. ### 1. Create your Account - Go to the [Mistral AI Console](https://console.mistral.ai/). - Sign up using your email, Google, or GitHub account. - Once logged in, you will be prompted to set up a **Workspace**. Give it a name (e.g., "MyLab") and accept the terms of service. ### 2. Activate the Free "Experiment" Plan Mistral requires you to select a plan to enable the API, but they offer a free tier for testing. - In the left-hand sidebar, click on **Billing** or **Limits**. - Look for the **"Experiment"** plan (often labeled as the Free or Experimental tier). - Click **Subscribe** or **Select**. - **Note:** You will likely be asked to verify your **phone number** via SMS. This is a security measure to prevent bot abuse of the free tier. ### 3. Generate your API Key Once your plan is active: - Navigate to the **API Keys** section in the left sidebar. - Click the orange **"Create new key"** button. ![mistral 01](https://joomill-templates.com/images/documentation/autolanguage/mistral-01.png) - Give your key a name (e.g., "Test-Key") so you can identify it later. - Click **Create key**. ### 4. Secure your Key **Copy the key immediately.** Mistral will only show the full string once for security reasons. If you close the window, you cannot see it again and will have to generate a new one.   --- ### 5. Integration in Joomla 1. Log in to your Joomla Backend. 2. Navigate to **Plugins** > **System - Autolanguage**. 3. Open the **Service & API** tab. 4. Select Mistral AI 5. Paste your key into the **Mistral API** **Key** field and click Save 6. Select your Model ![google api 12](https://joomill-templates.com/images/documentation/autolanguage/google-api-12.png) 7. **Save & Close**. [Lees meer...](https://joomill-templates.com/autolanguage-plugin/mistral-api-key.md) ## YOOtheme Pro Builder Support **YOOtheme Builder pages** are only available in the PRO version. Unlock this and other features by upgrading to **Joomill Autolanguage PRO** [Go PRO](https://joomill-templates.com/subscribe/order/product/autolanguage-pro) **How YOOtheme Pro Page Builder Translation Works**If you build your Joomla articles or pages using **YOOtheme Pro's page builder**, your content is not stored as plain HTML — it is stored as **JSON data** embedded inside the article. This means a standard translation plugin would copy that JSON across as-is, leaving all your texts untranslated. **Autolanguage PRO handles this automatically.** When translating a YOOtheme Pro page, the plugin reads the JSON structure, identifies all translatable text fields inside it, sends only those texts to your chosen translation engine, and then writes the translated content back into a perfectly intact JSON structure. Your **layout, styling, images and element settings remain completely unchanged** — only the text is translated. ⚠️ Important: YOOtheme Pro translation requires** Mode 1: Batch Translate** to be active. The Translate upon Save mode does not support YOOtheme Pro builder content. Make sure you have selected Batch Translate mode in the plugin settings before translating YOOtheme Pro pages. --- ### How to translate a YOOtheme Pro page 1. Go to **Content → Articles** in your Joomla back end 2. Select one or more articles built with YOOtheme Pro 3. Click **Actions → Translate** in the toolbar 4. Autolanguage PRO will detect the YOOtheme content and translate all supported fields automatically --- ### Supported YOOtheme Pro fields The following built-in YOOtheme Pro element fields & ZOOLanders Essential Addons fields are currently supported for translation: title meta content image_alt link_aria_label link_text tags message author footer label home_text scale_x_title_text scale_y_title_text subtitle_text title_text dataset_label metadata email_subject email_body shared_text shared_url control_name control_error_message text Need support for a 3rd party element? Are you using a **third-party YOOtheme Pro add-on** or a custom element with fields that are not being translated? No problem — every add-on can define its own custom field names. **Just send me an email** with the name of the add-on and, if possible, an example of the JSON output it produces. I will add support for those fields in an upcoming update. [Lees meer...](https://joomill-templates.com/autolanguage-plugin/yootheme-pro-builder-support.md) ## Changelog [changelog-autolanguage] [Lees meer...](https://joomill-templates.com/autolanguage-plugin/changelog.md)