Detect Amazon Polly AI voices.
Suspect a clip was made with Amazon Polly? Run it through the free detector to check whether the voice is AI-generated. Amazon Polly in short: AWS cloud text-to-speech, including neural (NTTS) voices, common in apps, IVR, and notifications.
Amazon Polly, and why it shows up in suspicious audio
Amazon Polly is Amazon Web Services' text-to-speech engine, embedded in a vast range of apps, phone systems, and notification pipelines. Its neural voices are deployed at enormous scale.
Because Polly is so widely available through AWS, its audio appears in everything from accessibility features to automated call systems, and occasionally in scripted impersonation.
Where you tend to see it: IVR and phone systems, app narration, and automated notifications.
Amazon Polly is a legitimate product; misuse is the problem, not the tool. You can read about it on the official Amazon Polly site.
How to tell an Amazon Polly voice
The human ear is unreliable on current Amazon Polly audio. These are the kinds of artifacts a detector is trained to pick up.
- 01Production-TTS pacing that does not react to meaning the way a human reader would.
- 02Synthesis artifacts that persist through telephony-grade compression.
- 03Uniform spectral balance across a clip a real microphone and room would not hold.
- 04Even, unvarying energy across long passages.
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.