Guides for protecting production JavaScript

When to use presets

Use presets when you want repeatable settings across browser sessions, team reviews, support requests, or quick comparisons between Standard mode and premium feature previews.

1. Open the online obfuscator.
2. Choose Standard, Balanced Preview, Maximum Preview, or a custom feature set.
3. Adjust Standard options such as string encoding, string movement, and name replacement.
4. Add any Variable Exclusion List patterns that preserve public names.
5. Select Export JSON Preset to save the profile.

What the preset stores

The exported preset is a small JSON file designed for the online tool. It stores configuration only; it does not include source code or obfuscated output.

{
  "format": "javascript-obfuscator-web-preset",
  "version": 1,
  "preset": "standard",
  "standardOptions": {
    "keepLinefeeds": false,
    "keepIndentations": false,
    "encodeStrings": true,
    "moveStrings": true,
    "replaceNames": true
  },
  "advancedFeatures": [],
  "variableExclusionList": "^_get_\n^_set_\n^_mtd_"
}

Importing a preset

Use Import JSON Preset in the online obfuscator to load a saved profile. The page validates the preset format and version before applying it.

If imported features do not match a built-in preset, the tool treats the result as a custom profile. That is expected and useful when you want a team-specific setting set.

Using a preset in npm builds

The npm CLI can import the same exported JSON file and map it to the HTTP API payload. This keeps browser review settings aligned with release builds.

npx jso-protector --config jso.config.json --web-preset javascript-obfuscator-preset.json --dry-run --json

In shared config, use "webPreset": "javascript-obfuscator-preset.json". Standard options, selected premium preview features, and the Variable Exclusion List are applied before any explicit options overrides.

How this differs from desktop projects

JSON presets are lightweight browser profiles for the online tool. Desktop projects are still the better workflow for large codebases, embedded JavaScript, local-only handling, and command-line automation.