Speech-to-text for
FileMaker. 100% local.
A single-file transcription tool that runs entirely on your machine. No cloud. No API keys. No data leaving the device. Just drop it in, call it from FileMaker, get text back.
What you can build
Meeting Notes
Record client meetings in FileMaker, get searchable transcripts automatically attached to the record.
Voice Notes
Let users dictate instead of type. Attach transcribed voice memos to any record in your solution.
Call Logging
Transcribe recorded phone calls and link the text to contact records. Fully searchable call history.
Dictation Interface
Real-time speech-to-text inside a FileMaker layout via web viewer. Live text as the user speaks.
Archive Processing
Batch-transcribe years of recorded meetings, voicemails, or interviews. Point at a folder, walk away.
Accessibility
Add captions or searchable text to audio content. Make your FileMaker solutions more accessible.
The alternative is painful
Integrating speech-to-text today
With Transcribr
localhost:8001Insert from URL from FileMakerTranscribe however you need to
One server, four ways to use it. Each maps directly to a FileMaker integration pattern.
Single File
Send an audio file, get a transcript back. Any format — MP3, WAV, M4A, OGG, FLAC and more. All files converted automatically.
Insert from URL call. Returns JSON you parse with JSONGetElement. One script step, one result.Batch Processing
Point it at a folder of audio files. It processes every file asynchronously and reports progress. Each result is stored and retrievable individually.
Watch Mode
Tell it to watch a folder. Any audio file that appears is automatically transcribed — no further interaction required. Set it and forget it.
Real-Time Streaming
WebSocket connection for live audio. Stream from a microphone, get transcription results back as the speaker talks. Sub-sentence latency.
Choose your trade-off
Select the model per request. Use tiny for live streaming, large for critical recordings. Mix and match as you go.
| Model | Speed | Accuracy | Memory | Best For |
|---|---|---|---|---|
| tiny | Good | ~75 MB | Quick drafts, real-time streaming, low-spec machines | |
| base Default | Better | ~150 MB | Good balance for most use cases | |
| small | Good+ | ~500 MB | Improved accuracy when speed isn't critical | |
| medium | Very good | ~1.5 GB | High-accuracy batch processing | |
| large | Best | ~3 GB | Maximum accuracy for critical transcriptions |
What you get back
Every request returns clean JSON you can parse with native FileMaker functions. No plugins required.
{ "transcription": "The full text as a single string.", "segments": [ { "index": 0, "start_time": 0.00, "end_time": 4.52, "text": "The full text" }, { "index": 1, "start_time": 4.52, "end_time": 7.10, "text": "as a single string." } ], "audio_duration_seconds": 7.10, "processing_time_seconds": 1.23, "model": "base" }
Clean JSON. Native to FileMaker.
JSONGetElement, JSONListKeys, and native FileMaker functions only.Technical details
localhost — no internet requiredDon't miss it
We're putting the finishing touches on Transcribr for FileMaker. Drop your email and we'll let you know the moment it's ready.
Notify Me