A terrific and pleasant recording system
Our overall experience with ScreenApp has been nothing but pleasant. Their support is terrific, and ScreenApp is a great recording system.
Aaron, Project Manager, review on Capterra
Methodology
This page is the source of truth for every accuracy, speed, and language claim on ScreenApp.io. Numbers come from our internal test corpus, the Groq engineering case study, OpenAI's Whisper benchmarks, and xAI's published Grok Speech-to-Text benchmarks. Provider stack last verified against the codebase: September 2026.
Last updated: September 15, 2026.
Transcription does not bet on a single vendor. ScreenApp routes each job through a provider chain tried in a fixed order, skipping any provider that does not support the requested language. xAI Grok Speech-to-Text leads the chain, followed by Mistral Voxtral, Modulate, Google Gemini, and Groq-hosted Whisper Large-v3 as the deepest fallback.
Mid-chain fallback providers (used when xAI declines or is rate-limited, before falling back further to Gemini and then Whisper): Mistral Voxtral and Modulate. A transcription job never fails because one vendor had an outage.
LLM layer for summarization, chat, and AI analysis: OpenAI GPT-5.6 Luna is the default model for AI chat, summaries, titles, templates and translation. Anthropic Claude Sonnet 5 and Google Gemini 3.1 Flash Lite can be selected for specific jobs instead. Watching video frames and listening to audio always runs on Google Gemini. Live captions use their own provider order, led by Groq-hosted Whisper for speed.
Why multi-provider instead of single-vendor: each provider has a sweet spot. xAI Grok STT has the lowest published error rate on phone calls, which is why it leads. Gemini is the broad catch-all and doubles as the downstream LLM. Whisper on Groq has the most languages, which is why it anchors the fallback chain rather than sitting idle. Routing each job to its best fit beats picking one provider for everything.
Customer audio is never used to train any of these models. Audio is processed and deleted per your account's retention settings. Full data handling on the Trust Center.
Live captions use a separate provider order from batch transcription, led by Groq-hosted Whisper Large-v3 for latency rather than by xAI: Groq, then xAI, Mistral, Modulate, and Google Gemini. This order is chosen for speed during a live session, not for the accuracy fit that leads the batch chain. No accuracy or latency figures for live captions are published yet.
This section is history, not a current benchmark. In 2025, ScreenApp moved from a self-hosted Whisper deployment on AWS to Groq's inference infrastructure. Groq published the case study below; the numbers are from their engineering team's measurements of that pipeline, which was the default at the time. Whisper Large-v3 on Groq is now the deepest fallback, not the default provider (xAI Grok Speech-to-Text leads the chain). No speed or latency figures have been published yet for the current xAI-led provider chain, or for live captions.
| Metric | Before Groq | After Groq | Change |
|---|---|---|---|
| 20-minute transcription job | ~20 minutes | ~15 seconds | 20x faster |
| Per-minute transcription cost | baseline | 1/15th | 15x cheaper |
| Free-to-paid conversion | baseline | +30% | uplift |
| Annual recurring revenue (year-over-year) | baseline | +405% | growth attributed to the speed and cost gains |
Source: ScreenApp + Groq case study (groq.com).
Historical, for the 2025 Groq Whisper pipeline: a 60-minute meeting completes in roughly 3 minutes end-to-end (transcription, diarization, summary generation). A 2-hour video processes in about 6 minutes. These are end-to-end times that include summarization and chaptering, not just raw transcription. No speed figures have been published yet for the current xAI-led chain.
When a YouTube video already publishes a caption track, ScreenApp reads that track instead of transcribing the audio. No speech recognition runs at all, which is why it is fast. The text is written by YouTube, so none of the word error rates on this page describe it. Videos without a caption track go through the AI transcription path above, which is slower and is what our benchmarks measure.
| Path | Imports (n) | Median | p90 |
|---|---|---|---|
| Download + AI transcription (before, Jul 8 to 9 2026) | 61 | 41.1 sec | 159 sec |
| Caption import (after, Jul 16 to 17 2026) | 1,774 | 14.7 sec | 29 sec |
Method: both windows measure the same endpoint (import start to transcript indexed) on the same population, on production traffic. We state the gain as about 3x rather than a precise figure: the before-window sample is small (n=61), which puts the true median speedup somewhere between 1.9x and 3.7x at 95% confidence. The mean (3.58x) is inflated by a long tail of large videos, so the median is the honest central figure.
Two limits worth stating plainly. First, caption import currently serves free-tier YouTube imports; paid accounts still take the download and transcription path, which measured a 60.5 second median before and 44.7 seconds after (that difference is sampling noise, not a change in the product). Second, 14.7 seconds reflects the current implementation, which fetches captions with yt-dlp. Last refreshed: July 2026.
Word error rate (WER) counts substitutions + deletions + insertions per 100 reference words. Lower is better. Baseline figures below come from the published benchmarks for each underlying model; the per-condition rows are from our own April 2026 retest on 18 hours of public-domain audio per language across three conditions: studio (single speaker, treated room), conference (multi-speaker, room mic), and field (handheld phone mic, ambient noise).
Headline figure: 95.8% accuracy. This is measured on the April 2026 provider mix used for that retest, before xAI Grok Speech-to-Text became the default provider. It has not been re-measured on the current default provider.
| Language | Locale | Studio WER | Conference WER | Field WER | iPhone mic WER † | Speakers tested |
|---|---|---|---|---|---|---|
| English (US) | en-US | 4.2% | 7.8% | 12.4% | 14.9% | 4 |
| Spanish (Latin Am.) | es-419 | 5.1% | 9.2% | 14.6% | 17.5% | 3 |
| Spanish (Spain) | es-ES | 5.4% | 9.8% | 15.1% | 18.1% | 3 |
| Portuguese (BR) | pt-BR | 5.8% | 10.1% | 15.8% | 19.0% | 3 |
| Portuguese (PT) | pt-PT | 6.4% | 11.2% | 17.0% | 20.4% | 2 |
| French | fr-FR | 5.9% | 10.4% | 16.2% | 19.4% | 3 |
| German | de-DE | 6.1% | 10.8% | 16.5% | 19.8% | 3 |
| Italian | it-IT | 6.3% | 11.0% | 17.1% | 20.5% | 3 |
| Japanese | ja-JP | 7.8% | 13.5% | 19.8% | 23.8% | 2 |
| Korean | ko-KR | 7.5% | 13.1% | 19.2% | 23.0% | 2 |
| Mandarin (Simplified) | zh-CN | 7.9% | 14.0% | 20.4% | 24.5% | 3 |
| Hindi | hi-IN | 9.2% | 15.8% | 23.1% | 27.7% | 3 |
| Arabic (MSA) | ar | 9.6% | 16.2% | 24.0% | 28.8% | 2 |
| Russian | ru-RU | 6.8% | 11.5% | 17.4% | 20.9% | 3 |
| Indonesian | id-ID | 7.1% | 12.4% | 18.5% | 22.2% | 2 |
† iPhone mic WER is a projection, not a measurement. Computed as Field WER × 1.2 to account for the noise-cancellation, beam-forming, and codec losses that iPhone built-in microphones introduce on top of a handheld phone mic. It has not been measured on a handset; read this column as an estimate only until a measured run is published.
Speaker counts per language are small (2 to 4). The figures above are indicative, not statistically robust, and no confidence intervals are published for them.
Sample files are not published. The corpus is drawn from public-domain sources (see Test methodology above); customer audio is never used, and the individual audio files used for the retest are not posted publicly.
Diarization (attaching a speaker ID to each word) is a flag passed to whichever transcription provider handles the job, not a separate pipeline. It follows the same language-based provider order as transcription: xAI Grok Speech-to-Text, then Mistral Voxtral, then Modulate, then Google Gemini, then Groq-hosted Whisper Large-v3 as the deepest fallback. Routing is automatic; you do not pick.
Whichever provider actually handles the job produces the diarized output in the same response as the transcript; there is no separate content-type router that picks "phone calls" versus "meetings." Speaker labels are available for the languages shown with a dagger in the language list below, up to 25 languages on xAI's published coverage.
Sources: xAI Grok STT and TTS API announcement, Google Gemini.
ScreenApp supports 99 languages. That figure is the union across the whole transcription provider chain (xAI Grok Speech-to-Text, Mistral Voxtral, Modulate, Google Gemini, and Groq-hosted Whisper Large-v3), not a per-provider count: which languages actually route to which provider depends on which of them declare that language. Whisper Large-v3, the deepest fallback, contributes the broadest published language list on its own. A subset also supports word-level speaker diarization: those are the languages marked with † in the list below. xAI publishes diarization coverage for 25 languages in total, so the † marks here are the ones confirmed against our own list rather than the full xAI set. The list below currently runs one entry longer than the published 99 count (it includes Cantonese); we have not yet reconciled which number to publish.
Afrikaans, Albanian, Amharic, Arabic †, Armenian, Assamese, Azerbaijani, Bashkir, Basque, Belarusian, Bengali, Bosnian, Breton, Bulgarian, Burmese, Cantonese, Catalan, Chinese (Mandarin) †, Croatian, Czech, Danish, Dutch †, English †, Estonian, Faroese, Finnish, French †, Galician, Georgian, German †, Greek, Gujarati, Haitian Creole, Hausa, Hawaiian, Hebrew, Hindi †, Hungarian, Icelandic, Indonesian †, Italian †, Japanese †, Javanese, Kannada, Kazakh, Khmer, Korean †, Lao, Latin, Latvian, Lingala, Lithuanian, Luxembourgish, Macedonian, Malagasy, Malay, Malayalam, Maltese, Maori, Marathi, Mongolian, Nepali, Norwegian, Nynorsk, Occitan, Pashto, Persian, Polish, Portuguese †, Punjabi, Romanian, Russian †, Sanskrit, Serbian, Shona, Sindhi, Sinhala, Slovak, Slovenian, Somali, Spanish †, Sundanese, Swahili, Swedish, Tagalog †, Tajik, Tamil, Tatar, Telugu, Thai, Tibetan, Turkish †, Turkmen, Ukrainian, Urdu, Uzbek, Vietnamese †, Welsh, Yiddish, Yoruba.
† indicates languages with word-level speaker diarization via xAI Grok STT. Other languages are transcribed (text-only) without per-speaker attribution.
Whisper's language list source: github.com/openai/whisper. Grok STT language coverage source: xAI Voice docs.
OpenAI GPT-5.6 Luna is the default model for AI chat, summaries, titles, templates and translation. Anthropic Claude Sonnet 5 and Google Gemini 3.1 Flash Lite can be selected for specific jobs instead. Watching video frames and listening to audio always runs on Google Gemini.
Summaries and chat answers are generated from the transcript, not from the original audio. A transcription error carries into the summary and into any answer that depends on that part of the transcript.
AI summaries and chat answers can be incomplete or wrong. For anything a decision depends on, check the summary or answer against the transcript or the original recording rather than taking it at face value.
Timestamps and the full transcript are there for exactly this: to let you jump to the source and verify what was actually said. No formal published evaluation of summary or chat quality exists yet.
ScreenApp is available as the web app, Mac and Windows apps, iOS and Android apps, and a Chrome extension that records tab, screen, mic and camera (Chrome, Edge, Brave, Opera and other Chromium browsers). Ratings and review counts below are pulled at build time from each platform's canonical store listing (the date is named next to each rating). Other listing details (version numbers, sizes, install dates) are point-in-time snapshots checked when this section was last edited; the live store listings are always the authoritative source.
This is the privacy declaration ScreenApp submits to Apple, rendered exactly as it appears on the App Store. Apple's listing is authoritative; if the table below ever diverges from the live App Store page, the App Store page wins and this table should be corrected. ScreenApp declares no tracking data.
| Group | Category | Data types |
|---|---|---|
| Data Used to Track You | None. ScreenApp does not declare any tracking data. | |
| Data Linked to You | User Content | Photos or Videos, Audio Data |
| Identifiers | User ID | |
| Diagnostics | Performance Data | |
| Data Not Linked to You | Identifiers | Device ID |
| Contact Info | Email Address, Name | |
| Diagnostics | Crash Data, Other Diagnostic Data | |
Canonical source: the App Privacy section on the ScreenApp App Store page. Full data handling policies on the Trust Center.
ScreenApp-latest.dmg and always serves the current production build, so there is no separate version string to copy here.io.screenapp.screenapp_mobile.Rating and review counts move daily on the App Store and Google Play. The numbers on this page are point-in-time snapshots, dated above. The live store listings are always the authoritative source; if the divergence ever exceeds 0.2 stars or 10 percent of reviews, please flag it via the Trust Center contact form and we will refresh sooner.
Two named customer reviews drawn from the public reviews page, one from Capterra and one from the Chrome Web Store. They are hand-picked samples, not a random draw and not the full corpus, so do not read them as an average. The aggregate ratings are whatever the App Store and Google Play report (4.0 stars across 111 ratings on iOS, 3.9 stars across 775 ratings on Android, pulled September 15, 2026), not the average of the two reviews below.
Our overall experience with ScreenApp has been nothing but pleasant. Their support is terrific, and ScreenApp is a great recording system.
Aaron, Project Manager, review on Capterra
I have tried at least 6 different ways to transcribe meetings and get summaries: Notion with AI, HiNotes with HiDock as hardware, Plaud with different hardware, Teams agents. Every tool did a part of the job, but not one of them delivered on all my requirements. ScreenApp goes far beyond my expectations.
Andreas Kroll, review on the Chrome Web Store, May 29, 2026
The numbers below are real production counts, pulled at build time from the same MongoDB cluster the dashboard reads from. They are not marketing rollups, not rounded, and not estimated. Refresh cadence: every deploy. Last pulled: September 15, 2026.
5,849,229
recordings processed
transcribed and analysed in production
2,153,669
speakers diarized
unique speaker turns identified across the corpus
306,572
AI Q&A sessions
questions asked against transcribed media
135,891
voice dictations
captured via browser, iOS, and Android
68,634
meeting-bot sessions
across Google Meet, Microsoft Teams, and direct integrations
403,335
analysed video metadata sets
meeting type, speakers, companies extracted
Recent activity (indexed proxy via videometainfo.createdAt): 1,810 recordings analysed in the last 24 hours, 8,000 in the last 7 days, 33,081 in the last 30 days. Daily rate of roughly 1,103 analyses per day.
Why videometainfo and not recordings directly: recordings._id is a UUID, so we cannot do indexed time-range queries on it. Each videometainfo doc maps 1:1 to a recording via the unique recordingId index, so the time-windowed counts above are a faithful proxy. Methodology and the open query module: below.
8,291,249 accounts registered as of September 15, 2026. Number reflects unique verified-email accounts in our production database, pulled at build time from the same source the dashboard reads from. The figure on this page refreshes every deploy, not on a quarterly cadence.
We do not publish round-number marketing claims like "2 million users" without the verifiable underlying count, on this page or elsewhere. If you ever see an inflated or undated user-count claim on a ScreenApp page, that's a content quality issue and we'd like to know: contact us via the Trust Center.
Every numeric claim on this page and across screenapp.io that depends on production data follows the same pipeline. Numbers are not curated, edited, or rounded for marketing.
GET /v2/site-data) that runs a small set of indexed aggregations and returns scalar counts. The query module is open inside the same repo at scripts/site-data-queries.ts.data/stats.db) and read synchronously by every page at static-generation time. Within a single deploy the numbers do not drift; between deploys they refresh.If you ever spot a number on the site that disagrees with a figure on this page, please flag it via the Trust Center. A divergence is a bug.
Two ways to use ScreenApp without paying upfront:
Current pricing and feature breakdown on the pricing page. What we do NOT offer: a recurring monthly free tier with X minutes/month, a "no credit card" trial of the paid plan, or unlimited free recordings. If you see those claims anywhere on this site, that's a content quality issue, please flag it via the Trust Center and we'll fix the source page.
SOC 2 Type 2 audited annually. 22 internal policies covering access control, data classification, secure development, and incident response. Continuous control monitoring.
Full live security posture, downloadable SOC 2 Type 2 report, and pre-filled security questionnaire at our Trust Center (trust.inc/screenapp).
Numbers on ScreenApp pages should match this page. If you find a feature page that contradicts these figures, that's a content quality bug we want to fix. Report it via the Trust Center contact form so we can check and correct the source page.
Paste a URL or upload an audio or video file. See the actual accuracy on your content, not benchmarks on someone else's.
No charge for 7 days, cancel anytime • Registrati senza carta di credito