What file types and upload formats does Encoding Converter support?
Updated
Encoding Converter accepts text-based files whose character encoding can be changed, and it takes them in three upload forms: a single file, many files at once, or a .zip archive containing multiple files. If your goal is batch conversion, the multiple-file and .zip options are the ones that matter; if you only need to fix one file, the single-file upload is enough.
What counts as a supported file
The tool is built for text-based files, meaning files whose contents are characters stored under some encoding. Typical candidates include:
.txtplain text files.csvand other delimited data files.html,.xml,.json, and similar markup or structured text- Source code and configuration files
- Subtitle and log files
The deciding factor is not the extension but whether the file is text. A binary format such as an image, audio file, or compiled executable has no character encoding to convert, so changing its encoding would corrupt it rather than fix it.
Upload formats
| Upload option | When to use it | Notes |
|---|---|---|
| Single file | Fixing one file's encoding | Simplest path |
| Many files | Batch conversion without packaging | Select several files in one go |
.zip file |
Batch conversion from an archive | Useful when files are already grouped or you want one upload |
The site states you can "upload a single file - many files - .zip files," so all three are first-class options rather than workarounds.
How the encoding settings fit in
Encoding Converter lets you specify the source encoding and the target encoding. Per the site's own guidance, the recommended order is:
- Specify the encodings (from and to).
- Then select the files.
Specifying the original encoding is optional but recommended. Naming it correctly matters most for batch jobs and .zip uploads, because a wrong source encoding applied across many files produces the same wrong result everywhere. If you are unsure of the source encoding, leaving it unspecified lets the tool attempt detection, but for a large batch it is safer to confirm the source encoding first.
Choosing the right upload for your task
- One file, known problem (for example, a
.csvshowing garbled accented characters): use the single-file upload and set both encodings explicitly. - A folder's worth of files: use the multiple-file upload so you set the encodings once and convert them together.
- Files already zipped, or a large set you want to move as one unit: use the
.zipupload.
In every case, the input is your text file(s), the action is choosing source and target encodings and uploading, and the expected result is the same files re-encoded to the target.