Encode a complete JWT string when a system asks for Base64
JWTs already use Base64URL within their compact format, which makes “JWT to Base64” easy to misunderstand. This tool performs a different operation: it takes the entire token string as input and encodes that text into a new Base64 value. Use that extra wrapper only when an API, test fixture, or integration explicitly asks for it.
Understand the operation
The token is input text; the output is a wrapper
A JSON Web Token is a compact way to carry claims between systems. A signed compact JWT commonly looks like header.payload.signature. Those sections are separated by periods and use Base64URL encoding as part of the JWT/JWS representation. Some encrypted JWTs use a different five-part compact form. The format is defined in RFC 7519, with the signed representation described in RFC 7515.
This encoder does not decode those sections or create a new JWT. It encodes every character of the complete value—including its periods—as one input string. When decoded with the matching Base64 variant, the output returns the original token text. That distinction matters: wrapping a JWT does not make its claims more private, renew its expiration, or produce a valid signature for a different token.
Bearer authorization header normally expects the original JWT. Use this page when a specific receiver requires an additional Base64-encoded token field.JWT text and outer encoding
A sample showing the whole input being wrapped
header.payload.signature
aGVhZGVyLnBheWxvYWQuc2lnbmF0dXJl
This example is not a real or signed token. Decode the output with the matching variant to get the exact input string back.
Three steps
How to encode a JWT to Base64
The paired editors let you keep the supplied token and the resulting encoded value in view while you work.
Paste or upload the token text
Add the complete JWT exactly as supplied, including its periods. This encoder treats the whole input as one text value; it does not split, parse, or validate the token.
Match the receiving format
URL-Safe Base64 is selected by default. Choose Standard Base64 or MIME wrapping only if the receiving field or system documents that requirement.
Encode and copy the result
Press Encode Now between the editors. Check the output, then copy or download it. The destination should decode this outer value before it handles the original JWT.
Choose what the receiver expects
Standard Base64, URL-Safe, or MIME
The variant controls the outer encoded value, not the internal JWT format. Use the receiving system’s documentation to choose. The URL-Safe option is selected initially because token strings often travel through systems with URL-sensitive characters, but the destination—not the input’s name—determines the correct variant. RFC 4648 describes the Base64 alphabets and URL-safe form.
- URL-Safe Base64: uses hyphen and underscore in place of plus and slash. Select it when the receiver asks for Base64URL or a URL-safe encoded value.
- Standard Base64: uses the standard Base64 alphabet. Choose it for APIs and data fields that specifically require standard Base64.
- MIME Base64: wraps long output lines. Use this only if the destination accepts MIME-style wrapped content; line breaks may be rejected by token fields expecting one continuous string.
The optional JWT Data URI adds the data:application/jwt;base64, prefix and switches the payload to Standard Base64, as Data URIs use the standard Base64 form. Use the complete URI only if the receiving field accepts a Data URI; it is not a replacement for a Bearer token.
Example custom request field
Only when the API contract asks for an encoded token
POST /v1/session/import
Content-Type: application/json
{
"tokenBase64": "aGVhZGVyLnBheWxvYWQuc2lnbmF0dXJl"
}The endpoint and field are illustrative. If your API expects Authorization: Bearer, send the original JWT instead of this wrapper.
A real integration pattern
Before and after: preparing a QA token fixture
A QA engineer is building a request fixture for a staging service whose documented test endpoint accepts a `tokenBase64` value.
Is the endpoint asking for a JWT segment or the full token?
The token already looks encoded, so the engineer may decode and re-encode the header, copy just the payload, or escape periods by hand. Those changes produce a different value and can make a fixture fail before the test reaches the service’s token validation.
Encode the supplied string as one value
The engineer pastes the complete staging token, leaves the option specified by the API selected, and clicks Encode Now. The resulting string goes into `tokenBase64`. The service decodes that outer layer first, then handles the restored JWT according to its own validation rules.
For a normal bearer-authentication flow, there is no extra encoding step. This example is for a custom field that explicitly specifies Base64.
Where this tool fits
Use cases for encoding a whole JWT string
A JWT Base64 encoder is useful at a boundary where a receiving format asks for an encoded string. It is not a JWT generator, token decoder, or signature checker. Keep the expected data shape clear in tests, API docs, and deployment configuration.
Custom API fields
Prepare a complete token for an endpoint that documents a Base64 or Base64URL token property.
QA fixtures and mocks
Create a reproducible test input when a mock service expects the JWT string inside an encoded field.
Integration handoffs
Pass token text through a legacy connector or configuration field that has an explicit Base64 contract.
Transport troubleshooting
Confirm exactly what an outer encode/decode step does when diagnosing a data-format mismatch.
Handle tokens carefully
Encoding is not encryption or signature verification
Base64 is reversible. Anyone with the encoded output can decode it. It does not hide claims or protect a bearer credential. Treat real access tokens as secrets.
A signature is tied to token bytes. Editing the JWT or reformatting its segments can invalidate a signature. This tool preserves the supplied text inside an outer encoding; it does not sign or verify it.
Keep the complete string together. For an outer wrapper, include every segment and separator. The example uses placeholders only; never paste a production token into public examples or shared screenshots.
Follow the receiver’s contract. Check whether it expects Standard Base64, Base64URL, or the original JWT. Extra encoding on a Bearer token typically changes the value the server receives.
Quick answers
JWT to Base64 FAQs
What does this JWT to Base64 tool encode?
It Base64-encodes the entire JWT string you provide as one text value. It does not re-encode individual JWT sections, create a token, decode claims, or verify a signature.
Is a JWT already Base64 encoded?
A signed compact JWT commonly contains Base64URL-encoded header, payload, and signature sections separated by periods. Encoding the complete token again creates an outer wrapper around that existing token; it is a separate operation.
Should I Base64-encode a JWT before sending it as a Bearer token?
Usually no. A Bearer authorization header expects the JWT in its original form. Encode the complete token only when the receiving API or data format specifically asks for a Base64 or Base64URL value.
Does this tool validate or sign the JWT?
No. It performs text-to-Base64 encoding only. It does not check expiration, issuer, audience, signature validity, signing keys, or token permissions.
Does Base64 protect a JWT or hide its claims?
No. Base64 is reversible encoding, not encryption. Signed JWT payloads are generally readable by anyone who has the token. Treat real access tokens as credentials and do not share them in public places.
Which variant should I use?
Use the exact variant required by the receiver. URL-Safe is selected by default and uses the URL-safe alphabet. Standard is common for general Base64 fields; MIME adds line wrapping and is suitable only when the destination expects it.