JWT Empty Segment – Fix Missing Header, Payload, or Signature

Local only

Identify a missing compact JWT segment even when two separators are still present.

50 chars · 1 line

Needs attention

Enter a JWT with three non-empty dot-separated segments

JWT structure error

How to fix an empty JWT segment

A token can contain two dots and still be malformed when the text between two separators is empty. The decoder rejects an empty header, payload, or signature before attempting to decode claims. This tool is free to use. No account or payment is required.

Last updated

What you can do here

  • Browser-local JWT decoding
  • Strict three-segment validation
  • Canonical Base64URL checks
  • Header and payload JSON validation
  • Expiration status details
  • No signature verification claims

Steps

  1. Look for consecutive dots or a leading/trailing dot.
  2. Identify whether the missing position is header, payload, or signature.
  3. Retrieve the original complete token instead of fabricating the absent bytes.

Separators alone do not make a complete token

The decoder checks both the number of segments and whether each segment contains data. This prevents an empty payload or signature position from being mistaken for a valid compact JWT.

Empty payload segment example

Two separators are present, but the payload between them is missing.

Invalid token shape

header..signature

Required shape

header.payload.signature

Common questions

Frequently asked questions

Why does header..signature fail if there are two dots?

Because the middle payload segment is empty. The decoder requires three non-empty segments.

Can I replace the missing payload with {}?

That would create different token bytes and would not restore the originally issued JWT or its valid signature.

Can an unsigned JWT have an empty signature?

This decoder intentionally requires a non-empty third segment and does not use decoding as a substitute for verification.

Debugging a specific JWT issue? Browse JWT troubleshooting.