Fewer tabs between a bug report and a fix
Debugging is mostly small translation jobs. Make this payload readable. See what is inside this token. Turn this icon into a component. These tools do the translating in your browser, so you can paste real payloads and tokens without sending them to somebody else's server.
Pick by task
| If you need to | Use |
|---|---|
| Read, validate or shrink a JSON payload | JSON Formatter |
| Inspect token claims, verify an HS256 signature or build a test token | JWT Encoder/Decoder |
| Turn an image into a Base64 string or data URL, or back again | Base64 Encoder/Decoder |
| Percent-encode a query value or read an encoded one | URL Encoder/Decoder |
| Hash text with SHA-256, SHA-512 or MD5, or compute PBKDF2 and HMAC values | Hash Generator |
| Preview Markdown or MDX while you write | Markdown Previewer |
| Browse the tables and schema of a .db, .sqlite or .sqlite3 file | SQLite DB Viewer |
| Turn raw SVG into a React component | SVG to React JSX |
Know the limits before you start
A few honest notes save time. The JWT tool verifies HS256 signatures only. The Base64 tool works with images rather than arbitrary text. The SQLite viewer is for browsing, sorting, searching and exporting to CSV or JSON, and it does not yet offer a SQL console or open encrypted databases. The Markdown Previewer detects MDX but shows JSX tags as plain text instead of running them.
A habit worth keeping
Decoding is not trusting. Anyone can read a JWT payload, and a hash is not encryption. Use these tools to inspect and debug, and keep real verification and secrets on your server.