Documentation

Features

  • Enter a username and password to generate an Authorization: Basic <Base64> header with UTF-8 encoding.
  • Switch between UTF-8 and ISO-8859-1 when you need to match either modern services or older Basic Auth implementations.
  • Copy the raw Base64 token separately when another tool or config field only needs the token value.
  • All processing stays in the browser and does not upload credentials to any server.

Use Cases

  • Build HTTP Basic Auth headers quickly during API integration and request debugging.
  • Test legacy systems, internal services, or gateway endpoints that still rely on Basic authentication.
  • Check header formatting, encoding issues, and credential copy mistakes during troubleshooting.

Notes

  • Basic Auth only Base64-encodes username:password; it does not encrypt the credentials, so HTTPS is still required in production.
  • A Basic Auth username cannot contain a colon :, because the first colon is reserved as the username/password separator.
  • If the username or password contains spaces, Chinese characters, or other special symbols, generate the header here instead of encoding by hand.
  • If a legacy endpoint requires ISO-8859-1 but the credentials contain Chinese text, emoji, or other unsupported characters, switch to UTF-8 or change the credential content.
  • Clear sensitive values after debugging, especially when you are using a shared device.