AZ Tools

HTTP Basic Auth Encoder / Decoder

Network

RFC 7617 Basic auth is just `base64(username:password)` glued onto an `Authorization: Basic` header. This tool does the encode and decode round-trip in the browser — no network call — and emits a ready-to-paste curl snippet. Warnings catch the common pitfalls: a colon in the username (Basic uses the first `:` as the divider so the credentials parse wrong), non-ASCII characters (RFC 7617 lets you pick a charset but most servers expect UTF-8), and empty credentials.

Base64 token
YWxpY2U6d29uZGVybGFuZA==
Authorization header
Authorization: Basic YWxpY2U6d29uZGVybGFuZA==
curl example
curl -H "Authorization: Basic YWxpY2U6d29uZGVybGFuZA==" https://api.example.com

Basic auth is base64(`user:pass`). It is reversible — only safe over HTTPS, and use a different mechanism (Bearer, mTLS) when you can.

How to use

  1. Encode mode: type a username and password — the Base64 token, full `Authorization` header, and a curl command appear below.
  2. Decode mode: paste any `Authorization: Basic …` line (or just the Base64 part) to see the username and password that's inside.
  3. Copy whichever output you need — Basic creds belong only over HTTPS.

Frequently asked questions

Is Basic auth secure?
Only when the connection is HTTPS. The Base64 is reversible — anyone who captures the header can decode it. Treat the token like a plaintext password.
Why does the username warning fire on a colon?
The Basic auth grammar splits on the FIRST colon. If the username contains `:`, the server reads everything after the first `:` as the password and your real password is appended to the username on the wire.

Related tools