Batch File Encoding Converter

Batch convert the encoding format of text files, supporting conversion between multiple encodings such as UTF-8, GBK, and GB18030, automatically detecting the source encoding to solve garbled text issues.

Bug report

Browser execution mode: Your data is processed in your browser and is not uploaded to the server.

Speed and Stability: Processing speed depends on your device and browser. For large batch work, the desktop version may be more stable.

Loading tool, please wait...

If the online tool fails to load or run, try the desktop tool.https://tools.yikeaigc.com/

Tool Usage

Return to old version

A desktop version is available with more powerful, stable features. Open desktop version

1Select text files to convert

Click to choose files, or drag and drop them here

Supports TXT, CSV, subtitles, HTML, JSON, XML, Markdown, logs, and code-like plain text files. Multiple files allowed.

2Sample data

3File list

No files added yet. Choose files or load sample data first.

1Choose a common conversion preset

2Source and Target Encoding

Source Encoding

Auto-detect works for most text. If the preview is garbled, choose the source encoding here.

Target encoding

Target encoding controls the downloaded file bytes. Use UTF-8 BOM for CSV in spreadsheet apps.

3Detection Strategy

Auto-detect Preference

Prefer Chinese text leans toward GB18030 at low confidence, ideal for common Chinese mojibake fixes.

Encoding Library Status

Checking local encoding libraries...

Encoding conversion, detection, and ZIP packaging all use locally loaded frontend libraries.

1BOM and Line Endings

Output BOM

When UTF-8 BOM is selected as the target encoding, a UTF-8 BOM will be added.

Line endings

For cross-system collaboration, choose LF or CRLF. Subtitles and code files often use LF.

2Text cleanup and safety checks

Remove source file BOMRemove the leading BOM character after decoding to avoid invisible characters at the start. Remove trailing whitespaceBatch remove spaces and tabs at the end of each line. Skip same-encoding filesSkip conversion when source and target encodings match. Useful for mixed-encoding folders. Skip suspected binary filesSkip files with unreadable control bytes to avoid misprocessing images, archives, and similar files. Keep empty filesEmpty text files will be written to the result package with the original filename. Show processing logLog detected encoding, skip reasons, and output filenames during conversion.

3Preview and download settings

Preview characters

Preview shows only part of the content and does not affect full file conversion.

ZIP filename

Multiple files will be downloaded as a ZIP. Output filenames match originals by default; duplicates get numbers.

1Preview before conversion

Preview file

Preview action

Source file contentWaiting for files

Please add files first.

Converted text previewUTF-8

Check the text here after setup.

2Start processing

Preparing...0%

Success0

Skipped0

Failed0

Result size0 B

3Result file

Instructions

Software Usage Instructions

Add files: Click the upload area or drag files onto the page. Plain text files such as TXT, CSV, SRT, HTML, JSON, XML, MD, LOG, INI, and code files are supported. When multiple files are selected, the first 20 are shown in the list, but all files are included during processing.
Use sample data: Load UTF-8 text, GBK CSV, or subtitle samples to get familiar with the detection, preview, and conversion process.
Set encoding scheme: Select a common scheme in the “Encoding” tab, or manually set the source and target encodings. Source encoding supports automatic detection; target encoding supports formats such as UTF-8, UTF-8 BOM, GBK, GB18030, Big5, Shift_JIS, and UTF-16.
Configure processing options:
- BOM settings: Add a BOM according to the target encoding, or specify UTF-8 BOM, UTF-16 BOM, or no BOM.
- Line break settings: Keep as is, or normalize to LF, CRLF, or CR.
- Text cleanup: Remove source file BOM, trim trailing whitespace, skip suspected binary files, and keep or skip empty files.
- Download parameters: Set the number of preview characters and the ZIP archive file name.
Preview content: After entering the “Convert” tab, select a file to view the source content and converted text preview. If the preview appears garbled, return to the “Encoding” tab and manually specify the source encoding.
Start conversion: After confirming the files, encodings, and options, click “Start Conversion and Generate Results”. The processing log will show each file’s source encoding, target encoding, output file name, and processing status.
Download results: A single file can be downloaded directly; multiple files will be packaged as a ZIP. The output file name matches the original file name by default. If duplicate names occur, a number will be automatically appended to the file name.

FAQ

A: You can first use automatic detection and check whether the text appears correctly in the preview area. If garbled text appears, try common encodings such as GBK, GB18030, UTF-8, Big5, and Shift_JIS manually, then convert after selecting the encoding that displays the content correctly.

A: UTF-8 is suitable for cross-system and web content; GBK is common in older Chinese Windows software; GB18030 covers a wider range of Chinese characters. For general text exchange, converting to UTF-8 is recommended; to maintain compatibility with older software, choose GBK or GB18030 according to the software’s requirements.

A: Choose UTF-8 BOM when a CSV file needs to be opened directly in spreadsheet software and display Chinese correctly. For code, web templates, or configuration files, UTF-8 without BOM is usually preferred to reduce compatibility issues.

A: First load the CSV file and use auto-detection to check the preview. If the original file comes from an old system, try GBK or GB18030 as the source encoding; choose UTF-8 BOM as the target encoding and set line endings to CRLF to help spreadsheet software recognize it.

A: By default, the original file name is kept unchanged. If multiple files have the same name, the tool automatically adds a number after the file name, such as data.csv or data(2).csv, to prevent files in the ZIP archive from overwriting each other.

A: Common causes include incorrect source encoding detection, the file not being plain text, corrupted file content, or the target encoding being unable to represent certain characters. Use the preview feature to confirm the source encoding first, and switch to UTF-8 as the target encoding if needed.

A: Common plain text files are supported, such as TXT, CSV, TSV, SRT, VTT, HTML, XML, JSON, MD, LOG, INI, YAML, SQL, JS, CSS, PHP, Python, and more. You can batch convert, preview content, normalize line endings, handle BOM, remove trailing whitespace, and download the results as a package.