Why Are STT/TTS Features Missing in Locally Deployed Dify 1.11.4?

[Zzzz-Jonathan]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

Content

In the locally deployed Dify version 1.11.4, I can’t find the “Speech-to-Text” and “Text-to-Speech” features on the Features page.

However, the online Dify of the same version does have these features. Could you please advise what might be causing this issue?

[dosubot[bot]]

Hi @Zzzz-Jonathan! I'm Dosu and I’m helping the dify team.

The STT (Speech-to-Text) and TTS (Text-to-Speech) features are missing in your local Dify 1.11.4 deployment because, by default, these features are disabled unless explicitly enabled and properly configured. In the codebase, both features are set to enabled: false by default, so they won't appear in the UI unless the backend or system settings update their state to enabled (source).

For these features to show up and work locally, you need to:

• Configure and enable speech-to-text and text-to-speech providers in your system settings. If no provider or model is set up for these features, they remain hidden (source).
• Make sure your provider supports audio endpoints. For example, some self-hosted models (like Gemini) do not expose audio features, so STT/TTS will not be available even if Dify supports them (source).
• If you use plugins or external services (like ChatTTS or Xorbits Inference for TTS), ensure they are correctly configured and that all required parameters (such as "Voice") are set. There are known mismatches between frontend and backend validation for these parameters that can cause issues (source).
• Double-check your Docker and environment variable setup. Missing or misconfigured environment variables, or incorrect port mappings, can prevent features from working or appearing in the UI (source).

If you’ve configured everything and the features are still missing, check your backend logs for errors or warnings related to STT/TTS. This can help pinpoint missing configuration or provider issues.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}