elevenlabs-scribe

ElevenLabs Scribe speech-to-text

Use this skill when a media-production task needs ElevenLabs Speech to Text (Scribe) for transcripts, caption timing, speaker-labeled interview logs, podcast edit prep, accessibility subtitles, localization handoff, call/interview analysis, or transcript cleanup. Do not use it as a text-to-speech, dubbing, voice cloning, or translation skill; Scribe produces text, timing, and metadata from existing audio/video. Use dubbing or TTS skills only after the transcript is verified and the user has rights to transform the source.

Volatile facts below were verified from official ElevenLabs documentation on 2026-07-10. If building against the live API, re-check model names, limits, pricing, residency endpoints, and retention options before irreversible production work.

Source-grounded facts

Current models and fit

• Use scribe_v2 for batch/file transcription. ElevenLabs documents Scribe v2 as supporting 90+ languages, word-level timestamps, speaker diarization up to 32 speakers, dynamic audio tagging, keyterm prompting, entity detection, and smart language detection.
• Use scribe_v2_realtime only for live streaming use cases such as agents, live meetings, or interactive monitoring. It is a WebSocket STT service, not the normal path for post-production captions from a finished file.
• Treat scribe_v1 as retired/unsafe for new work. The API schema still listed scribe_v1 as an allowed value when checked, but the official changelog announced Scribe v1 removal on 2026-07-09. Prefer scribe_v2 and flag any Scribe v1 dependency as a migration issue.

Inputs, outputs, and request shape

Batch endpoint: POST https://api.elevenlabs.io/v1/speech-to-text with multipart form data.

Inputs:

• Provide exactly one file input path or URL source. The current API reference describes file upload and source_url; cloud_storage_url is deprecated in favor of source_url.
• Audio and video files are accepted. Official docs list common audio formats including AAC, AIFF, OGG, MP3, OPUS, WAV, FLAC, M4A, WebM, and common video formats including MP4, AVI, MKV, MOV, WMV, FLV, WebM, MPEG, and 3GPP.
• Documentation conflict on file size: the API reference states uploaded files must be less than 5.0 GB, while the overview/key-facts page states a 3 GB maximum. For production planning, use 3 GB as the conservative preflight limit unless a current API test or account documentation confirms a larger limit.
• Documentation conflict on duration/multichannel: the overview FAQ says standard mode supports up to 10 hours and combined multichannel duration must be under 10 hours, while key facts says multichannel maximum duration is 1 hour. Treat 1 hour as the conservative multichannel planning limit for unattended production and chunk longer files.