JWT payloads are only encoded, not encrypted, unless a separate encryption layer is used. Never treat decoded payload data as proof of authenticity without signature validation.
Free developer encoding tool
Base64 URL Encoder Decoder
Encode and decode Base64, URL strings, HTML entities, and inspect JWT header and payload data without sending text to an external API.
- Base64
- URL encode
- HTML entities
- JWT preview
Converted result
Output
- Input length
- 0 characters
- Output length
- 0 characters
- Preview
- Output will appear here.
Token helper
Decode JWT header and payload
Paste a JWT to inspect the decoded header and payload. This viewer does not validate the signature and does not prove the token is trustworthy.
How Base64 encoding works
Base64 turns bytes into a text-safe alphabet so data can travel through systems that expect plain characters. It is common in API payloads, email attachments, configuration snippets, images embedded in text, and authentication formats.
Base64 is not encryption. Anyone who has the encoded text can decode it. Use it for representation and transport, not for secrecy.
Encoding modes compared
Different encoding modes solve different transport problems. Choose the mode that matches where the text will be used.
| Mode | What it does | Common use |
|---|---|---|
| Base64 | Represents bytes as text | API fields, attachments, config snippets |
| URL encode | Escapes reserved URL characters | Query strings, redirect URLs, path parts |
| HTML escape | Displays markup characters as text | Showing code samples or literal markup |
| JWT decode | Reads header and payload | Token inspection, not signature validation |
URL encoding and decoding
URL encoding changes spaces, punctuation, and non-URL-safe characters into percent-encoded sequences. This prevents query parameters, redirect URLs, and path fragments from breaking when they contain spaces or reserved symbols.
URL decoding reverses that process. If a decode operation fails, the input may contain an incomplete percent sequence or text that was not actually URL encoded.
HTML escape and unescape
HTML escaping converts characters such as less-than, greater-than, quotes, and ampersands into entities. This is useful when you need to display markup-like text as text instead of letting the browser interpret it as HTML.
Escaping is only one part of safe output handling. Application security depends on context, framework behavior, and proper server-side controls.
JWT decoding caution
A JSON Web Token usually contains a header, payload, and signature. The header and payload are Base64URL encoded, which means they are easy to decode for inspection. That does not mean the token is valid.
To trust a JWT, an application must verify the signature with the expected algorithm, key, issuer, audience, and expiration rules. This page is only a quick inspection helper.
Common JWT claim fields
JWT payloads often use short registered claim names. These fields are only meaningful after the token signature and expected issuer rules are verified by the application.
| Claim | Meaning | What to check |
|---|---|---|
iss |
Issuer | Expected identity provider or service. |
sub |
Subject | User or entity the token describes. |
aud |
Audience | Application or API the token is meant for. |
exp |
Expiration | Epoch time when the token should expire. |
iat |
Issued at | When the token was created. |
Do not use encoding for secrecy
Encoding changes representation. Encryption protects content with a key. Hashing creates a one-way fingerprint. These are different tools, and mixing them up can create serious security mistakes.
Do not paste production secrets, passwords, private keys, session cookies, or live access tokens into general web utilities. Use approved internal tooling for sensitive material.
Methodology, Formula & Official Standards
This Base64, URL Percent-Encoding & JWT Inspector tool implements the official specifications and mathematical definitions established by IETF RFC 4648 (Base64 and Base64URL Data Encodings), RFC 3986 (URI Percent-Encoding), and RFC 7519 (JSON Web Token). Core calculation logic: Base64 Output Length = 4 × ceil(Input_Bytes / 3); UTF-8 byte array is grouped into 24-bit (3-byte) blocks and mapped to four 6-bit indices (0–63) in the RFC 4648 alphabet with '=' padding. All conversions and calendar evaluations run locally in your browser using deterministic standards so engineers, travelers, and students can verify exact outputs without rounding drift.
Step-by-Step Worked Example
Worked Example: Encoding the 15-byte UTF-8 string 'Hello, World! 🌐' (18 UTF-8 bytes because the globe emoji uses 4 bytes F0 9F 8C 90) divides evenly into six 3-byte (24-bit) groups, producing exactly 6 × 4 = 24 Base64 characters ('SGVsbG8sIFdvcmxkISDwn4yQ') with zero '=' padding characters and 33.3% size overhead.
Reference Benchmark & Comparison Table: Base64, URL Percent-Encoding & JWT Inspector Reference Benchmark & Comparison Table
| Standard Tier / Mode | Primary Definition / Input | Converted / Secondary Value | Key Technical Metric | Practical Engineering / Planning Rule |
|---|---|---|---|---|
| Standard Base64 (RFC 4648 §4) | A–Z, a–z, 0–9, +, / (pad =) | +33.3% (4 chars per 3 bytes) | MIME email attachments, Data URLs | Plus and slash must be escaped in URLs |
| Base64URL Safe (RFC 4648 §5) | A–Z, a–z, 0–9, -, _ (optional =) | +33.3% (unpadded in JWT) | JWT headers/payloads, OAuth2 PKCE tokens | Replaces + with - and / with _ for URL safety |
| URI Component Encoding (RFC 3986) | %XX hex octets for reserved chars | Variable (+200% on non-ASCII) | Query string parameters (?q=...) | Use encodeURIComponent() for parameter values |
| HTML Entity Escaping (W3C HTML5) | & < > " ' | Minimal on prose text | Preventing DOM XSS in templates | Mandatory before injecting untrusted text |
| JWT Token Inspection (RFC 7519) | Header.Payload.Signature (3 parts) | Base64URL decoded JSON | Debugging exp/iat claims locally | Decoding does not verify HMAC/RSA signature |
Frequently Asked Questions
What official standard governs this Base64, URL Percent-Encoding & JWT Inspector calculator?
This tool follows IETF RFC 4648 (Base64 and Base64URL Data Encodings), RFC 3986 (URI Percent-Encoding), and RFC 7519 (JSON Web Token), applying the exact formula Base64 Output Length = 4 × ceil(Input_Bytes / 3); UTF-8 byte array is grouped into 24-bit (3-byte) blocks and mapped to four 6-bit indices (0–63) in the RFC 4648 alphabet with '=' padding directly in client-side JavaScript.
Why do exact conversion constants and boundary rules matter?
Using truncated constants or ignoring leap-year, DST, or binary-vs-decimal rules introduces cumulative errors in storage sizing, network routing, and international scheduling.
Does this tool send any entered data, tokens, or dates to an external server?
No. Every conversion and inspection runs 100% locally inside your browser tab with zero server-side processing or logging.
How can I verify my result against the benchmark table?
Match your input range to the closest row in the 5-tier reference table above and compare against the Worked Example step-by-step walkthrough.
Editorial Methodology & Disclaimer
Editorial Methodology & Disclaimer: All calculator outputs and reference tables on Utility Stack are educational planning estimates based on published mathematical standards. They are not professional financial, legal, tax, or medical advice.
Official Standards & Policies: About & Methodology | Privacy Policy | Terms & Disclaimer | Contact