What's new in
JScrambler 3.8

Rename All, Risk None

Automatic and safe renaming of all identifiers is hard in JavaScript because the language is too dynamic. Up until now, every time you used Rename All, you had to double-check for broken naming references, and exclude them from being renamed. This often led people to use Rename Local instead of Rename All.

In 3.8, we included two new modes to control how renaming works and easily select which identifiers should be targeted. From now on, you will be able to have fine grain control over the public identifiers that are renamed.

Unsafe Mode

It leaves out all identifiers that are part of HTML5/JS native APIs but it renames all the rest, regardless of whether they are defined or not.

Safest Mode

Can’t go wrong with this one – this mode only renames identifiers whose definition can be found inside the source code.

Whats New 3.8

Include & Exclude List

Regarding the Unsafe and Safest modes, you’ll be able to specify identifiers inside two different lists. This way power is yours and errors or unwanted renaming will be gone forever:

Include List - there's an identifier you really want to rename? Put it in this list. Identifiers placed here will be renamed, whether their definition is found or not (Safest Mode);

Exclude List - if any identifier is present here, it won’t be renamed. If your code somehow stops working, you can pick the identifier that is causing the issue and make sure it will be excluded from the targets, end of story!

Whats New 3.8

JScrambler 3.7 now supports
all the main JavaScript
libraries and frameworks

Developed to guarantee that all JavaScript libraries and frameworks can be protected safely. We paid attention to detail and made JScrambler more compliant than ever so that you can protect your JavaScript and HTML5 whatever your technology stack may be.


Compliant like no other

JScrambler already supported most of the W3techs’ top ten most used JavaScript libraries such as JQuery, MooTools, Backbone.js, Marionette.js, Ember.js and Knockout. With 3.7 we went even further and made JScrambler the most compliant protection tool in the market, supporting all the libraries and frameworks developers normally use. It can now handle special cases where some transformations need to behave differently, for instance, cases like AngularJS custom HTML attributes that contain names of Angular custom modules and controllers or the example of module loaders (RequireJS) that load scripts that oblige some transformations to behave differently. For a complete list take a look here.


Compliance logos


Staying Sharp

Our continuous integration process is one of our main priorities in order to make sure JScrambler keeps compliant at all times, like no other. We have developed an automatic process to ensure compliance with all current libraries and frameworks. This is a very important step to ensure the quality of our product. You will have access to our compliance tests so you can check everything yourself. You can even suggest your own, or third party, libraries to be tested here.


Preparing for JavaScript’s future

At JScrambler we take as mission to always be ahead of the adoption of new technologies. JScrambler 3.7 lays the foundations to support ECMASCRIPT 6 (Harmony), which will soon be compliant with all browsers, by introducing JavaScript strict mode compatibility and Harmony’s generators protection. These are the first steps to our next major release which will aim to support the Harmony’s features as soon as they come available on major browsers.


ECMAScript 5


Faster and Easier

From now on Atom, the new text editor by GitHub made in JavaScript, will be integrated with JScrambler to make your obfuscation requests quicker and effortless . We’ve developed a plugin that allows you to request obfuscation directly from the editor. You can check it out here, and contribute to our GitHub repository. Protecting your code has never been this easy!





Another Channel to your Users

When using our Domain Lock and Expiration Date feature you can now inform your application's user about why the application stopped working when trying to run it with an invalid domain or after the code expired, right at the spot. The communication with your users gets easier, their experience with your app improves and your sales go up!


Domain Lock Alerts

What's new in
JScrambler 3.6


JScrambler is now
compliant with Node.js


JScrambler for Node.js applications

With Node.js, JavaScript can be used outside the context of a Web Browser, both on the server and client sides. It can also be built outside the browser and later be packed and executed inside the browser. This flexibility and elegance surely contributed to its popularity.
However, whether you’re working on a library distributed through NPM, a standalone client or a browser application, and like regular web applications developed using JavaScript, it is still sent or installed in clear-text in the end-user device. If are using shared or hosted servers, you may be worried to know that your code is stored in clear-text.

Node Support

Easy integration
with your build setup


API Clients


Whether you build your application using a command line script or a task runner it’s very easy to integrate JScrambler in your existing building process. JScrambler is already integrated in all major task runners and if that does not work for you, we have a JScrambler API CLI executable that you can all from your scripts or your favorite IDE. There’s also a Node.js API client that you can use if none of the above solutions suits you.


Minification and
Compression for free


Minification and Compression



From now on you can minify and optimize your JavaScript applications with JScrambler for free! Minification and optimization are industry standards which you can get from JScrambler using our easy to use Web Application Interface or integrating it in your build process using our Web API and one of the ready to use API clients.

JScrambler 3.5



Protection breakthrough:

JScrambler continues to innovate in JavaScript protection. JScrambler 3.5 introduces Self-defending capabilities to HTML5 and JavaScript applications.
Now your application is able to actively protect itself by detecting source code modification attempts and debugging activities, and breaking down intentionally to mitigate the attack. And all it takes to trigger this defense is a single character being changed.

Self Defending

New Code Traps for
improved licensing enforcing


Code Traps


Browser lock

Does your application require some browser specific feature? By using Browser lock, you can now make sure it won’t run if a different browser is used.


OS lock

If you developed an HTML5/JavaScript for a certain mobile that you don’t wish people to be able to execute it on a different platform, with or brand new OS lock you can enforce it.

Greater control of the
source code transformation

Now you can instruct JScrambler while you're writing JavaScript!

No one knows your application better than you. Then you should be able to tell JScrambler how to behave in certain parts of the code. You may want to bring all the guns to protect a certain security sensitive part where you keep a secret, or you may want to cut a little bit on the obfuscation in performance critical parts of your code. The "Ignore code blocks" brings the power of source code annotations: with a simple annotation you can disable or switch between transformations just on specific block of source code.

Greater Control

Presence in Media

  • Tech Crunch

    Today’s release introduces a number of new code transformations, as well as a new subscription package for professional users who need to support for mobile and desktop apps

    Frederic Lardinois Tech Crunch

    The Next Web

    JScrambler, a tool for making your code harder to read and manipulate, has today been updated with a self-protection feature.

    Martin Bryant The next web