Edge users · Same Web Speech API issue

Caption.Ninja Not Working in Edge Either?

Caption.Ninja told you to switch from Chrome to Edge. You did. It still does not work. You are not alone — Edge has its own SpeechRecognition API bugs on top of the underlying Web Speech API deprecation.

⚠ What you are seeing in Edge
Even after switching from Chrome to Edge, Caption.Ninja transcription drops, hangs, or fails entirely. Microsoft Q&A has confirmed reports of broken SpeechRecognition API after Edge version 111. The Edge workaround is not a fix.
Try StreamTranslate Free → View Pricing

card required for the Free Plan; no payment unless you upgrade. Free Plan with 3 hours every month. Works on any browser.

TL;DR
Edge is Chromium-based and inherits Chrome's Web Speech API deprecation issues. Plus Edge has additional bugs (broken SpeechRecognition API after v111). Switching browsers does not fix the architectural problem. StreamTranslate uses advanced AI server-side speech recognition — does not depend on any browser API. Free Plan with 3 hours every month.

Why Edge does not fix Caption.Ninja

Caption.Ninja recommends Edge as a workaround when Chrome fails. The recommendation makes sense in theory — Edge is Chromium-based, so it inherits the same Web Speech API. In practice, it does not work for three reasons:

  1. Edge inherits Chrome's Web Speech API deprecation. Google deprecated the legacy server-side speech recognition. Edge uses the same API, so the same failures hit there too.
  2. Edge has its own SpeechRecognition bugs. Microsoft Q&A users have documented broken SpeechRecognition API after Edge version 111. So Edge actually has MORE issues than Chrome, not fewer.
  3. The on-device SODA migration affects Edge too. Edge is following Chrome's migration to on-device speech models. Same hanging-in-downloading-state issues.

The fundamental problem is the architecture. Tools relying on browser-native speech recognition (Caption.Ninja, the now-shutdown Web Captioner, Zip Captions) are all hitting the same wall.

What actually works in 2026

The architectural fix is server-side speech recognition with a paid API. StreamTranslate uses advanced AI — professional, 99.9% uptime SLA, browser-agnostic. The browser does not run speech recognition; it just records audio and sends it to our servers. Edge, Chrome, Safari, Firefox — all work the same.

This costs us $0.0043 per audio minute. We pass that cost to users through subscriptions (from $9.99 one-time Stream Pass). Caption.Ninja's free model exists because they offload speech recognition to the user's browser — which is now breaking.

Migration in 60 seconds

  1. Sign up free — 3 free hours every month, card required for the Free Plan; no payment unless you upgrade.
  2. Pick spoken + target languages.
  3. Copy the OBS browser source URL.
  4. OBS → Sources → + → Browser → paste URL → 1920x1080.
  5. Go live. Captions in under 500ms.

Frequently asked questions

Why does Caption.Ninja recommend Edge if Edge has the same problem?
Edge sometimes has slightly different timing for API failures, so it works for some users for a while. But the underlying architecture is the same. Long-term, both Chrome and Edge have the same issue because Google is deprecating the Web Speech API.
Will Caption.Ninja fix this?
Only if Steve Seguin migrates the project off Web Speech API to a paid speech-to-text service — which would mean the free tier is no longer free. He is currently focused on Social Stream Ninja (his chat aggregator).
Is StreamTranslate affected by the Chrome API issue?
No. We use advanced AI server-side. Our speech recognition does not depend on Chrome, Edge, or any browser.
Does StreamTranslate work in Edge?
Yes. Works in every modern browser since we capture audio via MediaRecorder (universally supported) and run transcription server-side.
Will switching to a different free tool help?
No. Every free captioning tool that relies on Web Speech API is affected. Web Captioner already shut down because of this. Caption.Ninja is degrading. The only reliable path is a paid managed service.

Free Plan with 3 hours every month

card required for the Free Plan; no payment unless you upgrade. One URL pasted into OBS. Live in 60 seconds.

Launch StreamTranslate →
Caption.Ninja Not Working? Web Captioner Shutdown vs LocalVocal All Alternatives

Also stream IRL

Also supports IRL with Moblin and the OBS audio plugin, including home and cloud OBS setups such as IRL Toolkit.

Use an OBS receiver for IRL Pro, Larix Broadcaster, PRISM Live Mobile or TVU Go. Cloud providers may need to install the plugin on your server.

Moblin · Moblin Browser Source · Cloud OBS · IRL Toolkit · OBS Studio · IRL Pro · Larix Broadcaster · PRISM Live Mobile · TVU Go · MediaMTX

IRL setup guide · Desktop setup guide