Image and video decision

AutoSubtitles

A core, useful subtitle generator+editor is realistic for a single technical user to build (editor + ASR + rendering), but reproducing the polished animated presets, local-in-browser privacy guarantees, multilingual translation features, and production UX at the same level as the hosted product is more work and would remain inferior without continued product polish and design investment.

Visit website
SubscriptionCustom pricing
Initial build36 hours
Monthly upkeep4 hours + $50
Evidence2/3 runs agree

Open-source builds that already do this

Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All AutoSubtitles alternatives, with the arithmetic →

What a replacement has to do

  • Upload video -> generate AI transcript -> edit timing/text -> apply style preset -> export burned-in MP4 or SRT/VTT

What it still won’t have

  • Polished, curated animated presets and designer templates
  • Local-only processing guarantee (audio sent to third-party ASR if using cloud APIs)
  • Instant, serverless no-signup browser flow with production polish and priority support
  • Multi-language translation workflow integrated into editor (unless additional translation API is added)

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

AutoSubtitles does not publish a price we could read, so there is nothing to compare against. What building costs is below.

Money you would actually spend

Keep paying

Subscription price × seats × 12

Build it

AI build APIs + hosting

Time you would spend

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a single-developer subtitle web app using React for UI, Node.js + Express for optional server actions, PostgreSQL (optional) for saved presets, and ffmpeg (server-side) or ffmpeg.wasm (client-side) for video rendering. Implement: 1) drag-and-drop video upload and client audio extraction; 2) speech-to-text integration (configurable wrapper) that returns word-level timestamps; 3) a subtitle editor allowing edit, split/merge, and precise timing adjustment; 4) style presets engine (fonts, color, outline, position, simple word-by-word animation parameters) and ability to upload custom fonts; 5) export pipeline to produce burned-in MP4 and SRT/VTT/TXT downloads. Out of scope: multi-user account management and payment billing, real-time collaborative editing, and enterprise priority support. Include error handling for failed transcriptions and render jobs, automated tests for core flows, and a small README with deployment steps and required API keys.
How we checked4 sources · 2/3 runs agreed · evidence score 60

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 4 cited sources+3
  • Evidence score60

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.

How scoring works →

Cited sources · 4

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded