--- title: "Basic Usage TYPO3 v14" manual: "DeepL Translate (CORE)" version: "main" permalink: "https://docs.typo3.org/permalink/web-vision/deepltranslate-core:basic-usage@main" source: "Editor/Usage/Index.rst" rendered: "2026-10-06T14:40:53+00:00" --- # Basic Usage TYPO3 v14 {#basic-usage} Once the extension is installed and the API key provided, we are ready to start translating pages, content elements and/or records. - [Translate Page with or without contents elements](https://docs.typo3.org/permalink/web-vision/deepltranslate-core:translatepagewithorwithoutcontents@main) - [Translate Content Elements](https://docs.typo3.org/permalink/web-vision/deepltranslate-core:translatecontentelements@main) - [Translate Record](https://docs.typo3.org/permalink/web-vision/deepltranslate-core:translaterecord@main) - [Translate inline records](https://docs.typo3.org/permalink/web-vision/deepltranslate-core:translateinlinerecords@main) > [!NOTE] > TYPO3 v14 revamped the overall localization process looking different and > also working in a different way then in TYPO3 v13. > > - See [TYPO3 v13 Basic Usage](https://docs.typo3.org/permalink/web-vision/deepltranslate-core:basicusagetypo3v13@main) if you are on TYPO3 v13. ## Translate Page with or without contents elements {#translatepagewithorwithoutcontents} **deepltranslate-core** respects the new translation workflow and shares the same wizard provided by TYPO3 v14, which means that translating a page and optional directly the contents are started using the generic translation dropdown. 1. Generic translation dropdown to create translation ![Generic translation dropdown to create translation](../../Images/Editor/page-translation-dropdown-create-translation.png) 1. Select content elements to translate ![Select content elements to translate](../../Images/Editor/page-translation-wizard-content-selection.png) 1. Select **Translate** localization mode ![Select \`Translate\` localization mode](../../Images/Editor/page-translation-wizard-select-localization-mode.png) > [!NOTE] > DeepL based translation is only available for **Translate** > localization mode and will not be available if **Copy** > localization mode is selected here. 1. Select `Translate with DeepL` localization handler ![Select \`Translate with DeepL\` localization handler](../../Images/Editor/page-translation-wizard-select-translate-localization-handler.png) 1. Review and confirm selected localization options ![Review and confirm selected localization options](../../Images/Editor/page-translation-wizard-translation-confirmation.png) 1. Localization is in progress ![Localization is in progress](../../Images/Editor/page-translation-wizard-processingdata.png) 1. Localization completed successfully ![Localization completed successfully](../../Images/Editor/page-translation-wizard-localization-completed.png) ## Translate Content Elements {#translatecontentelements} Once the extension is installed and the API key provided, we are ready to start translating content elements. When translating a content element, there are four additional options besides the normal translate and copy. - DeepL Translate (auto detect). - DeepL Translate. 1. Start translate of missing records for language ![Start translate of missing records for language](../../Images/Editor/content-translation-translate-button.png) 1. Select source language ![Select source language](../../Images/Editor/content-translation-wizard-select-source-language.png) 1. Select content elements to translate ![Select content elements to translate](../../Images/Editor/content-translation-wizard-select-content-elements-to-translate.png) 1. Select **Translate** localization mode ![Select Translate localization mode](../../Images/Editor/content-translation-wizard-select-localization-mode.png) 1. Select `Translate with DeepL` localization handler ![Select \`Translate with DeepL\` localization handler](../../Images/Editor/content-translation-wizard-select-translate-localization-handler.png) 1. Review and confirm selected localization options ![Review and confirm selected localization options](../../Images/Editor/content-translation-wizard-translation-confirmation.png) 1. Localization is in progress ![Localization is in progress](../../Images/Editor/content-translation-wizard-processingdata.png) 1. Localization completed successfully ![Localization completed successfully](../../Images/Editor/content-translation-wizard-localization-completed.png) ## Translate Record {#translaterecord} In list view, you are able to translate single elements by clicking the DeepL translate button for the language you want. > [!NOTE] > In TYPO3 v13 extra `localize to` action are provided and not available in > case no `DeepL` translation configured for a language. In TYPO3 v14 the > action is always available and in case the selected language does not have > a valid `DeepL` translation the `Translate with DeepL` localization handler > will not show up. > [!WARNING] > **Attention** > > Fields of custom extensions need to be properly > [configured in TCA](https://docs.typo3.org/permalink/web-vision/deepltranslate-core:tableconfiguration@main) to enable translation. 1. Start localization for a record with **Localize to** in the **Records Module** ![Start localization for a record with \`Localize to\` in the \`Records Module\`](../../Images/Editor/record-translation-localizetobutton.png) > [!NOTE] > The process is the same as already visually demonstrated above. Dedicated > images will be added in the next extension release. ## Translate inline records {#translateinlinerecords} Inline records are records edited inside another record, for example the items of a card group or an accordion. Their translation belongs to the translation of the record they are part of, so they are translated together with it. When an inline record is added in the default language after the record it belongs to has already been translated, open the translated record. The new inline record is listed there as not yet localized, with a DeepL icon in its controls. Its tooltip says **Translate with DeepL**. 1. Click the DeepL icon **Translate with DeepL** in the controls of the inline record. ![The DeepL icon in the controls of an inline record which is not translated yet](../../Images/Editor/inline-record-translate-with-deepl-control.png) 1. The localization wizard of TYPO3 opens for the inline record. Keep the mode **Translate** and click **Next**. 1. **Manual Translation** is preselected as handler. Select **Translate with DeepL** instead and click **Next**. ![The handler step of the localization wizard with Manual Translation preselected](../../Images/Editor/inline-record-translation-wizard-select-handler.png) 1. Check the summary and click **Localize**. 1. When the wizard reports **Localization completed**, click **Finish**. The edit form of the translated record opens again and shows the translated inline record. If the form has unsaved changes, TYPO3 asks whether to save or discard them first. In TYPO3 v13 the icon asks for confirmation and translates the inline record directly, see [Basic Usage TYPO3 v13](https://docs.typo3.org/permalink/web-vision/deepltranslate-core:basicusagetypo3v13@main). The icon is only shown when - the inline field shows records which are not translated yet, an integrator setting (ask your integrator if new inline records do not appear in the translated record), - DeepL is configured for the language of the translated record, and you are allowed to translate with DeepL and to edit the inline records, - the localize button of TYPO3 is shown for the inline record, and - the inline record is stored with a reference to the record it belongs to, which is the usual configuration. Inline fields that store a list of records do not get the icon, and neither do files (images, media). > [!NOTE] > The localize buttons of TYPO3 itself, including > **Localize all records** and > **Synchronize with original language**, copy the content without > translating it.