Is this the same as JWT encoding?

JWTs use Base64url: + becomes -, / becomes _, padding is dropped. Tick URL-safe for that alphabet.

No. TextEncoder and btoa run here.

This page is text. Paste a data URL string if you already have one.

Yes. Accents and emoji survive a round trip.

Encoding is not encryption. Anyone can decode it.

Runs in your browser · Last updated 4 September 2026

Base64 Encoder

Encode and decode UTF-8 Base64 or Base64url in this tab. Same alphabet JWTs use.

InputURL-safe (Base64url, no padding)

Encoded

aGVsbG8sIEpXVA==

Decoded (if the box is already encoded)

Not valid Base64 (standard or URL-safe).

“hello, JWT” encodes to aGVsbG8sIEpXVA==. The decode box reads the same string back if you paste that value.

Is this the same as JWT encoding?: JWTs use Base64url: + becomes -, / becomes _, padding is dropped. Tick URL-safe for that alphabet.
Uploaded?: No. TextEncoder and btoa run here.
Images?: This page is text. Paste a data URL string if you already have one.
UTF-8?: Yes. Accents and emoji survive a round trip.
Secret?: Encoding is not encryption. Anyone can decode it.