Decodificador JWT
Decodificar e inspecionar JSON Web Tokens
Proximos passos sugeridos
Ferramentas Relacionadas
Gerador de Hash
Gere hashes SHA-1, SHA-256, SHA-384, SHA-512
Gerador de Senhas
Gere senhas aleatórias fortes e seguras
Gerador HMAC
Gere assinaturas HMAC usando SHA-256, SHA-384 ou SHA-512
Gerador de Token / Segredo
Gere tokens aleatórios, chaves de API e segredos em vários formatos
Gerador de Hash Bcrypt
Criptografe senhas com bcrypt e verifique hashes
Codificador / Decodificador Base64
Codifique texto para Base64 ou decodifique Base64 de volta para texto rapidamente.
Como Usar
Cole ou Digite
Insira seu texto, código ou dados na área de entrada.
Escolha as Opções
Selecione a transformação ou formato que deseja aplicar.
Copie o Resultado
Copie a saída para sua área de transferência com um clique.
Por Que Usar Esta Ferramenta
100% Gratuito
Sem custos ocultos, sem planos premium — todos os recursos são gratuitos.
Sem Instalação
Funciona inteiramente no seu navegador. Nenhum software para baixar ou instalar.
Privado e Seguro
Seus dados nunca saem do seu dispositivo. Nada é enviado a nenhum servidor.
Funciona no Celular
Totalmente responsivo — use no seu celular, tablet ou desktop.
Understanding JSON Web Tokens (JWT) Structure and Security
Key Takeaways
- JWTs consist of three Base64url-encoded parts: header, payload, and signature — the payload is readable by anyone, not encrypted.
- Never store sensitive data in JWT payloads — they can be decoded without the secret key. JWTs provide integrity, not confidentiality.
- All JWT decoding happens in your browser — your tokens are never sent to any external server.
JSON Web Tokens (JWT) are the de facto standard for stateless authentication in modern web applications. They carry claims about a user between services without requiring server-side session storage. Understanding JWT structure is essential for debugging authentication flows, verifying token contents, and identifying security issues.
JWTs are used by over 80% of modern web APIs for authentication and authorization.
Industry Adoption
Key Concepts
Three-Part Structure
A JWT has three Base64url-encoded sections separated by dots: the header (algorithm and type), the payload (claims like user ID, expiration), and the signature (cryptographic proof of integrity).
Registered Claims
Standard claims include iss (issuer), sub (subject), aud (audience), exp (expiration), nbf (not before), iat (issued at), and jti (JWT ID). These provide interoperable token metadata.
Signature Algorithms
HS256 uses a shared secret (symmetric), while RS256 uses RSA key pairs (asymmetric). RS256 is preferred for distributed systems where the verifier should not have the signing key.
Security Considerations
Common JWT vulnerabilities include: accepting 'none' algorithm, using weak secrets, not validating expiration, and confusing HS256/RS256 algorithms. Always validate all claims on the server.
Pro Tips
Always check the 'exp' claim — expired tokens should be rejected. Set short expiration times (15–60 minutes) for access tokens.
Use the 'aud' claim to ensure tokens are only accepted by intended services — this prevents token misuse across services.
Store JWTs in httpOnly cookies rather than localStorage to protect against XSS attacks.
Implement token refresh flows with longer-lived refresh tokens stored securely, rather than issuing long-lived access tokens.
All JWT decoding is performed entirely in your browser. Your tokens, which may contain user identity information and authentication claims, are never transmitted to any server. Note: this tool decodes tokens but does not verify signatures.