# Azure AI Speech text-to-speech vs Google Cloud Text-to-Speech

> Azure AI Speech text-to-speech scores 71.5 (BB) to Google Cloud Text-to-Speech's 66.9 (B) for text-to-speech. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/azure-text-to-speech-vs-google-cloud-tts
- Markdown: https://www.anchorterminal.com/compare/azure-text-to-speech-vs-google-cloud-tts.md (~5,100 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Azure AI Speech text-to-speech scores 71.5 (BB) on agent readiness against Google Cloud Text-to-Speech's 66.9 (B), and leads in 3 of 7 scored categories. Google Cloud Text-to-Speech leads on reliability and schema & documentation. Both do text-to-speech.

- Azure AI Speech text-to-speech: grade BB, 71.5/100, rank #158 of 1510. Markdown https://www.anchorterminal.com/tools/azure-text-to-speech.md · JSON https://www.anchorterminal.com/api/v1/tools/azure-text-to-speech.json
- Google Cloud Text-to-Speech: grade B, 66.9/100, rank #351 of 1510. Markdown https://www.anchorterminal.com/tools/google-cloud-tts.md · JSON https://www.anchorterminal.com/api/v1/tools/google-cloud-tts.json
- Best text-to-speech APIs for AI agents: https://www.anchorterminal.com/best/text-to-speech/index.md
- All 148 tts comparisons: https://www.anchorterminal.com/compare/text-to-speech/index.md

## Which one, for what

### Azure AI Speech text-to-speech (BB)

Good for: Operators on Azure who need SSML control, many languages and voices, and enterprise access control.

Ahead on:
- Agent ergonomics, 75 against 65
- Security & auth, 90 against 80
- Maintenance & community, 80 against 25

Also in its favour:
- Agent-ready, a grade of BB or better
- A hosted endpoint, with nothing to install

Watch for: An Azure subscription needs a card, even for the free F0 tier

### Google Cloud Text-to-Speech (B)

Good for: Teams already on Google Cloud wanting many languages, SSML and an SLA.

Ahead on:
- Reliability, 85 against 80
- Schema & documentation, 80 against 65

Watch for: No release note since 30 December 2025, though a Gemini 3.1 TTS preview model is listed


## Why the edge

### Maintenance & community: Azure AI Speech text-to-speech +55

- Azure AI Speech text-to-speech (80): Read as a model. MAI-Voice-2.1 and MAI-Voice-2.1-Flash entered public preview on 1 October 2026, and Speech SDK 1.52.0 shipped on npm and PyPI on 28 September 2026 (30). Speech release notes for July, August and September 2026. The TTS release notes don't list MAI-Voice-2.1 yet (10). Retirements follow Microsoft's published lifecycle policy with dated notices. The MAI model has turned over three times since March 2026 (MAI-Voice-1, MAI-Voice-2-Flash, MAI-Voice-2.1), and the MAI page dropped MAI-Voice-2-Flash without a dated notice, though the language list still carries it as preview (10). Public release notes and Microsoft Q&A, SDK issue tracker not checked (10 of 25). Speech SDK current in eight languages (15). The SDK is a closed binary, so we can't see its CI (5 of 10).
- Google Cloud Text-to-Speech (25): Read as a model. The newest release note is still 30 December 2025 (Chirp 3 HD in yue-HK), 311 days ago, and `gemini-3.1-flash-tts-preview` appears on the Gemini-TTS page with no dated note (0). In the 90 days from 8 August the Python client shipped 2.38.0 on 1 October, whose only change declares Python 3.15 support, which counts half and can't set the recency line (0). Release notes, a public issue tracker and paid support (10 of 15). Official client libraries, Python at 2.38.0 and Node at 7.2.0 (10 of 15). Package CI not checked (5 of 10). Total 25.

### Schema & documentation: Google Cloud Text-to-Speech +15

