---
title: "FAQ"
manual: "DeepL Translate (CORE)"
version: "main"
permalink: "https://docs.typo3.org/permalink/web-vision/deepltranslate-core:faq@main"
source: "Faq/Index.rst"
rendered: "2026-10-06T14:40:53+00:00"
---

# FAQ {#faq}

## My dropdown in the site configuration is empty {#my-dropdown-in-the-site-configuration-is-empty}

This happens if TYPO3 cached the request from the DeepL API for allowed languages,
but no API key was provided. In this case, empty your system cache in TYPO3.
Normally no cache files should be created when no API key is provided.

If this step does not work, delete the cached files manually. The location is as follows:

**composer mode installation**

`var/cache/data/deepltranslate_core`

**classic mode installation**

`typo3temp/var/cache/data/deepltranslate_core`

After deleting the files in this directory and going to Site Configuration, the
extension will reload the cache and the dropdown should have all the translatable
language keys.

## Fields of a Content Block are not translated {#fields-of-a-content-block-are-not-translated}

DeepL translates only fields with `l10n_mode` set to `prefixLangTitle`.
Content Blocks does not set it, add `l10n_mode: prefixLangTitle` to the
fields in the YAML definition, the fields of a `Collection` included. See
[Content Blocks](https://docs.typo3.org/permalink/web-vision/deepltranslate-core:tableconfigurationcontentblocks@main).

## What will be the cost for DeepL API subscription? {#what-will-be-the-cost-for-deepl-api-subscription}

You can find all the details regarding the usage of the DeepL API here:

-   [https://www.deepl.com/pro-pricing.html](https://www.deepl.com/pro-pricing.html)