Enter a username or password to generate a credential.
A Basic Auth generator builds the credential that HTTP Basic Authentication requires: the base64 encoding of your username and password joined by a colon, prefixed with the word "Basic". The result is the value of the Authorization header a client sends to prove who it is. The scheme is defined in RFC 7617, "The Basic HTTP Authentication Scheme", and it is the simplest credential a server and client can agree on, which is why it is still everywhere in APIs, webhooks, private registries and internal tools.
The encoding is deliberately reversible. Basic auth is not encryption and offers no confidentiality on its own: base64 is a transport encoding, so anyone who can read the header can read the password back in one step. That is why this tool also decodes a token. Paste an Authorization: Basic value and it shows you the username and password it carries. The one rule that trips people up is that the username cannot contain a colon, because the first colon is the boundary between the two fields; the password may contain as many colons as it likes. This generator flags a colon in the username so a credential does not silently decode wrong.
Because the value is just base64 of "user:password", getting it right by hand is fiddly, and getting it wrong means a stream of 401 responses with no obvious cause. This tool produces the exact header line, a ready-to-run curl command in both the -u and explicit-header forms, a fetch() snippet, and the userinfo URL form (https://user:pass@host) for the cases where that still works. It encodes over UTF-8, so accented characters and non-Latin passwords produce the same bytes a compliant client would send, rather than being corrupted the way an ASCII-only encoder would corrupt them.
Everything happens in your browser. The username and password you type are never uploaded, which is the whole point when you are handling a real credential. Sending a live password to a server just to encode it would defeat the exercise. There is no signup and no logging, so it is safe to paste production credentials while you debug an integration.
Type the credential you want to encode. Optionally set the host so the generated curl and URL examples point at the right server.
Grab the Authorization: Basic header, the curl command, the fetch() snippet, or the base64 token on its own, whichever your task needs.
Switch to decode mode and paste a Basic auth header or token to recover the username and password it encodes.
If the username contains a colon, the tool warns you, because the credential would decode with the wrong split at the receiving end.
Produces the full Authorization: Basic line, curl -u and explicit-header commands, a fetch() snippet, and the raw base64 token.
Encode a username and password into a token, or paste an existing Basic auth value to read the credential it carries back out.
Encodes the credential over UTF-8, so accented and non-Latin usernames and passwords produce the exact bytes an RFC 7617 client would send.
Warns when the username contains a colon, the one input that makes a Basic auth credential decode incorrectly on the server.
Check one name across hundreds of TLDs at once. RDAP first, WHOIS fallback, and a verdict of available, taken or unknown — never a guess
Paste a User-Agent string and read the browser, rendering engine, operating system, device type and CPU it describes, all in your browser.
Create frosted-glass UI with a live preview and sliders for backdrop blur, transparency, saturation, color, and radius - then copy production-ready CSS.
Generate MD5, SHA-1, SHA-256, SHA-384, and SHA-512 hashes from any text
0 comments
No comments yet. Be the first to share your thoughts!