How to convert subtitles to UTF-8
TL;DR — Convert subtitle files to UTF-8 so accents, non-English characters, and captions open correctly in editors and video platforms.
Related tool
Subtitle Encoding Fixer
UTF-8 is the safest default encoding for modern subtitle workflows.
Quick answer
If a subtitle file came from an old editor, archive, DVD workflow, or regional subtitle site, convert it to UTF-8 before upload or delivery.
Use the Subtitle Encoding Fixer to decode the original file and download a UTF-8 copy.
Convert, repair, or validate first?
Start with the visible symptom. UTF-8 conversion helps when the text is unreadable, not when the timing structure is broken.
| What you see | Best first step | Why |
|---|---|---|
Broken accents, boxes, or � characters | Use Subtitle Encoding Fixer | The file was probably decoded with the wrong source encoding |
| Text is readable but upload fails | Use SRT Validator or WebVTT Validator | The problem is likely timestamps, cue order, blank lines, or headers |
| SRT uses dots instead of comma timestamps | Use Fix SRT Timestamps | Timestamp syntax is a format problem, not an encoding problem |
| Text has tags or messy spacing after encoding repair | Use Subtitle Cleaner | Clean markup only after characters are readable |
Why UTF-8 is usually the right target
Modern tools and platforms expect UTF-8 more often than older encodings. UTF-8 handles English, accented Latin text, Chinese, Japanese, Korean, and many other scripts in one format.
That makes it safer for:
- browser video captions
- YouTube or Vimeo uploads
- subtitle editing tools
- client handoff
- archive copies
Step-by-step workflow
- Keep a backup of the original subtitle file.
- Open the Subtitle Encoding Fixer.
- Select the source encoding if you know it.
- Upload the file and review the preview.
- Try another source encoding if the preview still looks garbled.
- Download the UTF-8 output.
- Test the output in the target player or editor.
Pick the likely source encoding
If you do not know the source encoding, use language and file origin as clues.
| File origin or language | Try first | Try next |
|---|---|---|
| Western European subtitles | Windows-1252 | ISO-8859-1 |
| Simplified Chinese subtitles | GB18030 | UTF-8 if the file came from a modern editor |
| Traditional Chinese subtitles | Big5 | GB18030 |
| Japanese subtitles | Shift JIS | UTF-8 |
| Korean subtitles | EUC-KR | UTF-8 |
Always compare the preview against real names and non-English lines before downloading the final UTF-8 copy.
Example
If this appears in the broken file:
El niño llegó tarde.Try Windows-1252 as the source encoding. The UTF-8 output should read:
El niño llegó tarde.What this changes
Converting to UTF-8 changes how the text is stored. It should not change:
- cue timing
- cue order
- subtitle format
- line numbers
If you also need to clean markup or spacing, run the file through the Subtitle Cleaner after the encoding looks correct.
Common mistakes
Choosing UTF-8 as the source for a broken legacy file
If the file already looks garbled, choosing UTF-8 as the source may simply preserve the broken text. Try the legacy encoding that matches the file origin.
Converting after upload fails
Encoding is best fixed before upload. Some platforms reject or misread subtitle text silently.
Losing the original
Always keep the original until the converted copy has been checked.
Related guides
- How to fix garbled subtitles
- How to fix subtitles showing boxes
- Subtitle encoding: Windows-1252 vs UTF-8
- How to clean subtitle formatting before upload
Related tools
Use the Subtitle Encoding Fixer
Fix garbled subtitles online by converting SRT, VTT, ASS, SSA, and SMI files to clean UTF-8 text. No signup, no upload, and everything runs locally in the browser.
Open Encoding fixer