Magic decode

Try base64, base32, hex, URL-encoding, ROT13/47 and single-byte XOR against a string and rank the results by how much they read like real text.

Magic decode throws your text at seven guesses at once: base64, base32, hex, URL-decoding, ROT13, ROT47, plus a brute-forced single-byte XOR. Each result is scored on how much it reads like real text, blending printable-character ratio, common-word hits and letter frequency into one number. XOR brute force checks only the first 4096 bytes. A high score is a lead, not proof.

Questions

What decodings does it try?

Base64, base32, hex, URL-decoding, ROT13, ROT47 and a brute-forced single-byte XOR, all against the same input text.

How is each candidate scored?

A weighted mix: 40% printable-character ratio, 30% common-English-word hits, and 30% letter-frequency fit against English.

How much of the input does XOR brute force check?

Only the first 4096 bytes, and it keeps the single best-scoring key out of all 255 tried, not every result.

Does a high score prove the encoding was correct?

No, it is a ranked lead, not proof; the text score can be fooled by coincidentally text-like garbage.

Does it try multi-byte XOR keys?

No, only single-byte keys are brute forced.

Related Forensics tools

n→nDetect file typeIdentify a file by its magic bytes, not its extension;n→nExtract stringsPull runs of printable text out of any binary file: the classic first look at an unknown file.n→nExtract embedded filesCarve out the bytes starting at each detected file signature, up to the next signature or end of file.n→nScan for embedded/appended filesScan every offset for known file signatures: finds a file hidden or appended inside another, e.g. a ZIP tacked onto a JPEG. A match means "signature found here", not "a file was deliberately hidden".1→1File tree from archiveList the paths, sizes and structure inside a ZIP or TAR archive, without extracting anything.n→nTrailing dataFind and carve out bytes appended after a PNG/JPEG/PDF/ZIP/GIF's real end marker, a common place to smuggle a second payload.n→nPolyglot detectCheck whether a file carries more than one valid format signature, at offset 0 or buried inside, the hallmark of a polyglot file.n→1Folder hash manifestHash every file you drop and produce a manifest in the same `<hex> <name>` format `shasum`/`sha1sum`/`md5sum` print, for spot-checking against the real tool.