Fake JWT Payload Generator

How to use

1. 1️⃣
   Choose your options above
2. 2️⃣
   Click Generate
3. 3️⃣
   Copy your result

Detailed instructions

1. Set the count field to how many tokens you need — up to the available maximum.
2. Choose a role from the dropdown: user, admin, or moderator, depending on the access level you want to simulate.
3. Click Generate to produce tokens, each with a unique sub UUID, email, jti, and timestamps.
4. Click the copy icon next to any token and paste it directly into an Authorization: Bearer header.
5. Repeat with a different role to generate tokens for contrast testing without refreshing your work.

Use Cases

• •Testing Express middleware that should return 403 for user-role tokens on admin-only routes
• •Populating Postman or Insomnia collections with structurally valid Bearer tokens for each role
• •Seeding Storybook stories where components render different UI based on decoded role claims
• •Writing Jest or Vitest fixtures for JWT-parsing utilities without importing a real auth library
• •Mocking auth state in a React or Vue app during local development against a stubbed API

Tips

• →Generate one admin and one user token in the same batch so you can test forbidden-vs-allowed responses back to back without switching tabs.
• →If your test framework checks exp, note the token expires exactly 3600 seconds after generation — run time-sensitive tests immediately or mock Date.now().
• →Paste the payload segment into jwt.io to visually confirm all claims are present before wiring the token into a test suite.
• →In Vitest or Jest, store generated tokens as fixtures in a __fixtures__ folder so the same token is reused across test runs rather than regenerated.
• →When mocking a frontend auth context, decode the payload with atob() and pass the claims object directly to your AuthContext provider to simulate a logged-in state.
• →Use the jti (JWT ID) claim as a unique identifier in tests that verify token-revocation logic — each generated token has a distinct jti value.

FAQ