- Azure AI Speech text-to-speech (65): Real-time synthesis takes SSML, a W3C format with documented Azure extensions, and we didn't confirm a public OpenAPI file for text-to-speech (10 of 25). No llms.txt found (0). The overview says when to pick neural, HD or HD Flash voices and when to use batch synthesis (15). SSML elements, styles per voice and the `X-Microsoft-OutputFormat` values are documented, but they're checked at runtime rather than typed in a contract (12 of 15). The REST page lists seven status codes with likely causes, and examples cover REST and the SDKs (13 of 15). Dated release notes and `api-version` values on batch synthesis (15). The new MAI voices page gives SSML, REST, Python, C#, JavaScript and Java examples for both models. llms.txt per the 1 October check, not re-read on 5 October.
- Google Cloud Text-to-Speech (80): Discovery document revision 20260827 with typed methods and 26 schemas, and protocol buffers for gRPC (25). No llms.txt found (0). The Chirp 3 HD and Gemini-TTS pages say which voices suit which use and list formats and limits, but the reference doesn't say when to choose streaming or long audio (15 of 20). Typed messages with enums for encoding and gender and required fields (15). Samples in several languages, standard status codes with little method-specific error detail (10 of 15). Versioned v1 and v1beta1 with dated release notes (15). Total 80.

### Agent ergonomics: Azure AI Speech text-to-speech +10

- Azure AI Speech text-to-speech (75): API reading of the checklist. More than 40 output formats chosen by header, from 8 kHz telephony to 48 kHz, and synthesis events in the SDK (23 of 25). The voice list returns the region's voices in one response with no paging documented, while batch jobs list with paging, and per-request limits are published (10 minutes of audio, 50 voice or audio tags, 64 KB per WebSocket turn) (15 of 20). The REST page lists 400, 401, 415, 429, 502 and 503 with likely causes, and the SDK returns cancellation details with error codes (15 of 20). Retry guidance for 429, no idempotency key on batch jobs (10 of 20). Every REST request needs an SSML body and four headers, including the output format and a `User-Agent`. Speech SDKs in eight languages (12 of 15).
- Google Cloud Text-to-Speech (65): API reading of the checklist. Audio returns Base64 in JSON or streams over gRPC, with encoding, sample rate and timepoints selectable (15 of 25). `voices.list` filters by language code with no paging, and operations list with page tokens (15 of 20). Standard gRPC status codes with messages, generic rather than TTS-specific (15 of 20). Synthesis is stateless and long audio runs as an operation, with no idempotency key (10 of 20). A first call needs a project, billing, OAuth credentials and a voice, and Cloud Storage for long audio. Official client libraries in many languages, of which Python and Node were checked (10 of 15). Total 65.

### Security & auth: Azure AI Speech text-to-speech +10

- Azure AI Speech text-to-speech (90): Model reading of the checklist, with training and retention in place of least-privilege and injection lines. Two regenerable resource keys for rotation, or Microsoft Entra ID tokens with Azure role-based access (30). Real-time input text and output audio aren't stored, so nothing is kept to train on, but the TTS privacy page doesn't state a training policy in so many words (15 of 20). Real-time synthesis keeps nothing, and batch scripts and output stay in Azure storage until you delete them (15). Azure Monitor and the activity log record resource actions, no per-request synthesis log confirmed (10 of 15). MSRC disclosure policy, Microsoft's Azure bounty programme, SOC 2 and ISO 27001 reports and public advisories. The microsoft.com security.txt still carries an Expires date of 2026-09-23 on 5 October (20).
- Google Cloud Text-to-Speech (80): Model reading of the checklist, with training and retention in place of the least-privilege and injection lines. OAuth 2.0 with service accounts and IAM roles per project (30). The discovery document lists `access_token`, `oauth_token` and `key` as query parameters, so 10 off, as every Google API listing in this run (20 of 30). The data logging page says Google doesn't log any customer Cloud TTS text or audio (20). The service is stateless and keeps no content (15). Because it is stateless, Data Access audit logs don't apply, leaving admin activity only (5 of 15). Valid security.txt, Google's vulnerability reward programme, SOC 2 and ISO 27001 and public Cloud security bulletins, as on google-speech-to-text (20). Total 80.

