This JavaScript obfuscator is intended to be used as a resource to convert human-readable JavaScript into a more shrouded code. This serves two purposes:
Generally, the code from the first textarea is copied into the second one.
Note: If you get errors with the output code, it may be because your source does not have semicolons (;) terminating each line.
Please report any bugs, fixes, or suggestions to help make this tool better and remember, always keep the original code!
Loop through all lines in the text area. If a line has no semicolon at the end, add one and then join it to the previous line.
Loop through all lines in the text area. Trim all white space from each line. If the first two characters are forward slashes (//), remove that line.
| Version | Date | Description |
|---|---|---|
| Version 1.0 | 9/06/2008 | The Beginning |
| Version 2.0 | 09/06/2008 | Simple Options - Remove comments & Remove line breaks |
| Version 3.0 | 09/06/2008 | Remove spaces option added |
| Version 4.0 | 24/12/2008 | Adapted joliclic.free.fr's JavaScript packer |
| Version 5.0 | 08/01/2009 | Use POST variables for AJAX to increase max length |
Awesome!!!
By Iman on 13th July 2021Cool! Thnks!!!!!
By Dima on 21st December 2019Best tool!
By MilkMan PRO(script dev) on 9th October 2019loved it. used it for a couple projects . . . used other obfuscation methods and the used this to finalize it :D
Not only obfuscated my code, it also made it marginally more lightweight. This tool is better than any other online obfuscator I've tested.
On 4th August 2019Awesome! Very useful. Thanks a lot!
By WallyDanny on 27th April 2019Great Job !!!
On 14th February 2018Good job team, fine work!
By Miguel on 7th April 2017I did never expect this!
On 1st April 2017Great Work!
By Sistepa on 17th March 2017Thanks
By Colombia on 25th January 2017You had a bug when use a for loop like for(a=b;;) { c = d;} It will replace ;; by ;
By Nam Nguyen on 27th May 2016T. Jaggar, thanks for the suggestion. We will look in to this,
By Daft Logic on 10th May 2016I used this tool for some time now and really like it. I usually upload my scrips on our test environment, and when they work fine I compress them here and place the compressed version on preproduction then production. Based on my way of working, I was thinking of a great addition you could add to it: Allowing a special markup for sections that the tool should remove, and which it would do first. That would allow to have the script with some tracing or debug statements, yet ensure those are gone for prod. If, for example, it was removing all found between DEBUG and /DEBUG and , we could do code like this:
var x = someImportantStuff(); /* DEBUG */ console.log("result of important stuff is " x); /* /DEBUG */ continueNormalThings();
D McLean, sorry this was the remnants of an older version of this page
By Daft Logic on 2nd February 2016I do not see the checkboxes referred to in paragraph above:
"...numerous functions that each are triggered by the options/check boxes."
Very Thankssss !!!!!!!!!!!!!
On 20th November 2015goood
By names on 26th August 2014Amazing Tool, Thanks a lot!
By s on 11th July 2014Now this is awesome
20 out of 99 comments shown.
There's no need to create an account or provide unnecessary details. Just your comment.