The Subtitle Encoding Converter takes the raw text of an SRT file and rewrites its character data in one of two ways: Unicode NFC normalisation, or a reduction to plain ASCII. You paste your captions into the SRT Content box, pick a mode in the Target menu, and get back a complete SRT file - same cue numbers, same timecodes, same line breaks - with only the characters themselves changed. The result downloads as a .srt file ready to drop straight back into your player, encoder or delivery folder.
Mojibake is the everyday name for the problem this solves: a Polish translator sends back a file full of accented letters, a legacy set-top box or an old hardware player renders them as question marks or boxes, and the client rejects the delivery. Localisation vendors, e-learning teams captioning multilingual courses, and anyone archiving subtitles collected from many contributors all run into the same mismatch. A quick pass through a subtitle encoding converter online is usually faster than diagnosing which of five tools in the chain mangled the text.
Technically, the NFC option calls Unicode Normalization Form C, which composes a base letter plus a combining mark into the single precomposed code point that most fonts and players actually have a glyph for. The ASCII option strips every character above U+007F, but first substitutes the typographic punctuation that translators habitually leave in: curly single and double quotes become straight quotes, en and em dashes become a hyphen, and a horizontal ellipsis becomes three dots. Anything else non-ASCII is removed rather than guessed at, so no character is silently replaced with a wrong one.
Nothing is uploaded. The conversion runs entirely in your browser on the text you pasted, so confidential scripts and pre-release episode captions never leave your machine, and even feature-length files of several thousand cues normalise in well under a second.