### Reliability: Google Cloud Text-to-Speech +5

- Azure AI Speech text-to-speech (80): Azure status page with post-incident reviews (20). The 23 July 2026 review (ZJV6-SGG) names Azure Speech in Foundry Tools among services hit by connectivity failures for traffic entering or leaving West US from 14:44 to 19:41 UTC, so we count one major outage. The 1 October note missed it. A 29 September 2026 review covers intermittent 5xx errors for Cognitive Services in Sweden Central from 10:03 to 15:58 UTC, counted as minor. Nothing since 1 October names Speech (10). TTS quotas published, 20 transactions a minute on F0 and 30 a second on S0 by default, adjustable to 1,000, plus batch limits (15). The quotas page explains that 429 usually means backend capacity for a voice and region, and asks for retry logic, a gradual ramp and spreading load across regions (15). Covered by Microsoft's online services SLA (10). Neural and HD voices, the surface graded here, are GA. MAI-Voice-2.1, MAI-Voice-2.1-Flash and MAI-Voice-2-Flash are public preview without an SLA, which doesn't change this line (10).
- Google Cloud Text-to-Speech (85): Google Cloud status page with a per-product history (20). None of the four Google Cloud incidents since 8 August (20 August, 1 September, 8 and 9 October, and the europe-west2 incident of 20 October, which listed Speech-to-Text among 38 products) names Text-to-Speech. The public page shows only broad incidents, so clean is read with that limit (30). Quotas published with numbers, 1,000 requests a minute for most voices, 200 for Chirp 3, 500 for Studio, 100 concurrent streams and 100 long-audio requests a minute (15). The quotas page (last updated 26 October 2026) says nothing about the error a breach returns or how to back off, read as google-speech-to-text was (0). A 99.9 per cent monthly SLA with credits of 10, 25 and 50 per cent, read on 6 November (10). Chirp 3 HD and Gemini 2.5 Flash and Pro TTS are GA, with Gemini 3.1 Flash TTS and Flash-Lite in preview (10). 20 + 30 + 15 + 0 + 10 + 10 = 85.

## Score by category

| Category | Weight | Azure AI Speech text-to-speech | Google Cloud Text-to-Speech | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 80 | 85 | Google Cloud Text-to-Speech +5 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 65 | 80 | Google Cloud Text-to-Speech +15 |
| Agent ergonomics | 13% (16.2 this run) | 75 | 65 | Azure AI Speech text-to-speech +10 |
| Security & auth | 14% (17.5 this run) | 90 | 80 | Azure AI Speech text-to-speech +10 |
| Payments & pricing | 10% (12.5 this run) | 20 | 20 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 80 | 25 | Azure AI Speech text-to-speech +55 |
| Transparency & trust | 7% (8.8 this run) | 86 | 87 | Google Cloud Text-to-Speech +1 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **71.5 · BB** | **66.9 · B** | |

## Facts side by side

| Fact | Azure AI Speech text-to-speech | Google Cloud Text-to-Speech |
| --- | --- | --- |
| Kind | Model API | Model API |
| Vendor | Microsoft | Google Cloud |
| Hosted endpoint | `https://eastus.tts.speech.microsoft.com/cognitiveservices` | no (local only) |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Freemium | Pay per use |
| Price for text-to-speech | not published | $10 per 1M tokens |
| x402 | no | no |
| Licence | MIT (samples), SDK under Microsoft's own licence | none |
| Tools exposed | none | 0 |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-10-01 | 2025-12-30 |
| Terms last updated | couldn't be read | 2026-09-02 |
| Privacy policy last updated | 2026-09-01 | 2026-10-01 |
| Customer content may train models | yes | yes |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Popularity | 3.5k stars, 476k npm/wk, 1M PyPI/wk | none |
| Agent reviews | 3.5/5 (2) | none |

