Source
Reach & accessibility — found from sitemap — Livestorm
Checked for Livestorm on 1 Oct 2026
- Page
- https://support.livestorm.co/article/live-captions
- Checked
- 1 Oct 2026, 12:13 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:ecb735d5652e6f5783edfaae413b854746aa2ade9c0da682cadc6967a4d91e3a
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Live captions availability Report an error
“Who can use it? Admin, Member, Viewer On which plans? All”
-
Live captions beta Report an error
“This feature is currently available as a public beta.”
-
Live captions description Report an error
“Live Captions provide real-time transcription of spoken content during your webinars, making events more accessible, inclusive, and engaging for everyone.”
-
Live captions compliance support Report an error
“At the same time, this feature supports accessibility compliance (RGAA/EAA)”
-
Live captions settings location Report an error
“You can enable or disable Live Captions directly from your account settings: Account Settings > Data Protection > AI and data.”
-
AI features toggle Report an error
“Toggle on Enable AI-powered features (this controls transcripts, AI content repurposing, and live captions).”
-
Live captions attendee toggle Report an error
“Each attendee can toggle captions on or off from their own toolbar without affecting others.”
-
Live captions prerecorded limitation Report an error
“Live Captions are not available when sharing pre-recorded videos during your event.”
-
Live captions rtmp limitation Report an error
“Live Captions do not work with RTMP input streams.”
-
Live captions requires event started Report an error
“The event must be started for captions to work.”
-
Company address Report an error
“2093 Philadelphia Pike #7510 Claymont, DE 19703 USA”
-
Company name Report an error
“© 2026 Livestorm Inc.”
5 facts read from this page are not shown because they could not be confirmed on the page as captured.