Obfuscate JavaScript code to make it harder to reverse-engineer with variable renaming and control flow transformations.
Paste in JavaScript and receive a rewritten version that is deliberately hard to read: meaningful variable names become short or random labels, if/else chains and loops are reshaped into dispatch structures, and string literals may be pulled into an encoded pool that the code fetches at runtime. The output is meant to run with the same observable behavior while removing the structure a human reader would lean on. The thing users most often get wrong is treating the result as protection: obfuscation is deterrence against casual reading, not security, and the underlying logic still ships to every browser that executes it.
Identifiers that are local to a function or block are replaced with short or meaningless names, so a name like `invoiceTotal` comes back as something like `a` or `_x2`. Because renaming touches only scoped identifiers, behavior does not change, but every hint of author intent in the naming is gone. Names other code depends on, such as globals and properties read by other scripts, are typically left intact.
Conditionals and loops are rewritten so the code no longer reads in the order it executes: conditions can be inverted, blocks moved, and nested branches flattened into a loop that dispatches between states. A reader following the output line by line loses the high-level shape of the original program. The trade-off is real: transformed code is larger and slower, and the cost grows with how much structure is flattened.
No. Every technique here - renaming, control-flow reshaping, string encoding - can be undone, and deobfuscation tooling exists. The tool runs in your browser and nothing is uploaded, but the output you ship is still read by anyone who loads the page. A determined analyst will recover the logic; obfuscation buys time, not secrecy. Anything that must stay secret belongs on a server you control.
It is designed to: renaming and control-flow transformations are behavior-preserving by construction. Still, verify before shipping - run your test suite against the obfuscated build, not just the source. The output is bigger and slower, and debugging it later is painful, so keep the original under version control and record the settings used for each build.
The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Generate strong, random passwords with customizable length, character sets, and complexity requirements.
Analyze password strength with entropy scoring, crack-time estimates, and improvement suggestions.
Create cryptographically random strings for API keys, tokens, salts, and unique identifiers.
Create QR codes for URLs, text, Wi-Fi credentials, vCards, and more with customizable size and colors.
Scan and decode QR codes from uploaded images or your device camera to extract embedded data.
Compute MD5, SHA-1, SHA-256, and SHA-512 checksums to verify file integrity and detect tampering.