Basic Auth Header Generator
Build an RFC 7617 Basic field value with explicit UTF-8 NFC or ISO-8859-1 encoding. Reveal or copy the result locally.
Build a Basic Authorization Header
Use the encoding expected by your service. The user ID cannot contain a colon. Base64 can be decoded back to your credentials, so treat the result like the password.
Basic Auth Header Generator: how to use it
- Enter the user ID and password for the value you intend to construct.
- Select UTF-8 with NFC normalization for a UTF-8 challenge, or ISO-8859-1 if your verified service expects it.
- Generate the header. Reveal it, copy the full header line, or copy only the field value. Reset when done.
Limits and notes
Uses up to 4,096 encoded bytes including the separator. User IDs cannot contain a colon. Both fields reject Unicode control characters. The tool does not send HTTP requests or retain the credentials across reloads.
How your privacy works →Basic Auth Header Generator: common questions
Can a password contain a colon?
Yes. The first colon separates the user ID from the password. Later colons belong to the password.
Which encoding should I choose for non-ASCII text?
Use the encoding expected by the receiving system. A Basic challenge with charset UTF-8 requests NFC-normalized Unicode encoded as UTF-8.
Is the output encrypted?
Base64 represents bytes in a reversible form. A Basic value carries the same sensitivity as the original credentials. RFC 7617 relies on transport protection such as HTTPS.