Dubbing My Videos with KrillinAI: An Honest Run

I make videos, and I wanted to add dubbing to them without spending money on a paid service. KrillinAI looked like a promising free, open-source option, so I decided to give it an honest try. (Fair warning: I don’t write code, so this is the story of someone bumping into walls and slowly working out how to get over them.) I spent roughly four days on this tool, and along the way I hit two big obstacles — one that was entirely my own fault, and one that turned out to be a genuine bug in the app that I ended up patching myself. Here is how it actually went.

The language barrier was mostly on me

The first thing to know about KrillinAI is that its interface is not in English. The buttons, the menus, the error messages — all of it is in a language I cannot read at all. That is not a flaw in the tool; it is simply built for a different audience. But it meant that from the very first screen I was essentially guessing what each button did, and constantly feeding text through a translator just to navigate. If you are in the same boat, expect the setup to feel slower and more uncertain than it would in your own language. None of this is the app’s fault, but it is honest to mention because it shaped my whole experience.

Tracking down a crash that wasn’t my fault

The harder problem came at the dubbing step. Whenever I clicked the button to start dubbing, the app simply died. No error message, no warning, no explanation — it just vanished. This is the most discouraging kind of problem, because the real difficulty isn’t fixing something — it’s figuring out what is even broken in the first place.

I sat down with Claude Code and worked through it patiently, retracing the steps until we could see what was actually tripping the program up. To my surprise, the crash wasn’t something I had done wrong — it was a real bug in the app itself. Once we could finally see the cause, the fix turned out to be just a handful of small lines of code. Getting past a wall like that, as someone with no programming background, was genuinely satisfying.

Where things stand now

The good news is that the parts of KrillinAI that did work impressed me. The subtitles and the translation came out genuinely well — noticeably better than I expected from a free tool, and good enough that I would trust them for real videos.

The frustrating news is that the final dubbing step still hasn’t produced a finished result for me. After clearing the crash, I ran into another wall further down the line, so I have not yet managed to export a complete dubbed video. That leaves me somewhere in the middle: thoroughly impressed by the translation quality, and still determined to get a finished dub out of it.

My takeaway is that KrillinAI is a capable tool with real strengths, but it asks a lot of patience, especially if the interface isn’t in your language. I’m not done with it yet — the subtitle quality alone is enough to keep me coming back, and once I clear the last hurdle I’ll share how the finished dubbing sounds.