String Obfuscator
Obfuscate and deobfuscate strings using common encoding techniques.
Convert a plain string into Unicode escapes, HTML entities, hex character codes, or Base64 — and back. Useful for casual concealment of strings in shipped code, templates, and pages, with the understanding that this is not encryption.
Common use cases: hiding email addresses from the simplest scraping bots, concealing API endpoint hints in shipped JS, making config strings less easy to grep in stack traces, and demonstrating different string-encoding formats.
Original Text
Obfuscated
Frequently asked questions
Is obfuscation the same as encryption?
No. Obfuscation just makes a string visually unintelligible — anyone with the algorithm can reverse it. Encryption requires a secret key and is mathematically infeasible to reverse without it. Never use obfuscation to protect secrets.
What is obfuscation actually useful for?
Casual concealment — hiding API endpoint hints in shipped JavaScript, stopping the easiest copy-paste of email addresses from a page (briefly), making debug strings less greppable. It buys minutes, not security.
Why obfuscate an email address on a webpage?
To slow down naïve email-scraping bots that grep pages for
@. Sophisticated scrapers render the page with a real browser and read the visible text anyway, so this is a marginal defence. Modern alternatives: contact forms or anti-spam services.Will the output still work if I paste it into code?
It depends on the technique. Unicode escapes (
\u0061 for "a") work in JS string literals. HTML entity encoding works in HTML text content. Base64 needs to be decoded at runtime. Pick the technique that matches the target context.