Basic Auth Generator

How to use it

1. Type the username and password into the two fields — the header is generated as you type.
2. Copy the Authorization header line and add it to your request, client or HTTP file.
3. Or copy the curl example and replace the URL with your endpoint.
4. The password field is masked; use Clear to wipe both fields when done.

Common use cases

• Quick API tests — try a Basic-auth endpoint from the terminal without hand-writing base64.
• Server config — fill in the encoded value for reverse proxy or web server auth directives.
• Client code — verify that your language's base64 output matches the expected header byte for byte.
• Non-ASCII credentials — usernames with accents or non-Latin characters are encoded via UTF-8, the way RFC 7617's charset parameter intends.

Why it stays private

The base64 encoding happens in your browser with no network activity at all. Credentials typed here are never stored, logged or transmitted — but the result is plain base64, not encryption, so treat any generated header as a secret.

FAQ

Q: Is Basic auth secure? A: Only over HTTPS. The header repeats on every request and is trivially decodable, so it must always travel inside TLS. Disable it for anything sensitive that cannot guarantee TLS.

Q: Why another base64 output for the same password? A: Some tools encode with Latin-1 and mangle non-ASCII characters. This generator encodes the UTF-8 bytes first, which matches what servers expect when the credentials are not plain ASCII.

Q: Can I put a colon in the username? A: The format splits on the first colon, so a colon in the username makes the part after it unparseable as username. Use a different username, or move the extra part into the password.