estrogen obfuscator

estrogen rewrites built JavaScript so a reader pays more to make sense of it. It is not secrecy: a decoder key ships in each file, right next to the data, and anyone with devtools can run the code back. This page runs the real engine, compiled to WebAssembly, entirely in your browser. Nothing is uploaded. Install it from npm as @sysce/estrogen.

Try dropping a .js file here, or click to choose one to upload.

Empty means fresh random keys each run, so the output changes every time. A value makes the output deterministic: the same source and seed give the same bytes, so a build repeats.

What this does

estrogen's app-chunk pass moves string and template literals into a per-file ChaCha20 pool and prepends the decoder. Identifiers and structure are left as-is in this browser demo.

The limit

The decoder key ships in the output, right next to the data, and devtools can run it back. This raises the cost of reading a build. It is not secrecy.

loading engine...

FAQ

Why would I obfuscate my JavaScript?

To raise the cost of reading a shipped build. estrogen removes the plain string and template literals from the source and puts them in an encrypted pool, so a reader can no longer grep for a message, a URL or a key name and land on the line that uses it. That slows down copy/paste reuse and casual inspection. It does not stop a determined reader.

Is this foolproof?

No. estrogen never claims secrecy. The browser has to run the code, so the decoder and its key ship in the same file as the data. Someone with the time and patience can run the decoder themselves and recover the strings. The point is cost, not a lock.

Why is the output larger than my source?

Because the pass prepends a decoder and stores the literals as an encrypted, base64 pool, which is bigger than the plain text it replaced. There is a lot of repetition in the decoder, so the output compresses well with gzip or brotli on your server.

Does it work on any JavaScript?

It works on standard JavaScript that parses. The browser demo runs one source string at a time through the app-chunk pass. If the input has no poolable string or template literal, the pass reports zero edits and the output matches the input.

Do you store my source?

No. There is no server. The engine is WebAssembly running in this page, so your code never leaves your browser.

The interface is derived from javascript-obfuscator-ui (BSD-2-Clause) by Timofey Kachalov and Tiago Serafim. The engine is estrogen. See third-party licenses.