When a log file comes off an old Windows box or a legacy daemon, the bytes are rarely what they look like on screen. Text that reads é instead of é, files that open as gibberish in a UTF-8 reader, and exports that refuse to paste cleanly into modern dashboards are all symptoms of one thing: an encoding mismatch nobody recorded. Log Encoding Converter makes those bytes honest again — without installing iconv, writing a Python one-liner, or guessing at a hex dump by eye.
Paste the text or hex bytes, tell the tool what encoding they are actually in, and it rebuilds the original bytes and re-reads them in the encoding you want to output. The classic mojibake case — text that was written in UTF-8 but displayed as ANSI — is a two-click fix: source ANSI, target UTF-8, Convert. The reverse direction works too: encode clean Unicode text down into Windows-1252, ISO-8859-1 or UTF-16 bytes for a system that only understands the older encoding, including the Windows-1252-specific characters in the 0x80–0x9F range (curly quotes, em dash, euro sign) that a naive Latin-1 mapping would get wrong.
Text input repairs display garbling; hex input lets you transcode data exactly, including bytes that contain NUL or control characters that a text editor would otherwise drop or corrupt. A byte-order-mark option and full hex view cover the fiddly cases, and UTF-16 little- and big-endian are both supported — useful for Windows Event Log exports and PowerShell transcripts, which default to UTF-16.
This is the kind of tool you reach for once a shift and forget about, until the next support ticket arrives with a log attachment full of question marks and diamonds. Everything runs in the browser with no uploads, so it is safe to paste production data straight from an incident.