Skip to main content
WizTools123
Free Online Tools

Tool Categories


Security Tools New Tool

Free Online Basic Auth Generator and HTTP Header Decoder

Turn a username and password into an HTTP Basic authorization header, or paste a header and read the credentials back out. Choose UTF-8 or the older ISO-8859-1, get the curl and fetch forms, and see why a colon cannot appear in a username. Nothing is uploaded.

Free Forever Nothing Uploaded Both Directions Nothing Uploaded
Free Online Basic Auth Generator and HTTP Header Decoder
Share this tool
Advertisement Slot (Top Banner) Google AdSense Unit • Responsive Banner
Basic Auth Generator Everything happens in this tab. Nothing you paste is sent anywhere.
Header to read
Result
Direction
Credentials
Give me
For curl

Buy Us A Coffee

Enjoying WizTools123? Help keep our server infrastructure 100% free and open for everyone.

Buy Us A Coffee
Sponsored Content (Below Tool) Google AdSense Placement

How to Use Basic Auth Generator

Step by step, start to finish.

1
Choose a direction

Build one takes a username and a password and gives you the header. Read one takes a header, or just the base64 out of it, and gives you back the credentials.

2
Type the username and password

The password is masked until you press Show. A colon in the username is flagged, because the server splits on the first colon and a username containing one cannot be represented at all.

3
Pick the charset if you have non-ASCII characters

UTF-8 is what the standard says and what you should use. ISO-8859-1 is what older servers actually read, and the two give different base64 for the same password.

4
Take the form you need

The whole header line, just the value, the bare base64, a curl command or a fetch call. All of them are the same credential written differently.

Key Features

What this tool does, and what it does not do.

Both directions

Build a header from credentials, or read credentials out of a header.

Charset handled

UTF-8 or ISO-8859-1, with the difference shown rather than guessed at.

curl and fetch

The ready to paste forms, using a header rather than credentials in the URL.

The colon rule

A colon in the username is flagged, because the server will split on it.

Password masked

Hidden until you press Show, so it stays out of a screen share.

Nothing remembered

No history and no saved setups. A password never reaches browser storage.

About Basic Auth Generator

HTTP Basic authentication is the oldest and simplest way to put a username and password on a request. The client joins them with a colon, encodes the result as base64, and sends the line Authorization: Basic followed by that string. There is nothing else to it, which is both why it is still everywhere and why it is so often used in places it does not belong.

The useful thing a page like this can do is not the base64, which is trivial, but the two details that actually catch people. The first is the colon: the server splits on the first one, so a username containing a colon cannot be expressed, and a header built from one will be silently misread. The second is the charset, where the standard says UTF-8, many older servers read ISO-8859-1, and a password with an accent in it produces two different headers depending on which you believe. Both are surfaced here rather than assumed.

The decode direction exists because that is the half people reach for under pressure. A request is failing, a log line has an Authorization header in it, and the question is which account it was using. Pasting the whole header works, pasting just the base64 works, and the page tells you when the bytes are not valid UTF-8 and shows you the ISO-8859-1 reading instead, which is the usual sign of a client on the other side of the charset question.

What the page says plainly, and keeps saying, is that base64 is not encryption. There is no key involved, so a Basic header is the password written in a slightly less readable alphabet. Over TLS that is acceptable. In a log file, a screenshot, a URL or a plain HTTP request it is a password leak that merely looks technical. Saying so is more useful than producing the header quietly and leaving the impression that something has been protected.

Frequently Asked Questions

Common questions about this tool.

No. It is base64, which is an encoding with no key, so anyone who sees the header can read the username and password immediately. Only the TLS connection protects it, which is why Basic auth over plain http is the same as sending the password in clear text.

Because the server decodes the base64 and splits on the first colon to separate the username from the password. A username with a colon in it would be read as a shorter username and a different password. The password itself may contain any number of colons, since only the first one matters.

UTF-8, unless something tells you otherwise. RFC 7617 specifies it and lets a server advertise that it expects it. ISO-8859-1 is here because many older servers decode the bytes that way, and for a password with a non-ASCII character the two produce different base64, which is a common reason a correct password is rejected.

You can write https://user:pass@host and some tools still accept it, but it is a bad idea and browsers have been removing support. A password in a URL ends up in history, logs and referrer headers. This page gives you the header form for that reason, including in the curl command.

No. The encoding and decoding happen in the page, and the curl and fetch forms are text for you to run yourself, not requests this page makes. There is also no history and no saved setup here, so nothing is written to browser storage.
Advertisement Slot (Bottom Banner) Google AdSense Unit • Responsive Banner