Quick start
If you want a fast path to automating obfuscation outside the desktop UI, start here. Most teams land on the npm CLI within an hour.
Cross-language clients & API
Same protect() shape in nine languages. Where the shipped clients don't cover your runtime, write your own from the wire-format spec.
Stack-trace symbolication & runtime defense
Production crashes carry mangled names. JSO's symbolicator demangles them locally; runtime-defense beacons can land in the dashboard, Slack, Discord, or your SIEM.
Recipes
Copy-pasteable answers to real customer questions: git-tag-as-label, blue-green key rotation, BuildId injection, SIEM routing.
Migrate to JSO
Opinionated, one-page migration guides for the two most common starting points.
JSO AI
Optional AI help for guided protection choices, compatibility checks, error explanations, and protected-release review. Browser previews and BYO OpenAI / Claude keys are available now.
Procurement & evaluation
Numbers-first reference for vendor reviews, security audits, and "do you ship a thing for X" triage.
Most-used options
These are the settings most teams touch first when dialing in their protection level and output style.
Advanced workflows
When your files depend on each other, jump into the cross-file guides and deeper protection options.
Command-line workflow
Best when you want repeatable builds, CI-friendly steps, or a fast path into automated obfuscation.
Open guide
npm CLI workflow
Run JavaScript Obfuscator from package scripts and CI after your frontend build emits JavaScript assets.
Open npm guide
JSON config presets
Save and reuse online tool settings, including Standard options, premium preview features, and Variable Exclusion patterns.
Open preset guide
Compatibility validation
Review browser checks, source-map policy, exclusion rules, and protected-release smoke tests before deployment.
Open validation guide