Type once and watch the text bend into lookalike letters, scrambled words, or invisible marks - the kind of thing an automated reader trips over but a person still understands.
A crawler reads text literally. It matches strings, scans for patterns, and files away whatever it finds. Change enough of those characters and the pattern collapses - yet a person, who reads by shape and context, barely notices the difference.
That gap is the whole idea. Obfuscation lives in the space between how a computer reads and how you do.
It is not encryption. There is no key, no promise of secrecy, no way to guarantee the original can never be recovered. Think of it more like fog than a vault. Fog is enough to stop a passing scraper from harvesting your email address off a page, or to keep a spoiler out of the preview snippet a chat app auto-generates. It is nowhere near enough to protect a password. When the stakes are real, reach for genuine text encryption instead and treat this tool as the lightweight cousin it is.
Each method distorts text differently, and the right one depends on where the masked words will live. Here is a single phrase run through every disguise, so you can feel the trade-off between how hidden it is and how easily a person can still read it back.
meet me at noonCyrillic swaps, still readablemeet me at noonInner letters shuffled on longer wordsteem em ta noonEach word flipped end to endm33t m3 @7 n00nLetters as numbers and symbolsm̃ẽẽt m̊e a̋t n̂o͆o̕nCombining marks pile upmeet me at noonBorrowed Greek and Cyrillic glyphsm·e·e·t m·e a·t n·o·o·nZero-width marks hide between lettersmEeT Me aT nOoNCasing jitters across the stringNotice the pattern. The disguises at the top stay friendly to human eyes; the ones lower down hide more but ask the reader to work harder. The intensity slider lets you dial that up or down inside a single method - nudge it low for a message people skim, push it high when you only care about breaking a machine.
People reach for this in surprisingly ordinary places.
Publishing a contact address in a public forum thread without inviting a wave of spam. Dropping a movie ending into a group chat without the link preview quietly spelling it out. Testing whether your own moderation filters catch a phrase when its letters have been swapped. Studying how confusable characters slip past keyword matching, which is genuinely useful if you build anything that ingests user text.
Because the output is just text, it drops anywhere text goes. Clean it up afterwards with the whitespace remover, normalise the casing with the case converter, or swap specific fragments in bulk using the text replacer. Curious how much a disguise inflates your string? Paste the result into the word counter - invisible characters add length you cannot see.
Worth knowing before you lean on it: obfuscation is a speed bump, not a wall. Modern scrapers normalise lookalike characters and strip zero-width marks routinely, and search engines may ignore or discount heavily masked text - so never obfuscate content you actually want indexed. Keep the untouched original somewhere safe, because some methods scramble text in ways you cannot cleanly undo.
Often, yes. Well-built scrapers routinely map lookalike characters back to plain letters and strip invisible marks. This tool stops casual, automated harvesting - not a motivated adversary. For anything sensitive, use encryption rather than disguise.
Reverse and mixed-case can be undone by eye, but scramble and zalgo lose information you cannot always reconstruct. Treat obfuscation as one-way and always keep a copy of the source text before you mask it.
Yes. The text you paste never leaves your device - obfuscation runs entirely in JavaScript on this page, with nothing sent to a server.
Several methods make random choices, so pressing Reshuffle produces a fresh variation from the same settings. That is deliberate: it makes the disguise harder to reverse from a single sample.
