Developer Tools

Runs locally. Your tokens and data never leave your browser.

JWT structure

header.payload.signature

header: algorithm + token type

payload: claims (sub, exp, iat, custom data)

signature: verification (can't decode without secret)

Cron syntax

┌───────────── minute (0-59)
│ ┌─────────── hour (0-23)
│ │ ┌───────── day of month (1-31)
│ │ │ ┌─────── month (1-12)
│ │ │ │ ┌───── day of week (0-6, Sun=0)
│ │ │ │ │
* * * * *

0 9 * * 1-5 → 9:00 AM, Mon-Fri

*/15 * * * * → every 15 minutes

0 0 1 * * → midnight, 1st of month

Base64 basics

Base64 encodes binary data as ASCII text. Common uses: data URLs, basic auth headers, embedding images in JSON.

Hello World → SGVsbG8gV29ybGQ=

{"key":"value"}eyJrZXkiOiJ2YWx1ZSJ9

JSON ↔ XML mapping

{"name":"John"}<name>John</name>

{"items":[1,2]}<items><item>1</item><item>2</item></items>

Also generates XSD schemas with auto-detected types: xs:integer, xs:boolean, xs:date

Security note: All decoding/encoding happens in your browser. JWTs often contain sensitive data — we never see them. Check the network tab if you don't believe us.