warningObfuscation does not encrypt code or protect secrets. Check the result before publishing: more intense profiles can significantly increase the size and reduce performance.
Transforms JavaScript or TypeScript code into a functionally equivalent version that is much harder to read and reverse-engineer. It renames identifiers, restructures the flow, and hides text strings.
It offers intensity profiles (for example, lighter or more aggressive) and target destinations depending on where the code will run, to balance protection and performance.
Processing runs entirely in your browser, without sending the code to any server. Obfuscation makes reading harder, but it is not encryption: a determined attacker can still analyze the result.
function greet(name) { return "Hola " + name; }
var _0x1a2b=['Hola\x20'];function _0x3c(_0x4d){return _0x1a2b[0x0]+_0x4d;}
No. Obfuscation makes the code hard to read, but it still runs as-is in the browser. It is not encryption: anyone with time and tools can analyze it. Never hide real secrets, such as API keys, in client-side code.
It can. The more aggressive profiles add layers of protection that increase the size and may slow down execution. Choose the profile according to the balance you need between protection and speed.
There is no function to undo it, and the original names and comments are lost. Always keep a copy of the un-obfuscated source code before generating the protected version.
No. Obfuscation runs entirely in your browser; the code never leaves your computer.