Karvics
AboutToolsProjectsBlogContact
Tools/Dev/JWT Decoder & Debugger

JWT Decoder & Debugger

What is a JSON Web Token (JWT)?

JSON Web Token (JWT) is an open standard (RFC 7519) that defines a compact and self-contained way for securely transmitting information between parties as a JSON object. This information can be verified and trusted because it is digitally signed. JWTs can be signed using a secret (with the HMAC algorithm) or a public/private key pair using RSA or ECDSA.

Why Use Our JWT Debugger?

JWTs often contain sensitive user identity data, roles, and authorization scopes. Unlike many online tools that send your token to an external server, our debugger runs 100% client-side in your browser. Your authentication tokens and API secret keys never leave your machine.

What this tool does

What this tool does

  • Header & payload decoding: Instantly view the algorithm, token type, and all claims in tree or JSON view
  • RFC 7519 claims inspector: Structured breakdown of iss, sub, aud, exp, nbf, iat, and jti with human-readable timestamps
  • Live expiration countdown: Shows real-time validity status with active countdown or expiration elapsed time
  • Multi-algorithm verification: Verify signatures locally for HS256 (HMAC), RS256 (RSA), and ES256 (ECDSA)
  • Developer quick-copies: 1-click copy for Authorization: Bearer headers and cURL commands

How to Use

  1. Paste Token or Pick Sample: Paste your raw JWT string or pick one of the pre-loaded samples (Active HS256, Expired Token, RBAC Token).
  2. Inspect Claims & Expiry: Review standard registered claims (issuer, subject, audience, issued time) and live expiration status.
  3. Verify Signature: Enter your HMAC secret key or RSA/ECDSA public key (PEM) to verify the token's cryptographic integrity.
  4. Quick Copy for APIs: Click "Copy Authorization: Bearer" or "Copy cURL Command" to use your token directly in API clients or terminals.

Glossary

Header
The first segment of a JWT specifying token type and signing algorithm (e.g. HS256, RS256, ES256).
Payload
The second segment of a JWT containing registered claims and application-specific identity or authorization data.
Signature
The third segment created by cryptographic hashing or signing of the header and payload using a secret or private key.
Standard Claims (RFC 7519)
Standard registered claim names including sub (subject), iss (issuer), aud (audience), exp (expiration), nbf (not before), iat (issued at), and jti (JWT ID).
HS256 vs. RS256 vs. ES256
HS256 uses symmetric HMAC-SHA256 with a shared secret; RS256 uses asymmetric RSA; ES256 uses elliptic curve cryptography (ECDSA P-256) for compact, high-performance signatures.

Related Tools

Explore more tools from this category to enhance your workflow

Mock Data Generator

Generate realistic fake data instantly. Export as JSON, CSV, YAML, TOML, or TOON completely offline.

JSON Formatter & Validator

Format, validate, minify, and beautify your JSON data securely in your browser.

JSON ↔ CSV Converter

Convert bidirectionally between JSON and CSV. Supports nested object flattening, unflattening, and type auto-detection.

Timestamp / Epoch Converter

Convert Unix timestamps (seconds, ms, µs, ns) to human dates, and dates to epoch timestamps with timezone auto-detection.

Karvics

Free online tools for developers, designers, and digital professionals. All tools work offline in your browser with no signup required.

Tool Categories

  • PDF Tools
  • Image Tools
  • Cryptography Tools
  • Password Tools
  • URL Tools
  • Notepad Tools
  • SEO Tools
  • TOON Tools
  • Dev Tools

Quick Links

  • All Tools
  • About Us
  • Projects
  • Blog
  • TOON Benchmark
  • Privacy Policy
  • Terms of Use
  • Contact Us
  • Sitemap
  • For AI Agents
  • Report an Issue

© 2026 Karvics. All rights reserved.

Frequently Asked Questions about JWT Decoder & Debugger

No, this tool decodes and verifies your JWT entirely within your browser using client-side JavaScript. Your tokens never leave your device, ensuring maximum security for sensitive credentials.

The tool automatically inspects and highlights standard registered claims: sub (Subject / User ID), iss (Issuer), aud (Audience), exp (Expiration time with live countdown), nbf (Not Before date), iat (Issued At time), and jti (Unique Token ID).

Yes! Click "Copy Authorization: Bearer" or "Copy cURL Command" under Developer Quick-Copies to generate ready-to-paste authorization strings for terminal requests, Postman, or API testing.

For HS256 tokens, we calculate the HMAC-SHA256 hash using the provided secret. For RS256 and ES256 tokens, we verify using the browser's native Web Crypto API and the provided public key (PEM format).

If you don't provide a secret, the tool can still decode the header and payload so you can inspect the contents and check the expiry date. However, it won't be able to verify if the token has been tampered with.

Some systems tolerate a short clock-skew window or don't strictly enforce the exp claim. This tool reports the exp claim's literal expiry — if your app behaves differently, that's a difference in how your server validates tokens, not an error in the decoding here.