Home › Voice Detection › How to Check a Voice

How to tell if a voice is AI-generated — a check you can actually run.

Listening closely is not a reliable test any more: current voice generators produce breaths, pauses and room tone on purpose. What works is a short routine — get the cleanest copy you can, run it through a detector, read the result for what it is, and settle the question through something other than the audio. This page walks through it, including the parts no detector can do for you.

Open the voice detector Jump to the steps ↓
First check free, no signup MP3, WAV, M4A, OGG, FLAC · up to 10 MB Reviewed 11 Oct 2026
Known limitation — please read before acting on a result. Genuine recordings can be wrongly flagged. Real human speech, especially compressed audio such as phone calls and messaging-app voice notes, can come back as “AI-generated”, sometimes with a high score. We have not yet published an evaluation of how often this happens. Until we do, treat a synthetic verdict on a recording you believe is real as unproven, and verify the speaker directly — calling back on a number you look up yourself settles it in a way no detector can.
Start here

Answer the question that matters first.

Before you analyse anything, ask what you would do with the answer. If a recording is asking you to send money, share a code, or act urgently, the fastest and most reliable check is not acoustic at all: hang up, and call the person back on a number you already had or look up yourself. That settles who you are talking to in a way no detector can.

A detector is the right tool when the recording itself is the evidence — a clip you are about to publish, a voice note someone forwarded, a narration you were sent as finished work, an interview answer submitted as a file. In those cases, the steps below give you a result you can defend.

What the check answers. TextSight returns one thing: how likely the speech in your file is synthetic rather than a recording of a person. It does not say which tool made a voice, whether two clips are the same speaker, whether a recording was spliced, whether music is AI-generated, or whether a human is reading an AI-written script. Those are different questions with different methods.
The steps

Five steps, in order.

Each one removes a way the result could mislead you.

  1. Get the original file, not a copy of a copy. Download the file from wherever it was first shared rather than screen-recording it or playing it through a speaker into a phone. Every re-recording and re-encode strips detail the detector relies on, and heavily degraded audio is where false positives cluster.
  2. Convert only if you must, and only once. The detector accepts MP3, WAV, M4A, OGG and FLAC up to 10 MB. If your file is something else — a WhatsApp .opus note, an iPhone audio message, a video — convert it a single time, preferably to WAV so no further compression is added. The voice message guide and video voiceover guide cover the common cases.
  3. Trim to the passage you doubt. The detector currently scores the first 60 seconds of speech in a clip, and every result says how much was analysed. If the suspicious part is three minutes in, cut it out and upload that. Keep it to one speaker where you can, with as little music or background noise as possible.
  4. Run the check. Upload the clip to the voice detector. Your first check is free without an account; a free account gives you three a day, which is enough for the reference comparison in the next step.
  5. Run a known-real recording of the same person. The single most useful thing you can add. A genuine recording of the same speaker that reached you the same way — an older voice note from the same chat, a call you were on — shows what “real” scores like under these conditions. The reference-clip method explains how to read the gap.
Reading it

What the result is telling you.

Every check returns a verdict and an AI-likelihood score between 0 and 100. Read them together, and read them against the conditions of the file.

You seeWhat it suggestsWhat to do next
Likely an AI voiceThe clip carries features the model associates with synthetic speech.Treat it as a reason to investigate, not a conclusion. Run a reference clip; verify the speaker by another channel.
Likely a real human voiceNo strong synthesis evidence in the part that was scored.This does not clear the recording of being edited, misattributed or taken out of context — those need other checks.
InconclusiveThe score sits in the uncertain middle, or the audio was too short, quiet or noisy to judge.Find a longer or cleaner copy, or move to verification that does not depend on the audio.
Compressed audio is the hard case. Phone calls and messaging-app voice notes lose much of the detail detectors use, and genuine speech that has been heavily compressed can score as synthetic. A high score on a voice note is far weaker evidence than the same score on a clean studio file. The accuracy page covers what moves results up and down.

On paid plans in the voice app, results also include a timeline showing which stretches of the scored audio leaned synthetic, and a PDF report you can keep with your notes.

Limits

What no detector can settle.

  • Identity. A real-sounding voice can still be the wrong person, and a synthetic verdict does not tell you who made it. Identity is settled by calling back, asking something only the real person would know, or a pre-agreed family or team code word.
  • Live calls. TextSight checks uploaded files. It does not listen to calls in real time, so it cannot warn you during a conversation. Record a call only where the law and the other party allow it.
  • Edits and context. A genuine recording can be cut, re-ordered or presented with a false caption. Provenance — where the file came from, who first posted it, what else corroborates it — matters more than any score.
  • Certainty. A result is evidence to weigh alongside other checks. It should never be the only basis for an accusation, a disciplinary step or a financial decision.
By ear

Can you tell just by listening?

Sometimes, with older or cheaper voices: flat emotion that never shifts, odd stress on names and numbers, breaths that land in the wrong places, or a voice that sounds identical in every sentence regardless of mood. These are worth noticing, but they are not reliable. Modern generators add breathing and hesitation deliberately, and real people on bad phone lines sound strange too.

Treat your ear as a reason to check, not as the check. And treat a confident “it sounds fine to me” with the same caution, because convincing synthetic speech is exactly the scenario detectors exist for.

FAQ

Checking a voice questions.

How long does a clip need to be?
A few seconds of clear speech can be enough, but more is better up to a point. The detector currently scores the first 60 seconds of a clip, so 20 to 60 seconds of a single speaker, without music, is the useful range. Very short, quiet or noisy clips often come back inconclusive.
Is a result proof that a voice is fake?
No. It is evidence to weigh alongside other checks. A high score on clean audio is a strong reason to investigate; a high score on a compressed voice note or phone recording is much weaker. Never use a single result as the only basis for an accusation or decision.
Can it tell me which AI tool made the voice?
No. It returns human versus synthetic with a score. It does not name ElevenLabs, OpenAI or any other generator, and we do not publish a per-tool detection rate.
Can it check a phone call while it is happening?
No. It analyses uploaded audio files only. For a suspicious live call, hang up and call back on a number you look up yourself.
Does it work on languages other than English?
The model reads acoustic properties of the recording rather than the words, so it is not English-only by design. We have not published any per-language evaluation, so treat results on non-English speech with extra caution and use a reference clip where you can.
Is my audio kept?
No. Audio is processed and discarded rather than stored, and it is not used to train the model. Signed-in users keep the result and file details in their history, not the recording.
Related

More voice detection guides.

Further reading

Run the check. Then verify the person.

Your first check is free with no signup — 3 a day with a free account. Your audio is processed and discarded, never stored.

Open the voice detector All voice guides
Uploaded files only · first 60 seconds scored · a result is evidence, never proof