Speech-to-Text Functionality (2025.3 Release)
Answered
A customer testing 2025.3 reached out with questions regarding the Speech-to-Text functionality in the notes and activities section.
They noted the following behavior during testing:
- The function does not include punctuation or capitalization automatically.
- When verbally saying punctuation (e.g., “full stop”), it types the literal words rather than applying the punctuation mark.
- The microphone turns off quickly, after a short pause or one sentence, requiring the user to repeatedly press the microphone icon for each line or sentence.
Questions for Product:
- Are there specific guidelines or supported voice commands for using Speech-to-Text effectively?
- Is the microphone timeout behavior (turning off after brief pauses) expected, or should it remain active longer?
- Are there any known limitations or planned improvements for this functionality in 2025.3 or future releases?
Any documentation, tips, or expected behavior notes we can share with the customer would be greatly appreciated! Thanks in advance!
-
I was able to get more information on this from engineering. Tagging @... to update the relevant support article.
- The browser’s built-in speech recognition intentionally returns raw text. It does not perform natural-language post-processing unless the browser implements it (Chrome mostly doesn’t).
- The Web Speech API does not interpret punctuation commands.
- The Web Speech API is not designed for continuous dictation unless you manually restart recognition.
-
I didn't have a good place to put this, so I created a new Speech to Text article, incorporating information from the 25.1 release notes as well as the above. Please send over any feedback! https://supportcenter.ungerboeck.com/hc/en-us/articles/36610999588503-Speech-to-Text-in-the-Text-Editor
Please sign in to leave a comment.
Comments
3 comments
Date Votes