Generate an HTTP Basic Auth header from a username and password, or decode a header you've captured back into its parts. The tool builds Authorization: Basic with UTF-8-safe Base64 as RFC 7617 recommends, and gives the same credentials as cURL and fetch snippets. It's free and runs entirely in your browser — the credentials never leave your device.
| Step | Value |
|---|---|
| Credentials | Aladdin / open sesame |
| Joined | Aladdin:open sesame |
| Base64 | QWxhZGRpbjpvcGVuIHNlc2FtZQ== |
| Header | Authorization: Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ== |
Join username and password with a colon, encode that as UTF-8 Base64, and send Authorization: Basic followed by the result.
Only over HTTPS. Base64 is encoding, not encryption — anyone who sees the header can decode the password instantly.
No. The server splits at the first colon, so it would cut the username short. The password may contain colons.
Older clients encoded credentials as Latin-1. This tool uses UTF-8, which RFC 7617 recommends; the server must agree.
No. Encoding and decoding happen in your browser.
HTTP Basic authentication, defined in RFC 7617, sends credentials as the word Basic followed by the Base64 encoding of username:password. The generator encodes the pair as UTF-8 before Base64, so accented or non-Latin characters survive — the older behavior of encoding as Latin-1 garbles them, and RFC 7617 recommends UTF-8. Because the server splits the decoded string at the first colon, a username containing a colon can't be represented and is rejected; a colon in the password is fine. The decoder accepts a full Authorization: Basic header, the bare token, or Base64url, and reports invalid Base64, non-UTF-8 bytes and a missing separator separately. Snippets show the same credentials for cURL and fetch. Base64 is reversible encoding, not encryption, which the page states plainly: the header must only travel over HTTPS. Nothing is transmitted, but using test credentials in any online tool is good practice.