TTS Workbench

TTS Workbench is a self-hosted, multi-engine text-to-speech platform that gives homelab users one local Gradio workflow for Kokoro narration, F5-TTS voice…

  • AI
  • Other
TTS Workbench is a self-hosted, multi-engine text-to-speech platform that gives homelab users one local Gradio workflow for Kokoro narration, F5-TTS voice cloning, Qwen3-TTS generation, and compatible Intel Arc GPU acceleration.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

43/100 Fair

Maintained
66last commit 95 days ago
Popular
123 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 26 days ago

GitHub stars
3
Open issues
0
Last commit
2026-08-18
License
MIT
Activity
stale

Checked 8 days ago - source: GitHub (heroeswearkapes/tts-workbench)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Map Docker port 2525 for Jupyter If you use the Docker prep script, Jupyter Notebook (a web notebook for choosing speakers) listens on port 2525 and is configured for all network interfaces; map that port in Docker and keep it off the public internet unless protected. Without the port mapped, the container can run but you won't be able to open the speaker-selection page in your browser. source
  • Point training at your GPU IDs When training GlowTTS or HiFiGAN, set CUDA_VISIBLE_DEVICES to the GPU numbers you want to use, for example 0 for the first NVIDIA GPU. If you leave it unset or choose a missing GPU, training may use the wrong device or fail to start on your GPU. source
  • Keep config and model files findable Fine-tuning needs a config file and a pre-trained model file (the starting voice model), often stored in your local TTS models folder under your home directory; keep those files where the command's paths point. If the files are renamed or moved, fine-tuning can't start. source
  • First Use Models load only when first used, so allow time for the initial load and keep local storage for generated audio and metadata. source

Fetched 2 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does TTS-Workbench send my text or reference audio to an external service?

No. It is designed to make engines usable through a consistent workflow without sending text or references.

How do I access the TTS-Workbench UI?

It provides one local Gradio interface for narration, voice cloning, and emerging TTS models.

Does TTS-Workbench support voice cloning?

Yes. Its local Gradio interface includes voice cloning along with narration and emerging TTS models.

How does TTS-Workbench handle TTS engines with very different controls?

It makes engines with very different controls and runtime requirements usable through a consistent workflow.

Answers sourced from ca.unraid.net, github.com, github.com

Community

Collected 48 days ago - public community threads