TL;DR: Video-Subtitle-Extractor (VSE) is a free, open-source tool that OCRs hardcoded (burned-in) subtitles out of a video into an SRT file. It's genuinely powerful — 87 languages, local OCR with no API keys, batch extraction, and GPU acceleration — and for a developer with an NVIDIA GPU who wants free bulk extraction, it's hard to beat. But VSE is Python-based, NVIDIA/CUDA-oriented (slow on a Mac's CPU), and it does one thing: extract. It does not translate the subtitles, burn them back in, or give you an editor to fix them. GeekLink is a turnkey macOS app that does the same OCR extraction and then keeps going — AI translation, an editing pass that flags lines it's unsure about, and burn-in — all in one app with no Python setup. If you're a developer on an NVIDIA GPU and only need raw extraction for free, VSE is excellent; if you're on a Mac and want to go from burned-in subtitles to a translated, corrected, re-burned video without touching a command line, GeekLink does the whole pipeline.
Want burned-in subtitles extracted, translated, and burned back in — no Python? GeekLink runs the whole OCR pipeline locally on your Mac. Free tier, no account required.
Download FreeWhat is Video-Subtitle-Extractor (VSE)?
Video-Subtitle-Extractor (VSE) is a free, open-source (Apache 2.0) tool that extracts hardcoded subtitles from video and outputs an SRT file, using local OCR with no third-party API. With 9,000+ GitHub stars it's the most popular tool in this category, especially in the Chinese-speaking community.
VSE detects the subtitle region frame by frame, reads the on-screen text with a local OCR model, filters out non-subtitle text, de-duplicates repeated lines, and writes an SRT (or TXT). It supports 87 languages, offers Fast / Auto / Precise modes that trade speed for accuracy, and can batch-extract multiple videos as long as they share the same resolution and subtitle region.
Its real strength is that everything runs locally and free, with GPU acceleration on NVIDIA hardware for higher accuracy and speed. It also pairs with a sister project (video-subtitle-remover) if you want to erase the old burned-in text afterward. VSE is, by design, an extraction tool — it turns burned-in text into an SRT, and that's where its job ends.
The tradeoffs are the flip side of being an open-source Python project. It's oriented around NVIDIA CUDA, so on a Mac it falls back to CPU and runs slowly. Setup can mean downloading a release build or, if that fails, installing a conda environment from source. Small UX sharp edges exist too — for example, video and program paths can't contain spaces or non-ASCII characters. For a technical user these are minor; for a non-coder they're real friction.
GeekLink vs VSE: How do they compare?
They overlap on exactly one thing — local OCR of burned-in subtitles into an editable file. Everything after that (translation, editing, burn-in) is GeekLink-only, and everything about being free and scriptable on any GPU is where VSE wins.
| Feature | GeekLink | Video-Subtitle-Extractor (VSE) |
|---|---|---|
| Burned-in subtitle OCR → editable SRT | Yes — core feature | Yes — core feature |
| Platform | macOS (native, Apple Silicon) | Windows / Linux / macOS, but tuned for NVIDIA GPU (Mac = CPU, slow) |
| Setup | Download the app, open it — no Python | Download release, or install a conda/Python environment from source |
| Interface | Native GUI with editing timeline | GUI for extraction (no editor to correct results in-app) |
| Languages (OCR) | Covers major CJK + Latin + more | 87 languages |
| Batch extraction | Yes — multiple videos in one run | Yes — but requires identical resolution & subtitle region across the batch |
| AI translation of the extracted subtitles | Yes — Claude 3.5 Haiku, GPT-4o, GPT-4o mini, DeepSeek (context-aware, 40+ pairs) | No — extraction only |
| In-app editing / flag uncertain lines | Yes — editor marks low-confidence lines to review | No — text substitutions only via a manual JSON map |
| Burn subtitles back into the video | Yes — styled burn-in | No — outputs SRT/TXT only |
| Remove old burned-in text / watermark | No | Via a separate sister project (video-subtitle-remover) |
| Price | Free tier; paid $12.99/mo, $99/yr, or $169 one-time lifetime | Free, open-source (Apache 2.0) |
Key takeaway: this is "free extraction engine" vs "turnkey extraction-to-delivery pipeline." VSE and GeekLink both read burned-in text off the frames, and VSE does it for free across 87 languages. But VSE stops at the SRT. GeekLink is built for the person who needs that SRT translated, corrected, and burned back into a finished video — on a Mac, without installing anything.
How much does each cost?
VSE is completely free and open-source under Apache 2.0 — there is no paid tier, and nothing is metered. That's a real advantage: if extraction is all you need and you have the hardware and comfort to run it, your cost is zero.
GeekLink has a permanent free tier (full OCR, speech recognition, editing, batch, SRT/ASS export; free exports carry a small GeekLink credit) plus flat paid plans for the translation and burn-in pipeline:
- Monthly — $12.99/month
- Annual — $99/year (~$8.25/month), includes 1M AI translation tokens (~1,500 minutes)
- Lifetime — $169 one-time (early bird) / $199 regular, includes 1M AI translation tokens, no subscription
- Extra AI translation tokens — $6.99 per 1M tokens (overage)
You're not really paying GeekLink for OCR — you're paying for everything VSE doesn't do. The OCR extraction itself is available on GeekLink's free tier. The paid plans cover the AI translation and the turnkey, no-setup Mac experience. If your only need is free extraction, VSE is the cheaper answer; if you'd otherwise be stitching VSE together with a separate translator and a burn-in tool, GeekLink's flat price buys you the whole chain in one app.
When should you use VSE over GeekLink?
VSE is the better choice in several situations:
You want free, unmetered extraction and you're comfortable with Python. VSE costs nothing and has no token limits. If you can run a release build or set up a conda environment, you can extract as much as you like.
You have an NVIDIA GPU. VSE is built around CUDA acceleration, so on a capable NVIDIA card it extracts quickly and accurately in its precise modes. GeekLink is macOS-only, so it's not an option on a Windows/Linux GPU rig.
You need one of VSE's 87 languages that's outside common CJK/Latin sets. VSE's language coverage is very broad.
You want an open-source tool you can script or modify. VSE is Apache 2.0 — you can automate it, integrate it into a pipeline, and change it. GeekLink is a closed desktop app.
When is GeekLink the better choice?
GeekLink is the stronger pick when extraction is only the first step, or when you're not going to touch a command line.
You're on a Mac and want it to just work. GeekLink is a native macOS app: download it, open it, draw a box around the subtitle area, run. There's no Python, no conda, no CUDA, and no "paths can't contain spaces" gotcha. On Apple Silicon it's built to run locally without needing an NVIDIA GPU.
You need the subtitles translated, not just extracted. This is the biggest gap. VSE outputs the original-language SRT and stops. GeekLink can translate that SRT with Claude 3.5 Haiku, GPT-4o, GPT-4o mini, or DeepSeek — with context across lines, not word-by-word — right after extraction.
You want to review and fix the OCR before you ship it. OCR is never perfect on stylized or busy footage. GeekLink gives you an in-app editor that flags the lines it's least sure about, so you check the handful worth checking instead of proofreading everything. VSE's only correction mechanism is editing a JSON substitution map by hand.
You need the finished video, not just a file. GeekLink can burn the corrected, translated subtitles back into the video with styling. VSE gives you an SRT/TXT; burning it in is a separate job with a separate tool.
Can VSE translate or burn in the subtitles it extracts?
No. VSE extracts burned-in subtitles into an SRT (or TXT) and stops there — it has no translation feature and no burn-in feature. Its scope is deliberately the "read the picture text into a file" step. If you need the result in another language, you take VSE's SRT to a separate translation tool; if you need it burned back into the video, you take it to a separate burn-in tool (or a video editor).
For a technical user assembling a pipeline, that modularity is fine — VSE for OCR, something else for translation, ffmpeg or an editor for burn-in. The cost is that you're maintaining three tools and moving files between them, and the translation step usually isn't context-aware unless you wire in an LLM yourself.
GeekLink collapses that chain into one app: OCR the burned-in text, translate it with an LLM that sees the surrounding lines, correct the flagged lines in the editor, then burn the result back in — without ever leaving the app or writing a script. The comparison isn't "which OCR is better" so much as "do you want an OCR engine, or the whole extract-translate-deliver pipeline."
The two can even be complementary: a developer could use VSE on an NVIDIA GPU for fast free bulk extraction, then hand the SRTs to GeekLink on a Mac for AI translation and styled burn-in. Different tools, different stages.
Frequently Asked Questions
Is GeekLink a paid alternative to Video-Subtitle-Extractor?
Partly. GeekLink's burned-in subtitle OCR is available on its free tier, so basic extraction doesn't cost anything. The paid plans ($12.99/mo, $99/yr, or $169 lifetime) cover AI translation and the turnkey Mac experience. VSE is fully free and open-source, but it only extracts — it doesn't translate, edit, or burn subtitles back in.
Does Video-Subtitle-Extractor run well on a Mac?
It runs on macOS, but VSE is built around NVIDIA CUDA acceleration, so on a Mac it falls back to the CPU and extracts slowly. GeekLink is a native macOS app built for Apple Silicon, so it runs locally at full speed without needing an NVIDIA GPU, and it installs as a normal app with no Python or conda setup.
Can VSE translate the subtitles it extracts?
No. VSE outputs the original-language SRT or TXT and has no translation feature. To translate you'd take that file to a separate tool. GeekLink translates the extracted subtitles in-app with Claude 3.5 Haiku, GPT-4o, GPT-4o mini, or DeepSeek, using context across lines.
Can VSE burn the subtitles back into the video?
No. VSE only produces a subtitle file; burning it in is a separate step with another tool. GeekLink can burn the corrected, translated subtitles back into the video with font, color, and position styling, in the same app.
Which is more accurate at OCR?
Both use strong local OCR. VSE can be very accurate in its precise mode on an NVIDIA GPU, at the cost of speed. Accuracy on stylized or busy footage varies for any OCR tool, which is why GeekLink adds an editor that flags the lines it's least confident about so you can quickly review them — VSE's only correction path is a manual JSON substitution map.