Synthetic voice can make information easier to hear, localise a script, create a consistent narration style, or prototype an accessibility experience. It can also mislead people, expose sensitive voice data, and create serious rights problems. A responsible comparison begins with the difference between text-to-speech and voice cloning, then asks whether the team has consent and a clear purpose.
This is a selection framework, not an in-house audio benchmark. It does not claim that Get AI Updates tested providers, measured latency, or verified a voice match. Product features, languages, plan terms, and safeguards change. Confirm the documentation, terms, and account controls for the exact product in use before recording or publishing anything.
Text-to-speech and voice cloning are different decisions
Standard text-to-speech (TTS) turns text into audio using an available synthetic voice. It can be useful for an article narration, an app prompt, an accessibility feature, or a prototype. The source text may still need editorial review, but no specific person’s voice needs to be replicated.
Voice cloning or custom voice work tries to reproduce the characteristics of a particular voice. That can be appropriate when the voice owner knowingly participates, approves the use, and understands how recordings and outputs will be handled. It is not a shortcut for using a public figure, a colleague, a customer, an actor, or a family member without clear permission.
| Workflow | Example legitimate purpose | Required control |
|---|---|---|
| Standard TTS | Narrate a help article with a provider-supplied voice | Confirm licence, language, output review, and any disclosure need |
| Custom brand voice | Create a voice for a product where the voice talent has agreed | Signed scope, approved recordings, retention/deletion plan, output approval |
| Voice clone | Enable a speaker to create their own approved synthetic voice | Explicit informed consent, verification, use restrictions, and records |
| Impersonation request | Make a recording sound like a recognisable person who did not approve it | Decline; do not upload or generate |
The final row is not an edge case. A workflow needs a clear refusal path before it receives a risky request.
Consent is more than a checkbox
Before collecting audio, document who owns the voice, the permitted use, the territory or audience, the duration, whether edits or translations are allowed, whether the voice may be shared with others, and how the owner can withdraw permission. A person agreeing to record one explainer does not automatically approve political, advertising, customer-service, or training use.
Some services use verification steps as part of their voice-cloning process. Verification can be a useful safeguard, but it does not prove every downstream use is authorised. The organisation publishing the audio still needs to respect the original agreement and applicable law.
Do not treat publicly available clips, podcast interviews, video audio, or a person’s voicemail as source material that is free to clone. A recording being accessible online is not evidence of consent for synthetic reproduction.
Select tools by operational fit
Avoid a generic “most realistic voice” ranking. Naturalness is subjective and depends on language, script, direction, and listener expectations. Instead, evaluate the workflow against a documented use case.
| Evaluation area | Questions to ask |
|---|---|
| Voice source | Is it provider-supplied, commissioned, or a specific person’s approved voice? |
| Consent and rights | What permission exists, who holds it, and where is it recorded? |
| Language and pronunciation | Does the selected voice/language support the actual script and names? |
| Editing controls | Can the team revise pronunciation, pacing, and text without altering the approved meaning? |
| Data handling | What audio, transcript, and account data are uploaded, retained, or shared? |
| Output controls | Can the team label, review, archive, and remove published files when needed? |
| Cost model | What unit is billed and how will usage limits be monitored? |
Microsoft’s current TTS documentation, for example, distinguishes standard voices from custom-voice options and points implementers to responsible-AI and transparency material. That is a useful reminder that a feature checklist is not a deployment plan.
A safe first implementation
Start with a short, original script and a provider-supplied standard voice. Do not use customer calls, staff recordings, or a celebrity-like voice in the first test. Keep the task small:
Purpose: audio version of a 90-second accessibility explainer
Script owner: editorial team
Voice: provider-supplied standard voice
Audience: public website visitors
Allowed edits: punctuation and pronunciation fixes that preserve meaning
Review: editor checks accuracy; accessibility reviewer checks transcript and player controls
Disclosure: decide whether the page needs a synthetic-audio note
The audio should not be accepted because it sounds polished. Review the transcript against the approved script, check names and numbers, provide controls that work on mobile, and ensure that the page still offers the information as readable text. An audio player must not hide the facts that a user needs to understand a page.
Use a consent and output register
For any custom or cloned voice, retain an internal record that an authorised person can review:
Voice owner: [legal/approved name]
Consent date and authorised approver: [record reference]
Allowed uses: [specific channels and content types]
Not allowed: [political, paid ads, training, sublicensing, etc.]
Source recordings: [secure location and retention period]
Provider/account: [exact product and plan]
Published outputs: [URLs or asset IDs]
Withdrawal/removal process: [responsible owner and response path]
Never place this sensitive record in a public article, a public repository, or an image caption. The public page needs only the disclosure that serves the audience; the detailed consent record belongs in an access-controlled business process.
Transparency and deceptive use
Use plain disclosure where people could reasonably believe they are hearing a real person or a live interaction. Do not fabricate endorsements, customer testimonials, emergency messages, evidence, or official communications. Do not use a synthetic voice to obscure who is responsible for a message.
Provider policies can reinforce this. ElevenLabs’ published policy prohibits cloning or impersonating a living person without explicit informed consent or other valid authorisation, and it bars misleading use. Its documentation also describes verification as a safeguard with limitations. Those policies are not a substitute for your own consent record, but they make the direction clear: safety belongs in both product controls and the operating process.
Quality review without invented benchmarks
If a team needs to compare products, define a script and rubric before generating audio. Use content that the team owns and avoid sensitive names or claims. Evaluate clarity, pronunciation of verified names, consistency with the approved script, player accessibility, time needed for an authorised editor to revise, and the availability of required language support.
Record the date, product/version, account plan, settings, script, reviewer, and result. Do not call one provider “best” from a single listening session. Do not invent a latency, conversion, retention, or listener-preference statistic. If no controlled evaluation exists, describe the provider’s documented features and the selection criteria instead.
Common failure modes
- Consent drift: a recording approved for one tutorial is reused in advertising or another language without permission.
- Transcript drift: an edited script no longer matches the audio or changes a factual meaning.
- Weak disclosure: listeners are led to believe a synthetic message is a real person’s recording.
- Inaccessible delivery: no transcript, unclear controls, or audio-only essential information.
- Uncontrolled sharing: source recordings or cloned voices are available to more people than the agreement permits.
- Unreviewed automation: an application generates customer-facing audio with no content or incident-review path.
Each failure mode is a reason to pause, narrow the use case, and add an accountable human owner.
Related reading on Get AI Updates
For a broader voice tool comparison, see Top AI Voice Cloners & ElevenLabs Guide. For editorial workflow context, see Best Free AI Blog Content Generators. Recheck both pages for current provider terms before making a purchase or recording voice data.
Sources and editorial review notes
- Microsoft Azure text-to-speech overview, ElevenLabs voice-cloning documentation, and ElevenLabs Prohibited Use Policy.
- Last source check: 3 November 2026. A named editor and the authorised voice owner must approve any provider-specific statement, recording, clone, screenshot, or published audio. This guide is not legal advice and does not establish consent for any voice.
