Skip to content
⚡

JWT Generator

Generate unsigned or HS256-signed JWTs locally in your browser for auth testing, demos, and debugging. Build sample claims quickly without sending token data or secrets to a server.

JWT generator

Create a local test token

Build unsigned or HS256-signed sample tokens without sending claims or secrets anywhere.

Generated tokens are useful for local debugging and demos. Only trust claims after verification against the real signing configuration in your application.

Generated output

Copy into your next debug step

Next best tools

What to do after generating a test token

Use the next tool based on what you are debugging: claim contents, timestamp problems, or raw token segments.

JWT Decoder & Inspector

Decode the token you just generated, inspect claims, and check HS256 verification behavior.

Timestamp Converter

Translate `iat`, `nbf`, and `exp` into readable dates when auth timing looks wrong.

Base64 Encode / Decode

Inspect individual JWT segments manually if you need to compare raw encoded values.

How to use this JWT generator

  1. Choose whether you want an unsigned token or an HS256-signed test token.
  2. Edit the header and payload JSON to match the claims you want to simulate.
  3. Provide a shared secret if you are signing with HS256, then click Generate token.
  4. Copy the encoded token into your app, API client, or the JWT Decoder for the next debug step.

When a local token generator is useful

JWT debugging often starts before your real auth flow is ready or while you are isolating one specific claim issue. In that moment, it helps to generate a known-good sample token with the exact claims and timestamps you want to test.

This tool is useful for local demos, auth middleware testing, verifying claim parsing, and checking how frontends or APIs behave when a token is expired, not active yet, or missing a field.

It is not a replacement for production token issuance. Real trust comes from your issuer, your key management, and verification inside the application that consumes the token.

Features

  • Generate unsigned JWTs or HS256-signed test tokens locally
  • Edit header and payload JSON directly in the browser
  • Preview common claims like iss, sub, scope, iat, nbf, and exp
  • Copy the finished token with one click
  • Never uploads payload data or secrets to a server
  • Designed for debugging, demos, and local auth testing

Frequently Asked Questions

? Does this JWT generator sign tokens?
Yes. It can generate unsigned tokens with `alg: none` or sign HS256 tokens locally in your browser with a shared secret that you provide.
? Is my payload or secret sent to a server?
No. Header JSON, payload JSON, and HS256 secrets stay in your browser. pigia.dev does not upload them anywhere.
? Should I use generated tokens in production?
Use this tool for testing, demos, and local debugging. Production tokens should come from your real auth system and be validated by your application.
? What algorithms are supported?
This version supports unsigned tokens (`alg: none`) and HS256. Public-key algorithms such as RS256 are not generated here.

Guides That Support This Tool

Short reference content for the workflows and concepts behind this utility.

Guide ->

JWT Test Token vs Real Signed Token: What Changes in Practice

A generated test token is useful for debugging, but it is not the same as a production auth token.

Workflow ->

Auth Debugging Workflows for JWTs, Headers, and Token Expiry

Start here when auth bugs span JWT claims, token generation, headers, and expiry windows.

Guide ->

Why JWT Expiry Checks Break: exp, nbf, Clock Skew, and Timezones

Most JWT time bugs are not mysterious once you compare the raw claims to real timestamps.