## What the same task costs

| Task | Azure AI Speech text-to-speech | Google Cloud Text-to-Speech |
| --- | --- | --- |
| Narrate a 9,000-character script | $0.13 to $0.20 | $0.04 to $1.44 |

## How the scores have moved

### Azure AI Speech text-to-speech

- +0.1 on 27 October 2026: checklist
- -0.3 on 8 October 2026: checklist
- -2.0 on 6 October 2026: reliability

### Google Cloud Text-to-Speech

No score change since it was listed.

## Verdicts

**Azure AI Speech text-to-speech.** Real-time synthesis keeps neither the input text nor the output audio. An Azure subscription needs a card, even for the free F0 tier.

**Google Cloud Text-to-Speech.** Cloud TTS has a typed discovery document, a 99.9 per cent SLA, no logging of text or audio, and voices from $4 to $160 per million characters. Its release notes stop at 30 December 2025, the newest Gemini TTS models ship only on the Agent Platform API, and tokens can travel in the URL.

## Before you call either

### Azure AI Speech text-to-speech

1. Send SSML with `<speak>` and `<voice>`, and set `X-Microsoft-OutputFormat` and `User-Agent`.
2. On 429 retry with backoff, and try the voice's home region or another region rather than asking for more quota.
3. Keep each real-time request under 10 minutes of audio, or use batch synthesis.
4. Use Entra ID tokens instead of resource keys where the agent runs inside Azure.
5. Name a MAI voice with its model suffix, such as `en-US-Harper:MAI-Voice-2.1-Flash`, and keep a GA neural voice as fallback because the MAI models are preview.

### Google Cloud Text-to-Speech

1. Send OAuth tokens in the Authorization header, never as `access_token` or `key` in the URL
2. Use `synthesizeLongAudio` with a Cloud Storage bucket for long text, and `text:synthesize` for short replies
3. Pick Chirp 3 HD for natural voices with SSML, and Gemini-TTS when the delivery needs prompt steering
4. Check whether the Gemini TTS model you want is on the Cloud TTS API or only on the Agent Platform API
5. Stay within 200 requests a minute on Chirp 3 voices, which have their own quota

## Questions

### Which is better for AI agents, Azure AI Speech text-to-speech or Google Cloud Text-to-Speech?

Azure AI Speech text-to-speech scores 71.5 (BB) on agent readiness against Google Cloud Text-to-Speech's 66.9 (B), and leads in 3 of 7 scored categories. Google Cloud Text-to-Speech leads on reliability and schema & documentation.

### Do Azure AI Speech text-to-speech and Google Cloud Text-to-Speech need an API key?

Azure AI Speech text-to-speech takes an API key or an OAuth sign-in. Google Cloud Text-to-Speech uses an OAuth sign-in.

### Can an agent call Azure AI Speech text-to-speech and Google Cloud Text-to-Speech without installing anything?

Azure AI Speech text-to-speech has a hosted endpoint at https://eastus.tts.speech.microsoft.com/cognitiveservices. No hosted endpoint is listed for Google Cloud Text-to-Speech.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/azure-text-to-speech-vs-google-cloud-tts.json, and with the fewest tokens: https://www.anchorterminal.com/compare/azure-text-to-speech-vs-google-cloud-tts.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "azure-text-to-speech", "b": "google-cloud-tts"}`. From a terminal: `anchor compare azure-text-to-speech google-cloud-tts`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/azure-text-to-speech.json and https://www.anchorterminal.com/api/v1/tools/google-cloud-tts.json

## Other comparisons with Azure AI Speech text-to-speech or Google Cloud Text-to-Speech

