🍋 Privacy & Security
JWT Decoder
Decode and inspect JSON Web Tokens
chars
words
sentences
lines
Results
Result
About JWT Decoder
Parse JWT tokens to inspect header, payload, and signature. Shows all standard claims with descriptions, expiration status, and algorithm information.
How It Works
JWTs are three Base64URL-encoded segments separated by dots. This tool decodes the header and payload segments and formats them as JSON. The signature segment is displayed as-is (verification requires the secret key).
Step by Step
- 1 1
- 2 .
- 3
- 4 P
- 5 a
- 6 s
- 7 t
- 8 e
- 9
- 10 a
- 11
- 12 J
- 13 W
- 14 T
- 15
- 16 t
- 17 o
- 18 k
- 19 e
- 20 n
- 21
- 22 (
- 23 h
- 24 e
- 25 a
- 26 d
- 27 e
- 28 r
- 29 .
- 30 p
- 31 a
- 32 y
- 33 l
- 34 o
- 35 a
- 36 d
- 37 .
- 38 s
- 39 i
- 40 g
- 41 n
- 42 a
- 43 t
- 44 u
- 45 r
- 46 e
- 47 )
- 48
- 49 2
- 50 .
- 51
- 52 V
- 53 i
- 54 e
- 55 w
- 56
- 57 d
- 58 e
- 59 c
- 60 o
- 61 d
- 62 e
- 63 d
- 64
- 65 h
- 66 e
- 67 a
- 68 d
- 69 e
- 70 r
- 71
- 72 (
- 73 a
- 74 l
- 75 g
- 76 o
- 77 r
- 78 i
- 79 t
- 80 h
- 81 m
- 82 ,
- 83
- 84 t
- 85 y
- 86 p
- 87 e
- 88 ,
- 89
- 90 k
- 91 e
- 92 y
- 93
- 94 I
- 95 D
- 96 )
- 97
- 98 3
- 99 .
- 100
- 101 I
- 102 n
- 103 s
- 104 p
- 105 e
- 106 c
- 107 t
- 108
- 109 p
- 110 a
- 111 y
- 112 l
- 113 o
- 114 a
- 115 d
- 116
- 117 c
- 118 l
- 119 a
- 120 i
- 121 m
- 122 s
- 123
- 124 w
- 125 i
- 126 t
- 127 h
- 128
- 129 e
- 130 x
- 131 p
- 132 l
- 133 a
- 134 n
- 135 a
- 136 t
- 137 i
- 138 o
- 139 n
- 140 s
- 141
- 142 4
- 143 .
- 144
- 145 C
- 146 h
- 147 e
- 148 c
- 149 k
- 150
- 151 e
- 152 x
- 153 p
- 154 i
- 155 r
- 156 a
- 157 t
- 158 i
- 159 o
- 160 n
- 161
- 162 s
- 163 t
- 164 a
- 165 t
- 166 u
- 167 s
- 168
- 169 a
- 170 n
- 171 d
- 172
- 173 t
- 174 i
- 175 m
- 176 i
- 177 n
- 178 g
Tips
- JWTs are signed but NOT encrypted — anyone can read the payload
- Always validate JWTs server-side; client decoding is for inspection only
- The 'exp' claim is Unix timestamp — this tool converts it to readable dates
Frequently Asked Questions
Does this tool verify the signature?
No. Signature verification requires the secret key or public key, which should never be shared client-side. This tool only decodes and displays the token contents.
What are standard JWT claims?
iss (issuer), sub (subject), aud (audience), exp (expiration), nbf (not before), iat (issued at), jti (JWT ID). All are optional per RFC 7519.