The TextEncoder API never supported legacy encodings (such as 'shift_jis', 'windows-1252', etc) except for two UTF-16 variants ('utf-16', 'utf-16be'). Usage was minimal and support was removed from the spec. The TextEncoder constructor will no longer take an argument (if one is passed it is ignored, as is the standard for DOM APIs), and will always encode to "the encoding" (utf-8).



Editor's draft

Status in Chromium


Removed (tracking bug) in:

  • Chrome for desktop release 53
  • Chrome for Android release 53
  • Chrome for iOS release 53
  • Android WebView release 53

Consensus & Standardization

After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.

  • Positive
  • No signal
  • No signal
  • No signals



Intent to Deprecate and Remove:

Search tags

encoding textencoder utf8 utf-8 utf16 utf-16,

Last updated on 2020-11-09