Not sure what you’re looking at? Paste anything and we’ll identify the encoding — JWT, PEM, data URI, hex, URL-encoded, or Base64 — and route you to the right tool with the input pre-loaded.
JSON Web Tokens (three-segment, dot-separated), PEM-encoded blocks, data URIs, HTTP Basic Auth headers, URL-encoded text, hex strings, and standard or URL-safe Base64. The detector also examines decoded bytes to suggest whether it’s an image, document, or plain text.
JSON Web Tokens (JWT), PEM blocks, data URIs, HTTP Basic Auth headers, URL-encoded text, hex strings, and Base64 in both standard and URL-safe variants. The detector also examines decoded bytes to suggest whether the content is an image, document, or plain text.
Multiple checks run in parallel — pattern matching for structural markers (dots in JWTs, BEGIN/END in PEM), character set analysis (does the input contain only Base64-alphabet characters?), and validation by attempting to decode. Each candidate gets a confidence score; the highest wins. Alternatives are shown if confidence is below 95%.
Not by content — encrypted data looks random by design. The detector can identify standard wrappers around encrypted data (PEM-wrapped encrypted keys, JWE tokens) by their structural markers, but the encrypted payload itself appears as opaque Base64 or DER bytes.
The detector returns the most likely interpretation but is not infallible. The "Other possibilities" section shows other candidates with their confidence scores, so you can manually pick the right tool if needed.