We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Free online JavaScript obfuscator to hide your original logic, protect source code, and prevent reverse engineering or unauthorized modifications.
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
Paste JavaScript and choose a transformation for string literals: hexadecimal escapes, Unicode escapes, a lookup array for strings, or a Base64 payload wrapped in eval. Optional switches remove comments and compress whitespace. The output is a transformed text representation intended to be less immediately readable; the available modes do not rename identifiers or perform broad control-flow transformations.
Obfuscation is not encryption. Anyone who can run the code can inspect or recover the strings, and making source harder to read does not prevent modification or reverse engineering. The Base64/eval mode creates source text that is dynamically executed when run. Browser Content Security Policy settings may block that behavior, and dynamic evaluation of untrusted input can introduce security risk.
eval(): documents dynamic source execution and security considerations; checked September 29, 2026. Review the eval reference.Guide
Follow the workflow and verify inputs and outputs with practical examples.
Paste code into the editor or load the built-in sample. Start with a small, non-sensitive snippet while checking how a mode changes strings.
Hex and Unicode modes escape string characters; string-array mode stores strings in an array and replaces literal occurrences with lookups; Base64/eval mode wraps the encoded source in a dynamic evaluation expression.
Comment removal is enabled by default. Whitespace compression is optional and trims repeated spaces, blank lines, and line edges. Review the source first if comments or formatting are meaningful to your workflow.
Copy or download it, then test it in your target browser.
Use cases
See how the tool fits into real work and everyday tasks.
An instructor can transform a short example and compare the readable literal with its hex or Unicode form to teach how strings are represented in source.
A developer can make a casual inspection less immediate, then run functional tests and keep original source available for maintenance.
A reviewer can examine the Base64/eval output shape and check whether the destination page’s Content Security Policy permits dynamic evaluation.
Q&A
Find concise answers to common questions and confusing cases.
No. These transformations make text less direct to read but do not encrypt it or stop a determined reader from recovering it.
No. Policies that disallow dynamic evaluation can block it. Check the target site’s policy and test the exact output in that environment.
No. The listed modes transform string literals and optionally remove comments or compress whitespace; they are not identifier renaming or control-flow obfuscation.
No. It produces transformed text, not a syntax or behavior certification. Test the output with your project’s own checks before release.
Notes
Review scope, result limitations, and important precautions before use.
Do not treat obfuscated output as a security boundary or place secrets in client-side code. The eval-based mode executes generated source and may conflict with browser policy; never execute code you do not trust. Comment removal and whitespace changes can affect unusual source patterns, so preserve the original and test behavior after every selected transformation.
Related
Discover related tools, collections, and available API capabilities.