Subtitling Services for video that has to read cleanly on every screen it reaches.

Subtitling is quoted per project rather than from a published per-minute rate, and the per-minute framing hides most of what moves the figure. The drivers are the language pair and how many qualified subtitlers work in it, whether the job is origination and timing from the video or translation against an existing timed template, speech density and how often speakers overlap, the specification the file has to meet, how many target languages share one timing template, and whether an independent QC pass is included or assumed. Ask for the quote separated into origination, translation, QC and format delivery, and compare providers on that breakdown rather than on a headline minute rate.

There is no single figure, and a rate quoted as a national average describes a market rather than a piece of work. What a subtitler earns moves with the language pair and how many qualified people work in it, whether the task is origination and timing or translation against a supplied template, how demanding the material is, the turnaround, and whether the engagement is one file or a continuing catalog. MoniSa contracts subtitlers per project on terms agreed with the linguist and publishes no rate bands, because a single band would misdescribe most of the pairs the work runs in.

The usual route is a strong pair of working languages, deliberate practice with the constraints rather than with translation alone — reading speed, line length, cue duration, shot changes — and a portfolio of timed files that shows those constraints being respected. Most people learn one subtitling tool, then take QC or template-timing work before origination, because reviewing files teaches a specification faster than writing them does. A sample that reads cleanly at speed counts for more than a certificate. MoniSa recruits subtitlers and subtitle reviewers into its specialist network, and applications go through the careers page rather than a project enquiry.

There is no single best tool, and the useful version of the question is which constraints your work has. Judge a subtitling tool on the delivery formats and frame rates it writes without post-editing, whether it enforces reading speed, line length and minimum cue duration while you type rather than reporting them afterwards, shot-change detection, waveform and frame-accurate navigation, how it handles right-to-left and complex scripts, and whether one timing template can be carried across several target languages. MoniSa works in the tool a platform or partner requires and delivers to their specification rather than to a preferred toolchain.

Subtitles are written for a viewer who can hear the audio but does not follow the language, so they carry dialogue and on-screen text and nothing else. Closed captions are written for a viewer who cannot hear it, so they add speaker identification, meaningful sound effects and music cues, and they are what an accessibility requirement usually means. SDH — subtitles for the deaf and hard of hearing — is the same content delivered in the subtitle format a platform already supports, which is why it ships alongside subtitle tracks rather than as a separate caption stream. The production lane is the same; the output contract is not, so which one is wanted has to be named at scoping.

Runtime and the number of files, the source and target languages, the delivery format and frame rate, the platform or house-style specification where one applies, any existing transcript or timed template, whether the subtitles are burned in or delivered as a sidecar file, whether closed captions or SDH are wanted alongside them, and the release date. With those, the answer is feasibility and a defined quote rather than a range that moves once the files arrive.