After downloading: your first project
- Keep your original files and choose a separate output folder.
- Check whether your selected engine runs locally or uploads source to the hosted service.
- Review plan eligibility for the options you intend to use. A free download does not mean every protection option is free.
- Start with a representative sample, then run your application's tests against the protected output. Use the compatibility validation guide before publishing.
Need help? Send support your app version, Windows version, selected engine mode and error message. Do not include your password or API key.
Stuck on your first project?
I paid, but a feature still asks me to upgrade
Check that the API key belongs to the same account as your active order, then check the named feature against your plan. VM access also requires enrollment. Repeating the same request will not resolve a plan restriction. If your purchase should include the feature, contact support with your order reference and the exact error before buying again.
The app asks for my key again after restarting Windows
This does not by itself mean your password changed. Check that you are using the same Windows user and app version. Record whether you launched a different extracted copy or ran as another user. Send support the app version, Windows version, and when the prompt returns. Do not send your password or API key, or reset credentials just to troubleshoot a saved-login issue.
Protection finished, but my application does not work
A generated file is not proof that the application still works. Keep the original source, protect to a separate folder, and run the same tests on both versions. Record the first browser or Node error and the enabled options. Use a small, non-sensitive reproduction when contacting support. Local Standard supports basic ES5; modern syntax needs transpilation or a compatible engine mode.
Contact support with the app version, engine mode and error text. Remove credentials and private source from screenshots and logs.
Frequently asked questions
Which download do I need?
Choose the Windows desktop app to protect files and save project settings. For automated builds, the Windows download includes cli/jso-local.exe. For other integrations, use the Developer tools section and follow the linked guide. Some tools are direct-download packages, not published npm-registry packages.
Do the desktop applications send my source code anywhere?
Local Standard keeps source on your computer and works offline without an account for basic ES5 JavaScript. Local Advanced also keeps source on your computer, but checks your paid plan online. Hosted mode uploads selected JavaScript to the service and is required for VM bytecode protection.
How do I verify a download is the file you published?
Compare the checksum against the published value before running anything. Every public archive is listed with a checksum for exactly this purpose, and verifying is the difference between trusting the file and trusting the network that delivered it. Signed release verification covers the same ground for artifacts produced by your own protected builds.
Are the desktop applications Windows only?
The graphical applications are Windows desktop software, yes. Cross-platform workflows are covered by the npm CLI and the bundler plugins, which run wherever Node runs, and by the HTTP API for anything that needs to be driven from another language or operating system.
Do I need a paid plan to use these?
No account or paid plan is needed for basic ES5 protection in Local Standard mode. Local Advanced requires an eligible paid plan and an online entitlement check. Hosted features depend on your plan; VM protection also requires enrollment. Check the options you need before buying.
How do I know which version I am running?
Check the version shown in the application. In the modern Windows app, protection reports are optional and off by default; enable them when you need a .report.json sidecar. When reporting a problem, include your app version, engine mode and protection options. Test the protected output before publishing it.