🔒 100% private — runs in your browser, nothing is uploaded

Basic Auth Generator

Build an HTTP Basic Authorization header and credential URL from a username and password — with the safety warning stated plainly, not buried.

HTTP Basic authentication is the oldest login on the web: the client joins username and password with a colon, base64-encodes the result, and sends it as an Authorization: Basic header with every request. This page performs that encoding exactly as the specification (RFC 7617) defines it, including the step implementations most often get wrong — the pair is first encoded as UTF-8 bytes, and only those bytes are base64-encoded, which is what makes non-ASCII passwords work. Worked example, the RFC’s own: username Aladdin and password open sesame produce the header Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==, and the defaults on this page are set to that very pair so you can watch it happen. The base64 here is implemented by hand over the UTF-8 bytes, in the open, rather than delegated to a one-liner you cannot inspect.

Warning first: Basic authentication is encoding, not encryption — anyone who sees the header or the URL can recover the password in seconds, so only ever use it over HTTPS. Your credentials stay in page memory on your device: they are never uploaded, stored, sent anywhere or put into a link by this page, and they vanish when you close it.

Quick answers

How do I create a Basic Authorization header?

Join username and password with a colon, encode as UTF-8, base64-encode, and prefix with “Basic ”. The specification’s own example: Aladdin and open sesame give Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==.

This page does the encoding by hand over the UTF-8 bytes and also builds the credential-URL and curl forms from the same pair.

Is a Basic auth header encrypted?

No. Base64 is an encoding anyone can reverse in seconds, so the header is only as safe as the connection carrying it: use it over HTTPS only, and never for anything high-value. The password is recoverable from the header by design.

Your credentials are processed only in this page’s memory on your device and are never stored or sent anywhere by the page.

How to use

  1. Type the username and password. The header updates as you type: the pair is joined with a colon, encoded as UTF-8 bytes, and base64-encoded by hand in this page.
  2. Copy the Authorization header for your HTTP client, proxy or test request — and only ever send it over HTTPS, for the reason stated in the warning on this page.
  3. Use the URL form only where a tool genuinely requires credentials in the address, and treat that URL as a password afterwards: it will sit in browser history, server logs and any screenshot that catches it.
  4. Check your work against the worked example below if a server rejects the header: with Aladdin and open sesame, the correct header is a fixed, published value you can compare character for character.

About this tool

Now the warning, stated as plainly as it deserves: base64 is an encoding, not encryption. Anyone who sees that header — in a log, a proxy, a screenshot, a leaked config file — can decode it back to the password in seconds, with tools on every computer. Basic authentication is therefore only ever safe inside an HTTPS connection, where the header travels encrypted, and even then it should guard test environments, internal tools and low-stakes endpoints rather than anything precious; it has no logout, no expiry and no second factor. The URL form deserves extra suspicion: credentials in an address are stored by browsers, written into server logs and forwarded in referrer headers, which is why this page builds it only because some tools demand it, labelled with what it costs. Your credentials themselves never leave this device — they are processed in page memory, never uploaded, stored, sent or put into a link by this page, and they vanish when you close it.

Frequently asked questions

Is Basic authentication secure?

Only inside HTTPS, and only for low-stakes uses. The header is base64, which anyone can decode instantly — it hides nothing. HTTPS encrypts the connection carrying it, which is the actual protection. Over plain HTTP, a Basic header is effectively the password posted in public.

Why does the password allow special characters and accents?

Because the encoding is defined over UTF-8 bytes: the username and password are joined, encoded to UTF-8, and those bytes are base64-encoded. A password with an accented character therefore produces a well-defined header — provided the server decodes the same way, which RFC 7617-compliant servers do.

What is wrong with putting credentials in the URL?

URLs get kept: in browser history, in server and proxy logs, in analytics, and in the referrer sent to the next site. A credential URL is a password that files itself in a dozen places. Use it only when a tool leaves no alternative, and rotate the password afterwards.

Are my credentials stored or sent anywhere?

No. The encoding runs in this page on your device; the username and password are never uploaded, stored, transmitted or written into the page address, and closing the page erases them. The header and URL shown are for you to copy into your own client.

📦 Embed this tool on your site

<iframe src="https://verystep.com/embed/basic-auth-generator/" title="Basic Auth Generator" width="100%" height="520" loading="lazy" style="border:0"></iframe>

Free to use. The embed shows a small "Powered by Verystep" link.

First time embedding? Read the step-by-step guide →

More free tools