TTS Debug
by dmazzoni@google.com more by this developer →
#75,997 of 263,655 by installs on Chrome · #44,947 of 162,012 in productivity
First seen by this census 09/01/2026 — the store does not publish a creation date
Last updated 01/18/2018
Tracked since 09/01/2026
Compare with another extension
Category: productivity / developer
Languages: English (United States)
Description
Tool for developers of Chrome TTS engine extensions to help them test their engines are implementing the API correctly.
Alternatives to TTS Debug
| Name | Users | Rating | |
|---|---|---|---|
ImTranslator: Translator, Dictionary, TTS
|
900,000 | 4.4 | compare |
Google Analytics Debugger
by Google Analytics
|
600,000 | 4.2 | compare |
Odoo Debug
|
100,000 | 4.7 | compare |
Analytics Debugger
|
100,000 | 4.6 | compare |
Translate - Translator, Dictionary, TTS
by 208 Witmer St Los Angeles, CA 90026 USA
|
100,000 | 4.5 | compare |
HttpWatch: HTTP Debugger
by NEUMETRIX LIMITED
|
90,000 | 2.4 | compare |
Adobe Experience Platform Debugger
by Adobe Inc.
|
80,000 | 2.9 | compare |
Text to Speech TTS AI | Readvox
by Fenvox LLC
|
50,000 | 4.2 | compare |
Xdebug Helper by JetBrains
by JetBrains
|
50,000 | 4.8 | compare |
TagHound - Analytics/GTM/Pixel Debugger
|
50,000 | 4.8 | compare |
Growth
Change in installs. This store publishes the count rounded to one or two significant figures, so it does not move when the listing grows - it moves when the rounding rolls over. The figures below are therefore what was actually observed between the two crawls named in "measured over", not scaled to the window, and the percentage is of that same rounding step - so a small listing crossing a bucket shows a very large one. A window needs a full period of history before it reports anything.
| Per | Growth | Growth % | Actual change | Measured over |
|---|---|---|---|---|
| day | Not enough history yet | |||
| week | Not enough history yet | |||
| month | Not enough history yet | |||
| year | Not enough history yet | |||