Can AI tools read code protected by JavaScript Obfuscator?
No obfuscator can promise that determined attackers will never understand public JavaScript. JavaScript Obfuscator raises the cost by removing readable names, hiding strings, scrambling structure, and changing stronger protected output across releases. Use Maximum mode for the code that matters most.
Does JavaScript Obfuscator offer advanced protection for sensitive code?
Yes. Corporate and Enterprise customers can review advanced protection options for the most sensitive parts of a project. Most customers should start with Standard, Balanced, or Maximum mode and contact support if a small set of functions needs heavier protection.
When should I use Maximum mode?
Use Maximum mode for public JavaScript that contains valuable business logic, licensing checks, paid-feature gates, or code you do not want copied easily. Use lighter modes when speed, file size, or compatibility matters more than maximum protection.
Is JavaScript Obfuscator compatible with ES6 or ES8?
Yes. JavaScript Obfuscator is compatible with ES6 and ES8, and new engine support continues to be added over time.
Is it possible to recover the original file from an obfuscated version?
No. The protected file is intended for release, not for editing. Keep your original source files safely stored because the obfuscated version cannot be turned back into the original project.
Can JavaScript Obfuscator protect JavaScript that is embedded in HTML?
Yes. JavaScript Obfuscator Desktop can also protect JavaScript embedded in HTML, PHP, ASP, ASPX, JSP, and similar files.
Does JavaScript Obfuscator optimize for speed?
In many cases, smaller code is faster code because download time is a major performance factor. Reducing redundancies can also help runtime efficiency.
Are there any restrictions on the size of the files that can be obfuscated?
JavaScript Obfuscator Desktop does not have a maximum file size limit for your project files.
Can I keep an exclude list of variables and functions that should not be obfuscated?
Yes. JavaScript Obfuscator Desktop lets you create a list of names with specific settings so selected variables and functions can remain unchanged.
My project has several files that call functions in each other. Will JavaScript Obfuscator protect it correctly?
Yes. The protected version of the same symbol stays consistent across every file in your project.
Where does JavaScript Obfuscator fit in a modern project?
Use the online obfuscator for quick checks. Use the desktop app when you need larger folders, local-only work, or JavaScript embedded in mixed files. Use advanced integrations only when a technical team wants protection connected to a repeatable release process.
Can my team automate protection?
Yes. Technical teams can connect JavaScript Obfuscator to existing release tools. Most customers should first choose the protection settings in the online or desktop product, then involve a technical owner if automation is needed.
How do I troubleshoot errors after protection?
Keep the protection report generated with the protected output. It helps technical teams translate protected error reports during troubleshooting while keeping sensitive mapping data under customer control. There is also an interactive browser demo you can try with sample data.
What is the release identifier for?
It is a technical identifier for a protection run. Most customers do not need it directly, but technical teams can use it to match a protected release with the report created during protection.
Is there an IDE integration?
Yes. VS Code and JetBrains editor options are available for technical users who want to protect a file or selected code without switching windows. See the ways to use JavaScript Obfuscator.
I'm currently using Jscrambler / the OSS javascript-obfuscator package. How do I migrate?
Two migration guides cover the common cases: migrating from Jscrambler and migrating from a free JavaScript obfuscator. They explain feature differences, product fit, and practical steps for moving to JavaScript Obfuscator.
Can JavaScript Obfuscator alert us about tampering?
Runtime defense options can send events to a customer-controlled destination when protected code detects certain tampering conditions. Teams that need dashboards and incident response should pair JavaScript Obfuscator with a monitoring platform.
When does JSO AI ship and what does it cost?
JSO AI is an optional add-on planned to help customers choose settings, check compatibility, and understand protection issues. See the pricing page for current preview details and availability.
Can I use JSO AI without buying obfuscation?
Yes. JSO AI subscribes independently from the obfuscation tier. Free-tier obfuscation customers can add AI Basic and get the preset assistant, compatibility checker, and config-help chat layered on top of the free engine. The two products are independently subscribable and independently meterable.
What does the AI feature send to the AI provider, and where does it go?
Customer code submitted to AI features is processed in memory under the same no-persistence policy as the protection workflow. AI features show a pre-submission notice, and organizations can disable AI features at the account level.
What happens when I run out of AI actions?
Hard quota by default, no surprise overages. Each AI tier comes with a fixed monthly pool of AI actions plus a separate protection token pool; both are displayed live on the dashboard. When you hit either limit the AI features degrade to "explain the action and link to the upgrade path" mode — they never silently bill more than your tier. Overage as an opt-in toggle may ship in a later phase.
Do you keep my JavaScript source code?
No. Source code obfuscation is processed in server memory, and you do not need to upload JavaScript files to the server. For more details, please review the Terms of Service and Privacy Policy.