Skip to content

Play.ht alternative

Play.ht alternative
(after the shutdown).

Meta acquired the PlayAI team in July 2025 and Play.ht shut the service down on 31 December 2025. Audexum is the drop-in replacement: 43 voices, 32 languages, €29/mo, same REST shape.

The short version.

Same REST contract: change the URL and the Authorization header

Free 2,000 credits to start, then 250/day

€29/mo for 1.2M credits vs Play.ht's $31.20/mo Creator (last public price, 2025)

Pay-as-you-go at €28 per 1M credits for migration-flexibility, credits never expire

Owned by an indie founder, not Meta

Hear it before you decide.

Real API output, unedited. Press play.

The actual numbers.

Play.ht pricing verified 2025-Q4 (last pricing published before shutdown; no live page to re-check).

AudexumPlay.ht
Creator plan€29 / 1.2M credits$31.20/mo (last public price, 2025)
Pay-as-you-go€28 per 1M creditsNot offered
Audexum prices in EUR; multiply by ~1.08 for USD.

What ships in each box.

See pricing
AudexumPlay.ht
API still worksYesNo
Free tierYesNo
REST + Bearer authYesYes
Voices43Many
Voice cloningYesYes
Pay-as-you-goYesNo

Why choose Audexum.

Play.ht was many indie devs' go-to TTS API. When Meta acquired the PlayAI team and switched off the developer API, integrations stopped working.

Audexum is independently owned, EU-hosted, takes payment directly from you, and has no investor pressure to be sold or pivoted. That's not just reassurance. It's the practical reason your integration is more likely to still work in two years. Questions? [email protected].

The migration is genuinely small: swap the base URL, swap the Bearer token, map your voice ID to one of ours (we have a guide for that in the docs). If you're rebuilding because your last API died, you should pick one that's structurally hard to kill.

Two lines of code.

Same REST shape. Same JSON in, audio out. Point it at our URL with your Audexum key.

API docs
Before · Play.ht
// Old Play.ht code
fetch("https://api.play.ht/api/v2/tts", {
  method: "POST",
  headers: {
    "Authorization": "Bearer " + process.env.PLAY_HT_KEY,
    "X-User-ID": process.env.PLAY_HT_USER,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    text: "Hello",
    voice: "s3://voice-cloning-zero-shot/..."
  })
});
After · Audexum
fetch("https://audexum.com/api/synthesize", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.AUDEXUM_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    text: "Hello",
    voice: "af_heart"
  })
});

Questions, answered.

Why did Play.ht shut down?

Meta acquired the PlayAI team in July 2025 and folded it into its Superintelligence Labs division. The API went dark on 26 July 2025, ahead of schedule, and the service shut down entirely on 31 December 2025. Accounts, saved audio and voice clones were deleted.

Is the voice cloning gone too?

No. Audexum does voice cloning. You record a short consent phrase in your own voice and the clone is built from that. Paid plans include 10 voices on Pro, 25 on Scale and 100 on Business; the free tier does not include cloning. You may only clone your own voice or one you hold written permission to use.

How long is the migration?

Most apps are migrated in under 30 minutes: base URL change, key swap, voice ID mapping. We have a full voice migration table in the docs.

Try Audexum free.

2,000 free credits + 250 a day, no credit card. First WAV in your terminal in 60 seconds.

Questions? [email protected]