Skip to content

Fix Corrupted Subtitles & Character Encoding

Fix encoding mismatches in subtitle files and convert between the supported source and target encodings.

Drag & drop your subtitle file here

Drag and drop subtitle files here or click to browse

SRT, VTT, ASS, SSA, LRC, SBV, TTML, SCC, STL, SMI, TXT, JSON
Browser-Based Processing · Files Stay on Device
Core Processing Architecture

Key Features

Engineered for video editors and localization teams. Helps enforce common subtitle timing rules and formatting.

Auto-detect source encoding (UTF-8, GB18030, BIG5, Shift-JIS, EUC-KR, UTF-16)
Convert to UTF-8 or UTF-8 with BOM for modern platforms and Windows-specific players
Convert to UTF-16 LE or UTF-16 BE with BOM
Convert to GB18030/GBK or BIG5 for Chinese systems
Convert to Shift-JIS or EUC-KR for Japanese and Korean systems
Convert to Windows-1252 or ISO-8859-1 for legacy Latin-system workflows
Browser-based processing with no standard-tool file uploads
Live Preview & Execution Pipeline

Fix Corrupted Subtitles & Character Encoding Live Execution Demo

mojibake.srt
Garbled (ANSI/GBK)
00:01.000ä½ å¥½ï¼ä¸çï¼ (Corrupted bytes)
00:04.000åå¹ (Failed code page)
clean_utf8.srt
Recovered (UTF-8)
00:01.000你好,世界!
00:04.000字幕编码自动修复

In-Memory Processing

File parsing, mutations, and time shifts for standard tools run in browser memory without sending subtitle files to our servers.

Millisecond Precision

Millisecond-accurate timecode parsing and arithmetic prevent synchronization drift across desktop and web players.

Fault-Tolerant Engine

Automatic multi-encoding detection and syntax sanitization gracefully handle malformed cues and unexpected linebreaks.

Production Workflows

Common Use Cases

Real-world scenarios across video post-production, course transcription, and global localization.

SCENARIO #1

Fix Garbled Text

Subtitle text that displays as gibberish can often be corrected by detecting the source encoding and converting to UTF-8. Literal question marks usually mean information was already lost and cannot be restored automatically.

SCENARIO #2

Chinese Subtitles

Convert between GB18030 (Simplified Chinese) and BIG5 (Traditional Chinese) encodings, or to universal UTF-8.

SCENARIO #3

Japanese Subtitles

Convert Shift-JIS encoded subtitles to UTF-8 for use in modern media players.

SCENARIO #4

Legacy Compatibility

Some older players require specific encodings. Convert UTF-8 subtitles to the encoding your player expects.

SCENARIO #5

Cross-Platform

Ensure subtitle files display correctly across Windows, Mac, Linux, and mobile devices by standardizing on UTF-8.

SCENARIO #6

SRT to UTF-8

Convert legacy SRT files from GBK, BIG5, Shift-JIS, EUC-KR, or Windows encodings to UTF-8 before publishing or sharing them.

Execution Pipeline

How It Works

Streamlined end-to-end processing pipeline engineered for speed and precision.

STEP 01

Upload your subtitle file

The tool automatically detects its current encoding.

PHASE 01
Next
STEP 02

Format Analysis

Select the target encoding from the dropdown (UTF-8 is recommended for most uses).

PHASE 02
Next
STEP 03

Configuration

Click Convert Encoding to process the file.

PHASE 03
Next
STEP 04

Processing

Download the re-encoded file with correct character display.

PHASE 04
Next
Engine Capabilities

Why Choose AllSubConverter?

Client-Side Privacy

Standard tools run in your browser so standard files are not uploaded to our servers.

Fast Local Parsing

Optimized processing engine parses and converts files directly in your browser.

Generous Batches

Up to 50 MB per file, 200 files or 1 GB total per batch.

Universal Compatibility

Runs in modern browsers across Windows, macOS, Linux, iOS, and Android.

Frequently Asked Questions

Garbled text (mojibake) happens when a file is decoded using the wrong encoding. For example, a GB18030-encoded Chinese subtitle read as UTF-8 will display gibberish. This tool detects the correct encoding and converts to your desired format.

Yes. The tool tries multiple encodings (UTF-8, GB18030, Shift-JIS, BIG5, EUC-KR) and reports which one it detects. You can then convert to any supported target encoding.

Yes, completely free with no registration, no watermarks, and no file uploads.

UTF-8 is the universal standard and works on virtually all modern devices and players. Use UTF-8 unless you have a specific reason to use another encoding.

BOM (Byte Order Mark) is a 3-byte prefix that helps some Windows applications detect UTF-8 encoding. Some older Windows media players require it. Most modern players do not need it.

Yes. Everything runs client-side. No file data is ever sent to a server.

Ready to convert your subtitles?

Fix encoding mismatches in subtitle files and convert between the supported source and target encodings.