Detect PlayHT AI voices.
Suspect a clip was made with PlayHT? Run it through the free detector to check whether the voice is AI-generated. PlayHT in short: smooth production TTS tuned for narration and IVR, with optional cloning.
PlayHT, and why it shows up in suspicious audio
PlayHT is a text-to-speech and voice-cloning platform popular for content narration, podcasts, and phone-system (IVR) prompts. Its cloned voices show up in both legitimate media and impersonation attempts.
Its focus on long-form and telephony audio means PlayHT clips often arrive already compressed, which is exactly the harder case a good detector has to handle honestly.
Where you tend to see it: IVR and phone prompts, narrated content, and cloned-voice impersonation.
PlayHT is a legitimate product; misuse is the problem, not the tool. You can read about it on the official PlayHT site.
How to tell a PlayHT voice
The human ear is unreliable on current PlayHT audio. These are the kinds of artifacts a detector is trained to pick up.
- 01Prosodic regularity typical of production TTS, especially in long narration.
- 02Vocoder artifacts that can persist through telephony-grade compression.
- 03Consistent pacing that does not react to punctuation the way a human reader would.
- 04Uniform spectral balance across a clip that a real microphone-and-room recording would not hold.
What the detector tells you
The detector reads the audio, not the speaker. Cloned or stock voice, clean or compressed, it looks for the signs of synthesis.
Drop the clip
Upload an MP3, WAV, M4A, OGG, FLAC or AAC file. Three seconds or more of clear speech gives the most reliable result.
The model scores it
The model scores the clip. On longer recordings it scores each segment separately, so you can see which part sounds synthetic.
Read the verdict
You get a verdict on a four-step scale, from Human to AI Generated, plus an AI probability score. It tells you whether the voice is AI-generated, not which tool made it.
What to do next
A verdict is evidence, not proof. Sign in to keep the result in your detection history and share it with a link. If you are a journalist or investigator, use it alongside your own reporting; if this is a suspected scam, treat the contact as unverified and confirm through a channel you already trust. The FTC's advice on suspected scam calls is a sensible baseline.
Building this into a workflow? The API returns the same verdict as JSON, and a Chrome extension for checking audio in any tab is in development.