When you need this
- Exports from Polish accounting software, online banking or ERP systems come in Windows-1250, but your system only accepts UTF-8.
- Old websites, mail archives and log files from Poland or Central Europe are stored in ISO-8859-2.
- A colleague saved a file as "ANSI" in Notepad on a Polish Windows PC, and your editor or tool expects UTF-8.
- Older versions of Polish programs such as Subiekt GT or Comarch Optima, and various payroll and banking systems, may export files in Windows-1250.
Garbled
Za¿ó³æ gêœl¹ jaŸñ ulica Piêkna 5, Kraków
After conversion
Zażółć gęślą jaźń ulica Piękna 5, Kraków
How to convert the file
- Drag the file into the box above.
- Mojibuster detects Windows-1250, ISO-8859-2 and UTF-8 on its own. The result shows which encoding it used to read the file.
- If the preview looks wrong, read the file again with one click on Read as ….
- Click Download to save the file as UTF-8.
Detection is tuned for Polish text. Czech, Slovak, Hungarian, Slovenian and Croatian files use the same code pages, but other letters. If such a file looks wrong, choose another reading with Read as ….
Windows-1250 vs. ISO-8859-2
The two code pages differ in just a few Polish letters: ą, ś, ź (and their capitals) sit at different byte values. That's why a file read with the wrong one looks almost fine – only these letters turn into ±, ¶ or Ľ. Mojibuster compares both readings and picks the one that produces Polish words.
Polish letters and their bytes
ą– Windows-1250B9, ISO-8859-2B1, UTF-8C4 85. Broken forms:Ä…and¹.ś– Windows-12509C, ISO-8859-2B6, UTF-8C5 9B. Broken forms:Ĺ›andœ.ź– Windows-12509F, ISO-8859-2BC, UTF-8C5 BA. Broken forms:ĹşandŸ.ł– byteB3in both code pages, UTF-8C5 82. Broken forms:Ĺ‚and³.ż– byteBFin both code pages, UTF-8C5 BC. Broken forms:ĹĽand¿.
The opposite mix-up is worse: a Windows-1250 file read as ISO-8859-2 turns ą into š, and ś and ź disappear completely, because bytes 9C and 9F are invisible control characters in ISO-8859-2. The original file is still fine, though – just drag it here.
Characters that have already turned into ? can't be recovered – the information was lost when the file was saved. Mojibuster shows how many there are. How these errors happen is explained in What is mojibake.
Converting on the command line
For many files, the command line is handy. On Linux and Mac: iconv -f WINDOWS-1250 -t UTF-8 old.txt > new.txt. In PowerShell 7: Get-Content old.txt -Encoding 1250 | Set-Content new.txt -Encoding utf8BOM (saves UTF-8 with a BOM, which Excel needs). On an English Windows PC, -Encoding Default in Windows PowerShell 5.1 means Windows-1252, not Windows-1250, so it won't work here.
These commands convert blindly. If the file was already UTF-8, you get garbled text like Ä…. Mojibuster detects the encoding first and leaves files that are already UTF-8 alone.
Frequently asked questions
How can I tell which encoding a file uses?
Mojibuster shows it after loading the file. A quick hint: ¹ and ³ instead of ą and ł mean Windows-1250 read as Western text, ± instead of ą means ISO-8859-2 read as Windows-1250, and Ä… instead of ą means UTF-8 read as Windows-1250. And %C4%85 is a URL code, not garbled text.
Does this work for Czech, Slovak or Hungarian files?
These languages use the same code pages, but detection is tuned for Polish. If the preview looks wrong, click Read as … and choose another reading.
Will the converted file open correctly in Excel?
Yes. For CSV files, keep Save with BOM switched on – then Excel opens the file without broken characters. More tips: broken characters in Excel.
Can I convert back from UTF-8 to Windows-1250?
Not yet – files are saved as UTF-8 only. If you need Windows-1250, save the file again in Excel or a text editor.
Is my file uploaded to a server?
No. The conversion runs entirely in your browser.