Decode Base64 to JSON
Auto-detect URL-safe.
Pretty-printed output.
Decode any Base64 string to formatted JSON — standard or URL-safe auto-detected. Decode JWT payloads, API responses and config values. Get code snippets for 5 languages.
JWT tokens are three Base64url-encoded parts separated by dots.
header.payload.signature.
Copy the middle section (between the first and second dot) and paste it here to see the claims.
The header (first section) is also Base64url JSON — paste it to see the algorithm.
The signature (third section) is not JSON and cannot be decoded here.
JWTs are used for authentication in almost every modern web application. When debugging auth issues, decoding the payload reveals the claims — user ID, roles, expiry time and custom data. Paste the middle section of any JWT to inspect it without any external tool.
Kubernetes stores secret values as Base64-encoded strings in YAML manifests. To inspect the actual content of a secret: kubectl get secret mysecret -o jsonpath='{.data.config}' returns Base64. Paste it here to read the JSON configuration inside.
Some webhook providers Base64-encode the event payload in the request body or header for safe transport. Decode the value here to inspect the event structure before writing your webhook handler — no local server required.
APIs and deep-link schemes often pass complex state as Base64-encoded JSON in URL query parameters. Decode any suspicious URL parameter here to understand what data is being passed — useful for debugging, reverse engineering and API testing.
Base64 decoded in your
browser. No upload.
The entire decoding runs in JavaScript using the browser's native atob() function. Your data never leaves your browser — no server, no logs.
Auto-detection inspects the input for URL-safe characters (- and _) and missing padding, restores them before decoding. Data URIs (data:application/json;base64,…) are stripped automatically.
