Why are not all legacy encodings available for encoding?
Native TextEncoder only supports UTF-8. ASCII, Latin-1, and UTF-16 have supplemental encode paths; more legacy encodings are mainly decode-only.
DevTools Text Encoding Converter converts text and bytes between UTF-8, ASCII, Latin-1, UTF-16, and other browser-supported legacy encodings to debug byte sequences and mojibake.
Convert text and bytes between UTF-8, ASCII, Latin-1, UTF-16, and other browser-supported legacy encodings.
Note: browser TextEncoder only supports UTF-8 natively; ASCII, Latin-1, and UTF-16 are implemented here. Legacy encodings like GBK, Big5, and Shift_JIS decode only when the browser supports the matching TextDecoder label.
Two modes: encode text to bytes, or decode hex bytes to text. Unsupported encoding labels are reported clearly.
Native TextEncoder only supports UTF-8. ASCII, Latin-1, and UTF-16 have supplemental encode paths; more legacy encodings are mainly decode-only.
Switch to bytes-to-text, choose UTF-8, paste the hex string, and see if it decodes to readable text.
The tool reports unsupported TextDecoder labels. Use Node.js iconv or a desktop tool for those cases.
No. Encoding and decoding run locally in your browser.
Format and beautify SQL, HTML, XML, and YAML, plus a regex debugger—all run locally in the browser, free with no sign-up.
Full JSON toolkit: format, validate, minify, convert to CSV/XML, diff, generate and validate Schema, JSONPath, and tree view—all processed locally in the browser.
Upload a logo, preview browser and Google search results, configure iOS/Android icons, and generate a complete favicon package in one click.
Base64, JWT, SHA256, MD5, HMAC, Bcrypt, RSA keys, SSL certificates, and password strength—common encoding and security text utilities.