> ## Documentation Index
> Fetch the complete documentation index at: https://docs.screenpipe.com/llms.txt
> Use this file to discover all available pages before exploring further.
# local meeting transcription for Zoom, Meet, and Teams
> Automatically transcribe Zoom, Meet, and Teams meetings locally with screenpipe using Whisper speech-to-text and speaker diarization — no bot, no cloud.
{/* https://screenpi.pe */}
screenpipe automatically transcribes all audio from your meetings, calls, and conversations. local Whisper is the default, and you can also connect an OpenAI-compatible transcription server.
for the full botless meeting workflow - live transcript, speaker cleanup, calendar enrichment, summaries, copy transcript, and APIs - see [meeting intelligence](/meeting-intelligence).
## languages
cloud transcription is multilingual. pick one language in **settings → recording → transcription** to force it, or leave the selection empty (or pick several) for automatic detection — non-English audio is detected and transcribed in its own language, not forced to English.
## setup
audio recording is enabled by default in the desktop app. configure audio devices and transcription engine in **settings**.
* **audio devices**: select which microphones and system audio to capture
* **transcription engine**: choose local Whisper, Deepgram, or an OpenAI-compatible endpoint
## use a local OpenAI-compatible server
screenpipe can send uncompressed WAV audio to any server that implements
`POST /v1/audio/transcriptions`. This keeps screenpipe's capture and search
workflow while letting a separate local runtime own transcription.
[Soniqo speech-swift](https://github.com/soniqo/speech-swift) provides the
endpoint on Apple Silicon. Install and start it on macOS with:
```bash theme={null}
brew install speech
speech-server --port 8080
```
On Linux or Windows, use a
[Soniqo Speech Core](https://github.com/soniqo/speech-core) package that includes
the same transcription endpoint. Download the model bundle, then start the
server:
```bash theme={null}
# Linux
speech download-models
speech serve
```
```powershell theme={null}
# Windows PowerShell, from the extracted package's bin directory
.\speech_download_models.ps1
.\speech-server.exe
```
In **settings → recording → transcription**, choose **OpenAI Compatible** and
set:
* **endpoint**: `http://127.0.0.1:8080`
* **model**: `whisper-1`
* **send raw WAV audio**: enabled
* **API key**: leave empty for a loopback-only server, or enter the server's bearer token
run **connection test** before restarting capture. the server does not need to
list models; screenpipe accepts a manually entered model name.
## search transcriptions
```bash theme={null}
# find discussions about a topic
curl "http://localhost:3030/search?q=budget+review&content_type=audio&limit=10"
# get today's meetings
curl "http://localhost:3030/search?content_type=audio&start_time=2026-02-11T00:00:00Z"
# filter by speaker
curl "http://localhost:3030/search?content_type=audio&speaker_ids=1,2"
curl "http://localhost:3030/search?content_type=audio&speaker_name=John"
```
## speaker identification
screenpipe automatically identifies different speakers. manage them via API:
### improve speaker identification with calendar
connect your **Google Calendar** to significantly improve speaker identification accuracy. screenpipe uses your calendar's attendee list to automatically name speakers during meetings — if a meeting has exactly 2 attendees, the other speaker is auto-identified without manual labeling.
to enable this:
1. go to **settings → connections → Google Calendar**
2. authorize screenpipe to access your calendar
3. during future meetings, attendee names from your calendar will automatically label speakers
this works best for 1:1 meetings and structured calls. for larger meetings (3+ attendees), calendar context is tagged to your notes for later reference.
```bash theme={null}
# get unnamed speakers for labeling
curl "http://localhost:3030/speakers/unnamed?limit=10"
# update a speaker's name
curl -X POST http://localhost:3030/speakers/update \
-H "Content-Type: application/json" \
-d '{"id": 1, "name": "John Smith"}'
# search speakers by name
curl "http://localhost:3030/speakers/search?name=john"
# merge duplicate speakers
curl -X POST http://localhost:3030/speakers/merge \
-H "Content-Type: application/json" \
-d '{"speaker_to_keep_id": 1, "speaker_to_merge_id": 2}'
# find similar speakers
curl "http://localhost:3030/speakers/similar?speaker_id=1"
```
## tips
* use a good microphone
* reduce background noise
* `whisper-large-v3-turbo` is faster with a small accuracy tradeoff; `whisper-large-v3` is the most accurate
* set language to English in settings if you only speak English (faster)
## long meetings and batch sizing
by default, screenpipe batches audio for transcription in chunks. each engine (Whisper, OpenAI, Deepgram) has its own configurable batch-duration limit.
if you notice meetings longer than one hour losing context between batches, you can customize the batch size in settings > advanced > `batch_max_duration_secs`. set to your meeting's typical duration to preserve context across the entire recording.
in smart/batch transcription mode, large meetings may be split across multiple transcription jobs. if you need full meeting context in a single batch, consider:
* switching to **realtime** transcription (transcription happens immediately as audio is captured, trading cost/latency for guaranteed continuity)
* increasing `batch_max_duration_secs` to match your meeting length (capped at each engine's configurable limit)
* using [retranscription API](/api/retranscribe-data) to re-process a full meeting with custom settings
## privacy
* local Whisper and loopback OpenAI-compatible endpoints keep transcription on your device
* audio files stored in `~/.screenpipe/data/`
* audio is sent off-device only when you select Deepgram or another remote endpoint
* disable audio recording in app settings
questions? [join our discord](https://discord.gg/screenpipe).