The subtitle encoding converter fixes garbled characters in SRT files caused by encoding mismatches. Older subtitle files — especially those from Windows-based tools — are often saved in Windows-1252 instead of UTF-8, causing accented letters like é, ü, and ñ to appear as gibberish.
Upload Subtitle File
How to Fix Garbled Subtitle Characters
Garbled characters in subtitle files are almost always caused by an encoding mismatch. The file was saved in one encoding (usually Windows-1252) but your video player or tool is reading it as UTF-8. The result is accented characters like é, ü, and ñ turning into multi-character garbage like é, ü, and ñ.
Step 1: Upload the Garbled SRT File
Click the upload area and select your .srt file. The file is read as raw binary bytes so the tool can decode it with the correct encoding from scratch. This is different from how your text editor reads the file.
Step 2: Choose the Source Encoding
Select "Auto-detect" first — the tool will analyze the byte patterns to identify the likely encoding. If auto-detect doesn't fix the problem, try "Windows-1252" manually. This encoding covers the vast majority of garbled subtitle files, especially those from European languages with Romance scripts (French, Spanish, Portuguese, Italian, German).
Step 3: Review the Before/After Preview
The side-by-side preview shows the original garbled text alongside the corrected UTF-8 version. Verify that accented characters are now rendering correctly. If they look wrong, try a different source encoding selection.
Step 4: Download
Click "Download .srt" to save the UTF-8 encoded file. The output file is compatible with all modern video players, subtitle editors, and streaming upload tools.
Frequently Asked Questions
Why do my subtitles show garbled characters like A+, A or weird symbols?
This happens when a subtitle file saved in Windows-1252 or ISO-8859-1 encoding is read as UTF-8. Characters with accents (e, u, n) and special punctuation use different byte sequences in each encoding, causing them to display as garbage when read with the wrong decoder.
How does auto-detect encoding work?
The tool first attempts to decode the file as UTF-8. If the decoded text contains replacement characters (the diamond question mark that appears for unrecognized bytes) or appears garbled, it suggests Windows-1252 as the likely source encoding. Auto-detect is a heuristic -- manual selection may give better results for unusual encodings.
What is the difference between ISO-8859-1 and Windows-1252?
Windows-1252 is a superset of ISO-8859-1 that adds printable characters (smart quotes, em dashes, trademark symbols) in the byte range 0x80-0x9F. Most files described as Latin-1 or ISO-8859-1 are actually Windows-1252. If ISO-8859-1 does not fix your file, try Windows-1252.
Will the converted file work everywhere?
Yes. The output is UTF-8 encoded, which is universally supported by all modern video players, subtitle editors, and web applications. VLC, Premiere Pro, and all major platforms accept UTF-8 SRT files.
Is this tool free and private?
Yes -- free with no signup. Your file is processed entirely in your browser using the built-in TextDecoder API. Nothing is uploaded to a server.