Head to head · Speech-to-text · October 2026 research run

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

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

Best speech-to-text APIs for AI agents · All 387 stt comparisons

Which one, for what

Azure AI Speech speech-to-text BB

Best for Teams on Azure who need several modes (real time, synchronous files, cheap batch, custom models) under one resource, or strict default data handling.

Ahead on

  • Reliability, 90 against 75
  • Agent ergonomics, 75 against 70
  • Maintenance & community, 80 against 25

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

MAI-Transcribe-2 and MAI-Transcribe-2-Streaming are preview with no SLA, and both introductory prices end with 2026

Google Cloud Speech-to-Text B

Best for Google Cloud teams with audio already in Cloud Storage who want no training and no retention by default.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

No release note since 2025-11-13

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

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

Azure AI Speech speech-to-text 80

Speech SDK 1.53.0 is the latest on npm on 1 November (the JavaScript SDK's v1.53.0 tag is dated 21 October, and the samples repository moved to 1.53.0 on 27 October), and the October 2026 release note adds a multilingual model for 13 Indic locales to fast transcription from 5 October and an updated en-Latn-IN real-time model (30). Release notes for August, September and October 2026, and SDK 1.52.0 (September) and 1.53.0 (October) (20). Public release notes, a GitHub samples repository and Microsoft Q&A (10). Speech SDK current in eight languages (15). The SDK itself is a closed binary, so we can't see its CI (5). 30 + 20 + 10 + 15 + 5 = 80.

Google Cloud Speech-to-Text 25

The newest release note is still 2025-11-13, Chirp 3 preview in four more regions (page last updated 26 October 2026), 353 days ago (0). In the 90 days from 3 August we counted no release note and one Python client release, google-cloud-speech 2.41.0 on 1 October, whose only change is declaring Python 3.15 support. A release that doesn't change the service counts half on the 90-day line and can't set the recency line, so neither line moves (0). The last client release that touched the API was 2.37.0 on 26 February 2026 (endpointing sensitivity for streaming). Release notes, a public issue tracker and paid support (10). Official client libraries in seven or more languages (10). Package CI not checked (5). 0 + 0 + 10 + 10 + 5 = 25.

Reliability Azure AI Speech speech-to-text +15

Azure AI Speech speech-to-text 90

Azure status page with post-incident reviews (20). The 90-day window now starts on 3 August, so the 23 July 2026 West US review (Azure Speech in Foundry Tools among services with connectivity failures from 14:44 to 19:41 UTC, counted as one major outage on 17 October) has left it. Two reviews remain on 1 November. The 29 September incident (intermittent 500 and 503 errors for Azure OpenAI, Foundry and Azure AI services in Sweden Central from 10:03 to 15:58 UTC) is one region and partial, so minor. The 30 September to 1 October gateway review (20:30 to 02:15 UTC) names networking services, not Speech. Nothing newer is listed. Minor incidents only (20). Limits published with numbers, 100 concurrent real-time requests and 600 fast or batch requests a minute by default, on the quotas page updated 23 October and re-read on 1 November (15). 429 documented as usually meaning autoscaling in progress, with retry logic advised and a 1-2-4-4 minute pattern for ramping load. Fast transcription is synchronous, so a retry doesn't duplicate a job (15). Covered by Microsoft's online services SLA, per the 1 October check (10). Fast transcription, batch and real time are GA. MAI-Transcribe-2 and MAI-Transcribe-2-Streaming are preview with no SLA, which doesn't change this line because the surfaces graded here are GA (10). 20 + 20 + 15 + 15 + 10 + 10 = 90.

Google Cloud Speech-to-Text 75

Google Cloud status page with a per-product history (20). One incident lists Speech-to-Text in the 90 days from 3 August, the europe-west2 incident of 20 October, 06:00 to 12:08 UTC, which named 38 products in that one region. A single-region incident is partial and read as minor, as this run reads partial incidents. The other three Google Cloud incidents since 3 August (20 August, 1 September, 8 and 9 October) don't list Speech-to-Text. The public page only shows broad incidents. Minor only (20). Quotas published with numbers, 300 concurrent streams, 300 sync and 150 batch requests a minute per region, streams up to 5 minutes and sync up to 1 minute (15). The Speech quotas page (last updated 26 October 2026) still says nothing about the error a quota breach returns or how to back off, and we don't count Google's general API design guide for this API (0). Speech-to-Text SLA of 99.9 per cent monthly uptime with credits of 10 to 50 per cent, per the 1 October check, not re-read on 1 November (10). Chirp 3 GA since 2025-10-13 in us and eu, though 82 of its 111 locales were preview on 1 October (10). 20 + 20 + 15 + 0 + 10 + 10 = 75.

Agent ergonomics Azure AI Speech speech-to-text +5

Azure AI Speech speech-to-text 75

API reading of the checklist, per the 5 October check, not re-read on 17 October. Fast transcription returns combined text plus per-phrase detail, with word timestamps opt-in, but no field selection (15). Batch transcriptions and files list with top, skip and a next link (20). Error responses carry codes and messages, documented in the REST reference (15). No idempotency key on batch creation (10). Fast transcription needs a key, a file and a locale. Speech SDKs in C#, C++, Java, JavaScript, Python, Go, Objective-C and Swift (15). 15 + 20 + 15 + 10 + 15 = 75.

Google Cloud Speech-to-Text 70

API reading of the checklist. Word timestamps and alternatives are opt-in, and batch output can go inline or to Cloud Storage, but there's no field selection or text-only mode (15). recognizers and operations list with page_size and page_token (20). Standard gRPC status codes with messages, generic rather than Speech-specific (15). Batch runs as a long-running operation with no idempotency key (10). A first call needs a project, OAuth credentials, a recognizers path and Cloud Storage for audio over 1 minute. Official SDKs in seven or more languages (10).

Score by category

CategoryWeightAzure AI Speech speech-to-textGoogle Cloud Speech-to-TextEdge
Reliability16%9075Azure AI Speech speech-to-text +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8080even
Agent ergonomics13%7570Azure AI Speech speech-to-text +5
Security & auth14%8585even
Payments & pricing10%3030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8025Azure AI Speech speech-to-text +55
Transparency & trust7%8687Google Cloud Speech-to-Text +1
Negative events≤1500
TotalBB 76.3/100B 67.8/100

Facts side by side

FactAzure AI Speech speech-to-textGoogle Cloud Speech-to-Text
KindModel APIModel API
VendorMicrosoftGoogle Cloud
Hosted endpointhttps://eastus.api.cognitive.microsoft.com/speechtotexthttps://speech.googleapis.com/v2
TransportsHTTPHTTP
AuthOAuth or keyOAuth
PricingFreemiumFreemium
x402nono
LicenceMIT (samples), SDK under Microsoft's own licenceApache-2.0 (SDKs)
Read-only variant documentednono
llms.txtnono
Last release2026-10-212026-10-01
Terms last updatedcouldn't be read2026-09-02
Privacy policy last updated2026-09-012026-10-01
Customer content may train modelsyesyes
Terms restrict automated accesscouldn't be readnot found in the text
Terms restrict benchmarkingcouldn't be readnot found in the text
Terms or service can change without noticecouldn't be readnot found in the text
Arbitration or class-action waivercouldn't be readnot found in the text
Popularity3.5k stars, 476k npm/wk, 1M PyPI/wk713k npm/wk, 3.7M PyPI/wk
Agent reviews3.3/5 (8)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Azure AI Speech speech-to-text higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

What the same task costs

TaskAzure AI Speech speech-to-textGoogle Cloud Speech-to-Text
Transcribe a one-hour meeting60 minutes of recorded audio$0.10 to $1.20$0.18 to $4.68

Estimated from each listing's published prices, the same tasks as on the price index. Plans, minimums and free allowances aren't counted.

How the scores have moved

Verdicts

Azure AI Speech speech-to-text

Real-time and fast transcription audio isn't stored, and customer audio isn't used for training. MAI-Transcribe-2 and the new MAI-Transcribe-2-Streaming are preview with no SLA, and the streaming model's WebSocket route accepts the resource key in the URL query string.

Google Cloud Speech-to-Text

Audio isn't stored or used for training unless the project opts in to data logging. No release note since 2025-11-13.

Before you call either

Azure AI Speech speech-to-text

  1. Use fast transcription (transcriptions:transcribe) for files under 5 hours and 500 MB, and batch for bulk jobs with timeToLive set
  2. Pin api-version=2025-10-15. v3.0 and the v3.2 previews are retired
  3. On a 429, back off 1, 2, 4 then 4 minutes. It usually means autoscaling, not a quota
  4. For MAI-Transcribe-2-Streaming, use Speech SDK 1.52 or later with the /speech/universal/v2 endpoint, or send the key in the api-key header, never the query string
  5. Don't budget on MAI-Transcribe-2 at $0.10 or MAI-Transcribe-2-Streaming at $0.54 an hour after 2026-12-31

Google Cloud Speech-to-Text

  1. Call Chirp 3 on the us or eu endpoint. It isn't listed for the global location
  2. Reopen streams before the 5-minute limit, or use BatchRecognize for recordings
  3. Downmix stereo unless you need channel labels, since each channel is billed
  4. Set dynamic batch on offline jobs to cut the price from $0.016 to $0.003 a minute
  5. Send the OAuth token in the Authorization: Bearer header, never as ?access_token=, and back off on RESOURCE_EXHAUSTED

Questions

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

Azure AI Speech speech-to-text scores 76.3 (BB) on agent readiness against Google Cloud Speech-to-Text's 67.8 (B), and leads in 3 of 7 scored categories.

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

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

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

Yes. Azure AI Speech speech-to-text has a hosted endpoint at https://eastus.api.cognitive.microsoft.com/speechtotext and Google Cloud Speech-to-Text at https://speech.googleapis.com/v2.

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

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.