Detect Google WaveNet AI voices.
Suspect a clip was made with Google WaveNet? Run it through the free detector to check whether the voice is AI-generated. Google WaveNet in short: Google Cloud's WaveNet and Neural2 voices, a widely embedded, natural-sounding cloud TTS.
Google WaveNet, and why it shows up in suspicious audio
WaveNet is the DeepMind-derived neural voice technology behind Google Cloud Text-to-Speech, alongside the newer Neural2 voices. It is one of the most widely embedded cloud TTS systems, appearing in apps, assistants, and automated phone systems worldwide.
Its reach means WaveNet audio shows up in a huge variety of content.
Where you tend to see it: App and assistant voices, automated calls, and narrated content.
Google WaveNet is a legitimate product; misuse is the problem, not the tool. You can read about it on the official Google WaveNet site.
How to tell a Google WaveNet voice
The human ear is unreliable on current Google WaveNet audio. These are the kinds of artifacts a detector is trained to pick up.
- 01Natural but metronomic pacing on longer output.
- 02A consistent spectral signature across a clip.
- 03Clean fricatives and phoneme transitions.
- 04A uniform noise floor uncharacteristic of a live microphone.
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.