Join the username and password with a colon as user:pass, then Base64-encode that string with a browser-based encoder to build the value for an HTTP Basic Auth header. The encoding runs on your device, so the credentials are never uploaded.
HTTP Basic Auth sends the header Authorization: Basic followed by the Base64 encoding of username:password. Base64 here is only a transport encoding, not encryption, so it is trivially reversible and must always travel over HTTPS. To construct the header value you Base64-encode the exact user:pass string, colon included.
Because a username and password are sensitive, you do not want to paste them into a server-side encoder. A client-side Base64 tool encodes the string in your browser, UTF-8 safe, so the credentials never leave your machine. You can also decode a value to check it. It is free and needs no account.
No. Base64 is a reversible encoding, so Basic Auth must always be sent over HTTPS.
You encode the username and password joined by a colon, as user:pass.
No. The encoding runs in your browser, so nothing is sent to a server.