CaptionSync
About

A subtitle studio that stays on your machine

CaptionSync is a browser tool for the part of subtitle work that is measurable: sync, reading speed, line length, and the small timing errors that make a file look amateur. It was built for editors, translators, students and creators who need to fix a file now, not to subscribe to a platform.

Why it exists

Subtitle work is usually done in a desktop application that costs more than a beginner earns on the job, or in a web tool that uploads the file to a server. The first is a barrier; the second is a confidentiality problem when the file describes unreleased footage. A browser can parse text, compute timing and play a local video without sending anything anywhere, so the tool that does it should not need an account.

CaptionSync is that tool. It reads the file into the memory of the tab, computes everything locally, and lets you export when you are done. There is no backend to store the file, no analytics product reading the text, and no sign-up wall in front of the export button. If you close the tab before exporting, the work is gone, which is the honest trade for not keeping it.

Who it is for

Video editors who receive a subtitle file timed for the wrong cut and need to deliver a fixed one the same afternoon. Translators who inherit a file from another language team and want to check it against the standard before handing it on. Creators who caption their own videos and want the lines to look professional on a phone. Students and researchers who work with transcripts and need to turn one into timed cues without buying software.

What it does not do

CaptionSync does not transcribe audio, translate text, burn subtitles into a video, or generate captions with a language model. Those are different tools with different failure modes, and bundling them would make this one worse. It also does not decide what the client wants: the default limits are the Netflix style numbers, and every one of them can be changed in the audit panel to match a specification.

How it is built

The whole application is static HTML, CSS and JavaScript. The parsers, the timing maths and the audit are pure functions with no network access. The service worker caches the app shell so it runs offline. The only third party script is Google AdSense, which supports the site by showing ads; it does not receive your subtitle text or your video. Fonts are the ones already on your device, so the page does not call a font service.

Try it on a sample first

Three demo files are built in: a drifting documentary, a file full of readability errors, and a clean podcast interview.

Open the studio