SonixLex

One workspace for media workflows

Extraction, transcription, and translation for video, images, and subtitles — from raw files to finished deliverables.

Every media workflow I touched ended the same way: the same video passed through four different tools, subtitles retimed by hand, translations pasted in from somewhere else. SonixLex is my answer to that pipeline — media comes in raw and leaves finished, and the parts that used to demand my attention now run without it.

What it is

A platform organized around videos, images, and subtitles. Videos yield subtitles in two ways — recognition focused on on-screen text, or recognition of spoken audio — or a plain transcription of the dialogue. The subtitles library accepts existing files for editing, translation, and delivery. The image side extracts text from screenshots so it can be translated, cleaned up, or explained. Translation runs through everything, single file or whole batch, with each job configured before it starts: languages, context, and direction. Everything processes in the background, with visible status from start to finish.

What it taught me

Background work changes the UX contract. Once a job runs without anyone watching, progress itself becomes a design problem: what's running, what finished, what needs attention. The absence of feedback is a bug.
"Subtitles" turned out to be two different problems. Text burned into the picture and dialogue spoken over it look like one feature and behave like two — different inputs, different failure modes, different tools.
Batch is a different product. Processing one file tolerates a retry; processing a hundred demands that failure be partial, visible, and recoverable per item.
Translation quality is context, not vocabulary. A good translation knows what kind of content it's translating and who it's for — which is why every job asks for that up front.

Batch translation view listing files with per-file progress

Subtitle editor with a timeline and translated segments side by side

Where it stands

Live , with a free tier to start and Power Sessions for the platform's more advanced work.

What it is

What it taught me

Background work changes the UX contract. Once a job runs without anyone watching, progress itself becomes a design problem: what's running, what finished, what needs attention. The absence of feedback is a bug.

"Subtitles" turned out to be two different problems. Text burned into the picture and dialogue spoken over it look like one feature and behave like two — different inputs, different failure modes, different tools.

Batch is a different product. Processing one file tolerates a retry; processing a hundred demands that failure be partial, visible, and recoverable per item.

Translation quality is context, not vocabulary. A good translation knows what kind of content it's translating and who it's for — which is why every job asks for that up front.