Tools / Credential parser
Credential parser
Delimiters vary product by product — pipes, colons, semicolons and tabs all appear. Paste it and each field gets identified.
🔒 Processed entirely in your browser and never sent to us or any server. Works offline.
How it decides
By format alone, with no login involved. Long strings of only A–Z and 2–7 are 2FA secrets; anything with an @ is an email; eight or more digits is an FB or BM ID. The rest is usually username and password, in an order that varies by product.
What it does not do
It will not tell you whether the account is alive. Only an actual login answers that, and any service claiming to check for you needs your credentials first — a far worse trade than the time it saves. Log in yourself, following the acceptance SOP.
The acceptance SOP: a 30-minute checklist · 2FA code generator
FAQ
Why does the delimiter differ between products?
Because upstream is several suppliers each shipping their own format. We have seen pipes, colons, semicolons and tabs in practice. This tool picks whichever delimiter yields the most fields, which is more reliable than hardcoding one.
How does it identify the 2FA secret?
By format. Base32 uses only A-Z and 2-7 and the string is long — a signature nothing else in a credential shares. Anything with an @ is an email; eight or more digits is an FB or BM ID.
Does it send my password anywhere?
No, and you can verify it: disconnect from the internet and it still parses. A credential parser that uploads credentials is a phishing page by definition.
Can it tell me whether the account is still alive?
No — it reads format and never logs in. Any service claiming to verify liveness needs your password first, which is a far worse trade than the time it saves. Log in yourself following the acceptance SOP.