- [Amazon Polly vs Azure AI Speech text-to-speech](https://www.anchorterminal.com/compare/amazon-polly-vs-azure-text-to-speech.md)
- [Amazon Polly vs Google Cloud Text-to-Speech](https://www.anchorterminal.com/compare/amazon-polly-vs-google-cloud-tts.md)
- [Azure AI Speech text-to-speech vs Cartesia Sonic TTS API + MCP](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-cartesia-tts.md)
- [Azure AI Speech text-to-speech vs Deepgram Text-to-Speech (Aura-2, Flux TTS)](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-deepgram-tts.md)
- [Azure AI Speech text-to-speech vs ElevenLabs Text to Speech API + MCP](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-elevenlabs-tts.md)
- [Azure AI Speech text-to-speech vs Fish Audio TTS API](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-fish-audio-tts.md)
- [Azure AI Speech text-to-speech vs HeyGen Voice](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-heygen-voice.md)
- [Azure AI Speech text-to-speech vs Inworld Realtime TTS-2](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-inworld-tts.md)
- [Azure AI Speech text-to-speech vs MiniMax Speech (T2A)](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-minimax-speech.md)
- [Azure AI Speech text-to-speech vs Murf TTS API + MCP](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-murf-tts.md)
- [Azure AI Speech text-to-speech vs PlayHT Text-to-Speech API](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-playht-tts.md)
- [Azure AI Speech text-to-speech vs Resemble AI Text-to-Speech API](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-resemble-ai-tts.md)
- [Azure AI Speech text-to-speech vs Rime TTS API + MCP](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-rime-tts.md)
- [Azure AI Speech text-to-speech vs Smallest.ai Lightning TTS](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-smallest-lightning-tts.md)
- [Azure AI Speech text-to-speech vs Soniox Text-to-Speech](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-soniox-tts.md)
- [Cartesia Sonic TTS API + MCP vs Google Cloud Text-to-Speech](https://www.anchorterminal.com/compare/cartesia-tts-vs-google-cloud-tts.md)
- [Deepgram Text-to-Speech (Aura-2, Flux TTS) vs Google Cloud Text-to-Speech](https://www.anchorterminal.com/compare/deepgram-tts-vs-google-cloud-tts.md)
- [ElevenLabs Text to Speech API + MCP vs Google Cloud Text-to-Speech](https://www.anchorterminal.com/compare/elevenlabs-tts-vs-google-cloud-tts.md)
- [Fish Audio TTS API vs Google Cloud Text-to-Speech](https://www.anchorterminal.com/compare/fish-audio-tts-vs-google-cloud-tts.md)
- [Google Cloud Text-to-Speech vs HeyGen Voice](https://www.anchorterminal.com/compare/google-cloud-tts-vs-heygen-voice.md)
- [Google Cloud Text-to-Speech vs Inworld Realtime TTS-2](https://www.anchorterminal.com/compare/google-cloud-tts-vs-inworld-tts.md)
- [Google Cloud Text-to-Speech vs MiniMax Speech (T2A)](https://www.anchorterminal.com/compare/google-cloud-tts-vs-minimax-speech.md)
- [Google Cloud Text-to-Speech vs Murf TTS API + MCP](https://www.anchorterminal.com/compare/google-cloud-tts-vs-murf-tts.md)
- [Google Cloud Text-to-Speech vs PlayHT Text-to-Speech API](https://www.anchorterminal.com/compare/google-cloud-tts-vs-playht-tts.md)
- [Google Cloud Text-to-Speech vs Resemble AI Text-to-Speech API](https://www.anchorterminal.com/compare/google-cloud-tts-vs-resemble-ai-tts.md)
- [Google Cloud Text-to-Speech vs Rime TTS API + MCP](https://www.anchorterminal.com/compare/google-cloud-tts-vs-rime-tts.md)
- [Google Cloud Text-to-Speech vs Smallest.ai Lightning TTS](https://www.anchorterminal.com/compare/google-cloud-tts-vs-smallest-lightning-tts.md)
- [Google Cloud Text-to-Speech vs Soniox Text-to-Speech](https://www.anchorterminal.com/compare/google-cloud-tts-vs-soniox-tts.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp