About JavaScript Obfuscator

Built for teams that need practical JavaScript protection.

Shipped continuously since 2004 by a small team focused on one thing: making client-side JavaScript harder to reverse-engineer without making your release flow heavier.

Trusted across web, embedded, and enterprise JavaScript projects since 2004

2004 Continuously shipping for 22 years
4 Shipping paths: online, desktop, API, npm CLI
Toronto Built and supported in Canada
Anti‑LLM Per-build polymorphic protection

About JavaScript Obfuscator

JavaScript Obfuscator is developed by Richscripts Inc, a privately held software company based in Ontario, Canada. We have been continuously shipping the product since 2004.

Our focus is straightforward: help teams reduce the readability of shipped JavaScript, preserve application behaviour, and fit protection into real release workflows without unnecessary friction.

What we build

We maintain four distinct surfaces for the same protection engine, each suited to a different release constraint:

Online obfuscator

For quick before-and-after evaluation, single-file tests, and shareable previews. No installation, no signup for free-tier limits.

Desktop application

For larger projects, batch processing, and JavaScript embedded in HTML, PHP, ASP, ASPX, and JSP templates. Source never leaves the workstation.

Hosted API and npm CLI

For repeatable release automation. The HTTP+JSON API works from any pipeline that issues HTTPS requests; the npm package drops into Node-based CI.

Documentation

Practical guides for command-line usage, cross-file configuration, release sequencing, and compatibility validation — written from real shipping constraints.

What we care about

Long-term reliability

The same product, same site, same team since 2004. No abrupt direction changes, no shutdown risk for buyers planning multi-year deployments.

Practical security

We protect against the threats teams actually face today — LLM-assisted reverse engineering, automated deobfuscators, casual inspection — not against fictional ones.

Workflow first

Protection that requires a tooling rebuild is protection that gets skipped. Every surface is designed so it drops into existing pipelines without architectural changes.

Honest support

Real engineers reply to support email. We ship release notes, document tradeoffs, and tell customers when a feature isn't a fit for their use case.

How teams use it

Some customers protect a single script before launch using the online tool. Others run the desktop app over directories to preserve naming across files and standardise options for repeatable production builds. The largest deployments wire the npm CLI or hosted API into CI/CD so every release ships with up-to-date polymorphic protection.

Our customer base spans software vendors, agencies, universities, internal enterprise teams, and public-sector organisations — anyone who needs an established way to make shipped client-side code harder to reverse engineer.

Milestones

2004

Initial release

Desktop JavaScript obfuscator launches under the Richscripts Inc banner in Toronto, Canada.

2010s

Hosted API + online preview

Browser-based preview tool and HTTP+JSON web service make protection accessible without a desktop install.

2024

Anti-LLM Maximum mode

Per-build polymorphic decoder, encrypted constants, and flat control-flow transforms ship to defeat LLM-assisted deobfuscation.

2026

VM bytecode protection

Selective per-function virtualisation enters Maximum mode for Corporate+ tier — selected hot functions compile to opcodes and run on a per-build VM interpreter.

Get in touch

Real engineers reply to email. Pick the address that matches what you need:

Support [email protected]
Sales [email protected]
General [email protected]