← All models

PlayHT

Retired

PlayHT has 1 model tracked on Modelglass across 1 vertical (Audio), most recently added 2023-07.

PlayHT has 1 audio model (1 retired) on Modelglass, most recently added 2023-07.

play.ht ↗

Coverage across verticals

Audio 1 model

1 retired

Audio pricing page ↗

PlayHT (rebranded "PlayAI") was acquired by Meta in July 2025 and the service was fully shut down December 31, 2025 — all user accounts, audio files, and voice clones were permanently deleted with no export tooling provided. Independently verified against Bloomberg (https://www.bloomberg.com/news/articles/2025-07-11/meta-acquires-voice-ai-startup-playai-continuing-to-add-talent), TechCrunch (https://techcrunch.com/2025/07/13/meta-acquires-voice-startup-play-ai/), and Cooley, the deal's law firm (https://www.cooley.com/news/coverage/2025/2025-07-15-play-ai-acquired-by-meta), plus multiple independent shutdown-timeline writeups (verified 2026-07-17). `url` and `pricing_page` above are kept for historical reference only — neither reflects a live, purchasable product. The description below (plans, pricing) is retained as a historical record of what PlayHT offered before the shutdown, not a current offering. --- Historical (pre-shutdown) description --- PlayHT offered ultra-realistic TTS via subscription plans (Hobby, Creator, Unlimited) and a pay-as-you-go API. The PlayHT 2.0 model was their highest-quality voice model with strong emotion expressiveness and voice cloning from a 3-second sample. API access was available from the Creator plan (~$49/month).

Release cadence

1 model tracked across all verticals. Earliest release 2023-07, most recent 2023-07.

Derived from Modelglass's per-vertical provider registries — image/llm/video/audio's registry/providers/*.yaml records, plus science/coding/agentic/gdpval's benchmark registries, where a provider is identified by the prefix before "/" in each model's model_id rather than a registry record of its own. Where the same company uses a different provider slug or model_id prefix across verticals (e.g. Google DeepMind vs. Google Cloud, or Qwen's "alibaba" model_id prefix in the coding registry vs. its "qwen" provider slug elsewhere), coverage is merged onto a single profile per an explicit, human-reviewed alias list (registry/provider-aliases.yaml) — everything else reflects exact-slug or exact-prefix matches only.