The command-line workflow lets you run JavaScript Obfuscator automatically with the project settings you already configured in the desktop application.
Typical workflow
- Create a project in the desktop app.
- Add the files you want to protect and configure the options in the GUI.
- Open Tools > Command Line to generate the command.
- Copy that command into a Windows command prompt, script, or automation step.
Why teams use it
This is the easiest path into repeatable builds because the desktop project stores your configuration and the command line reuses it without asking you to recreate every setting by hand.
Where it belongs in automation
Use the generated command after your normal build produces the JavaScript files you plan to ship. In other words, let your existing toolchain emit the final browser assets first, then run JavaScript Obfuscator on those output files or folders.
Build app
Generate JavaScript assets
Run the generated obfuscator command
Test protected output
Publish release artifacts
Related guides
If you are deciding how the desktop project fits into a broader release process, continue with Build and Release Workflows. If your application exposes public names or shared identifiers, also review Variable Exclusion List and the cross-file guides.
Need runtime integration instead? if you want to protect code dynamically instead of calling the generated command line, start from the main product downloads and integration area at
Download Desktop.