Why use the CLI ?
- One command: install, set your key, run
gladia transcribe audio.mp3 - Flexible output: plain text, JSON, SRT, or VTT to stdout
- Set up features: diarization, languages, and model selection (
solaria-1,solaria-3) - Files or URLs: local recordings or remote links
- Pipe-friendly: machine-readable output for scripts and CI
Install
API key setup
Quick start
Common workflows
Commands
Output formats
Use-o or --output:
Transcription options
Global flag:
--gladia-key (if not set via env or ~/.gladia).
Language
--language: limits which languages Gladia considers (hint list, not per-utterance switching).--code-switching: detects language per utterance. Not available withsolaria-3.
Diarization
Use--diarize for who spoke when (e.g. Speaker 0: …).
Shell completion
The installer can set up tab completion. To skip the prompt in CI, setGLADIA_NO_COMPLETION_PROMPT=1.
gladia completion --help for full instructions.
Next steps
Get your API key
Create an API key on the Gladia dashboard
Gladia CLI on GitHub
Source code, issues, and releases
Pre-recorded STT quickstart
Transcription features reference
What to use when
SDK
Build transcription into your product (JavaScript or Python)
Playground
Try models and features in the browser before you integrate
GladiaFlow
Dictate into any desktop app with a hotkey
CLI
Transcribe files or URLs from a terminal or CI