What this tool does
Attempts to identify unknown encodings/transformations by testing common patterns (hex, base64, URL encoding, gzip markers, etc.).
This page focuses on practical, step‑by‑step usage for **Custom Encoding Detector**, with clear examples and common pitfalls.
When you should use it
Use it when you receive a mysterious blob/log field and need a starting point for decoding.
How to use
- Paste the suspicious string.
- Run detection to see likely encodings.
- Apply the suggested decode path and re-check.
Quick example
Example: Detect that a string is URL-encoded Base64, then decode in two steps.
Notes
Detection is heuristic—verify results by checking whether the decoded output is meaningful.
Custom Encoding Detector
Advanced automatic encoding detection with confidence scoring and detailed analysis
Common Encoding Patterns
Advanced Encoding Detection
Professional encoding detection and analysis tool for security researchers, forensic analysts, and developers. Automatically identify and decode various encoding schemes with confidence scoring.
Supported Encodings
Base64 Variants
Standard Base64, URL-safe, with and without padding
Numeric Encodings
Hexadecimal, binary, decimal representations
Text Encodings
ROT13, ROT47, URL encoding, HTML entities
FAQ
Is Custom Encoding Detector encryption?
No. It is primarily an analysis/encoding utility. If you need confidentiality, use a real encryption scheme and manage keys properly.
What should I do if the input fails to decode/parse?
Start by checking for missing padding, wrong alphabet/variant, or extra whitespace. If the data looks multi-layered, try decoding step-by-step (e.g., URL decode → Base64 decode).
Is it safe to paste sensitive data here?
For best security, avoid pasting real secrets (private keys, live tokens, seed phrases). Use test data or work offline, especially for anything that could grant access or move funds.