Detect Descript AI voices.
Suspect a clip was made with Descript? Run it through the free detector to check whether the voice is AI-generated. Descript in short: editor-native voice cloning (Overdub) plus stock AI voices, tuned to blend into a real recorded track.
Descript, and why it shows up in suspicious audio
Descript is a widely used audio and video editor whose Overdub feature clones a voice from a training sample, letting an editor fix or add speech by typing rather than re-recording. It is a staple of podcast and video production.
Because Overdub is built to blend seamlessly into a genuine recording, an unlabeled synthesized insert can sit inside otherwise-real audio, which is exactly the case worth checking.
Where you tend to see it: Podcast and video edits, corrections spliced into real recordings, and cloned-voice inserts.
Descript is a legitimate product; misuse is the problem, not the tool. You can read about it on the official Descript site.
How to tell a Descript voice
The human ear is unreliable on current Descript audio. These are the kinds of artifacts a detector is trained to pick up.
- 01Seams where a cloned insert meets real recorded audio, heard as small shifts in room tone or level.
- 02Prosodic evenness in the synthesized segments that the surrounding human speech does not share.
- 03Timbre that stays fixed across an insert where a re-recorded take would drift.
- 04Vocoder artifacts in fricatives that survive the editor's export and re-encoding.
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.