stable-ts vs Whipscribe (2026): the timestamp fix-up library, honestly compared

What stable-ts actually is

stable-ts is a Python library that wraps an OpenAI-Whisper-compatible inference call (vanilla openai-whisper, faster-whisper, or whisper.cpp via the appropriate adapter) and replaces the timestamp pathway with a more careful one. The headline ideas, drawn from the README and the issues tracker on GitHub:

1. Dynamic programming over cross-attention weights. Whisper's decoder produces cross-attention maps as a side effect of generating each token. Those maps already contain information about where in the audio each token was attending. stable-ts runs a DTW-style (dynamic-time-warping) alignment over those weights to recover monotonic, well-bounded word timestamps — instead of relying on Whisper's special <|t|> timestamp tokens, which are produced by a separate decoding head and drift on long segments.
2. Regularization for monotonicity and silence. The DP pass enforces that word boundaries advance forward in time (no overlapping words, no zero-length words), and it consults voice-activity detection to shrink boundaries that bleed into silence. The output is a per-word timeline that looks like what a human captioner would mark.
3. Regrouping options. stable-ts ships refine and regroup primitives — declarative rules that let you split, merge, or re-balance segments by length, character count, gap, or punctuation. This is the part of subtitle authoring that turns an ASR transcript into broadcast-grade captions: max 32 characters per line, max 2 lines per cue, no orphaned punctuation, breaks at clause boundaries.
4. Denoising integration. Recent versions wire in optional denoising (denoiser="demucs" and friends) so the audio fed into Whisper is cleaner before the alignment pass runs. Useful for music-bed podcasts, lavalier-mic field recordings, and anything with consistent room noise.

The library is MIT-licensed, ~2.2k GitHub stars, single maintainer, last push 2025-10-29 as of this writing. It is a sharp tool, well-scoped, and the audience is exactly the people who are going to read the source.

What stable-ts is not

The library does one thing. It does not do most of the other things a transcription pipeline needs:

• No speaker diarization. stable-ts only operates on the alignment between transcript and audio. If you need "Speaker 1 / Speaker 2" labels you bolt on pyannote-audio or use whisperX as your inference layer instead.
• No URL ingestion. stable-ts takes a local audio path. YouTube, Spotify share links, Zoom-cloud recordings — that's your fetch step (yt-dlp + ffmpeg + retry logic).
• No exports beyond what's in the box. SRT, VTT, and JSON are supported out of the library; DOCX, plain text reflowed for reading, structured XML for broadcast captioning systems — those are yours to write.
• No GPU box. stable-ts inherits whatever inference engine you point it at. CPU works for tiny models; serious throughput needs a GPU you operate yourself.
• No queue, no auth, no UI. It's a library, not a product.

None of that is stable-ts's fault — it is a focused library doing exactly what it advertises. But the gap between "I have pip install stable-ts running in a notebook" and "I have a captioning pipeline in production" is real, and the gap is most of the engineering work in any transcription product.

The thing it actually fixes (and why captioners care)

If you have ever generated SRT subtitles from raw Whisper output and watched them play back next to the video, you have probably noticed the drift. A word lights up half a second after the speaker says it. Two words run into a single cue with one timestamp covering both. The last word of a segment hangs around for 800 milliseconds of silence after the speaker stops. For a transcript meant to be read, none of this matters. For karaoke, sing-along apps, broadcast captions, or short-form vertical clips where every cue is on screen for two seconds, all of it matters.

The drift is real because Whisper's timestamp tokens are predicted by a separate head with its own loss, and that head is allowed to be slightly wrong if the text token loss goes down. stable-ts ignores those tokens and reads the cross-attention directly — and the cross-attention is what the model was actually doing when it produced each word. The result is timestamps that match what a human would mark, with sub-100ms agreement on clean audio in the community benchmarks reported on the project's issues tracker and in subtitle-pipeline write-ups on Reddit's r/MachineLearning and r/whisper.

The honest side-by-side

Different surfaces, different jobs. The model layer underneath can be the same Whisper checkpoint in both cases.

Worked example: a YouTube creator publishing 10 videos a month

This is the most common shape we see when someone Googles "Whisper SRT subtitles." A creator with a regular publishing cadence, a need for accurate captions on every upload, and a backlog they'd like to not think about. Let's run it both ways.

The point isn't that stable-ts is overkill — the captioning quality you get from a well-tuned stable-ts pipeline is the best you can get from open-source Whisper, full stop. The point is that for the YouTube-creator use case, the marginal precision over Whipscribe's whisperX-based timing is invisible to viewers, and the engineering cost is real. If you would notice a 50ms timestamp error in your captions, build the stable-ts pipeline. If you wouldn't, use the hosted product.

When stable-ts is the right call

1. You're building a captioning or subtitle pipeline as a product. Karaoke apps, sing-along language-learning tools, broadcast caption authoring software, music-video lyric sync. The precision matters because it's the product. stable-ts is the right tool — embed it, tune the regrouping rules to your domain, and own the pipeline.
2. You have an in-house ASR pipeline already and want a drop-in timing fix. You run faster-whisper on your own GPUs, you ship transcripts in production, and your customers have started complaining about karaoke-style cue alignment. pip install stable-ts, swap your transcribe() call, ship the improvement.
3. You need offline operation with no audio leaving the device. Field journalists, hospital settings, classified work. stable-ts runs locally; the hosted product does not.
4. You want maximum control over cue formatting. Broadcast TV captions have specific rules (CEA-608/708, EBU-TT, BBC subtitle guidelines) that need exact character counts, line breaks, and reading speeds. stable-ts's regroup chain is the most expressive caption-formatting API in the open-source Whisper ecosystem.

When Whipscribe is the right call

1. You publish content and need transcripts. YouTube creators, podcasters, journalists, course creators. The transcript and the SRT are a means to an end (show notes, search, accessibility). You don't need broadcast-grade timing; you need a transcript by tomorrow.
2. You need diarization out of the box. Multi-speaker interviews, panel discussions, focus groups. stable-ts doesn't do this; Whipscribe does, on every plan.
3. You're calling transcription from an AI agent. A Claude or ChatGPT agent that needs to transcribe a URL as part of a workflow doesn't have a GPU, doesn't have a Python pipeline, and shouldn't have one. Whipscribe ships an MCP server (mcp.whipscribe.com) for exactly this case.
4. You value an evening more than $29. The honest version. The setup time on stable-ts (and any self-hosted ASR pipeline) is real, and most people who can be served by a hosted product should use one.

Credit where credit is due

stable-ts exists because jianfch wrote and maintains it under MIT, mostly as a single-maintainer project, and has done the careful work of making Whisper's timestamps trustworthy for caption pipelines that read them. The technique — DP alignment over cross-attention — predates the library in the speech-research literature, but jianfch's contribution is the well-engineered Python wrapper that the rest of us can pip install. If you ship a captioning product on top of it, sponsoring the project on GitHub is a reasonable thing to do; the work being done there is real.

Frequently asked