About JavaScript Obfuscator

Built for people who need practical JavaScript protection.

Shipped continuously since 2004 by a small team focused on one thing: helping you protect the JavaScript you share with customers, partners, and the public.

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

2004 Continuously shipping for 22 years
4 Ways to use it: online, desktop, and team plans
Toronto Built and supported in Canada
Stronger Protection for code that ships publicly

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 customers make shipped JavaScript harder to read, copy, and repurpose while keeping the original project easy to maintain.

What we build

We maintain a few simple ways to use the same protection engine, so customers can start small and move to a more controlled setup when their needs grow.

Online obfuscator

For quick before-and-after checks, single-file protection, and trying settings before you choose a paid plan. No installation is required.

Desktop application

For larger projects, batch processing, and mixed-file work. The app manages files locally, then sends selected JavaScript to the hosted protection service.

Team options

For companies that need the same protection settings used across multiple releases, accounts, or workstations.

Guidance and support

Practical documentation and human support for choosing settings, checking compatibility, and deciding which plan fits your project.

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 focus on real-world risks: casual inspection, copycat reuse, automated analysis, and public code that needs stronger protection before it ships.

Easy adoption

Protection should be easy to add, easy to repeat, and clear enough that non-specialists can understand what they are buying.

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 use the desktop app for larger folders and mixed-file work. Larger organizations use team options so the same protection approach is applied consistently across releases.

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

Online protection expands

Browser-based protection and account features make JavaScript Obfuscator easier to use without installing a desktop app.

2024

Maximum protection improves

Maximum mode adds stronger protection for customers shipping valuable JavaScript into public environments.

2026

Advanced protection for high-value code

Corporate and Enterprise customers gain additional protection options for the most sensitive parts of their JavaScript.

Toronto, Canada, the city where Richscripts Inc has built and supported JavaScript Obfuscator since 2004
Toronto · Canada

Built and supported from one place since 2004.

The team that ships releases is the same team that answers your support email. No outsourced support tier, no offshored engineering, no escalation queue you can't reach. When you reply to a ticket, an engineer who knows the codebase reads it.

Twenty-two years in the same city, the same product, and the same domain — javascriptobfuscator.com has been continuously hosted from the start.

Frequently asked questions

Who makes JavaScript Obfuscator?

It is built and supported by Richscripts Inc, and it has been developed continuously under the same name since 2004. That longevity is the main thing worth knowing about us commercially: buyers planning multi-year deployments are usually less interested in a feature list than in whether the tool and the company will still be here when they renew.

How long has the product been available?

Since 2004, which makes it one of the longer-running commercial JavaScript protection products. The engine has been rewritten and extended substantially over that period, and the surfaces around it have grown from a desktop application to include a browser tool, a command line runner and a package for Node-based build pipelines, but it has been the same product from the same team throughout.

What exactly do you sell?

A protection engine and the surfaces that drive it: a Windows desktop application, an online tool for previewing, a command line runner, and a package with plugins for common bundlers. Licensing is tiered, and the tier determines which transforms are available rather than how many files you may process. The pricing page lists what each tier includes.

What is your position on what obfuscation can and cannot do?

That it raises the cost of reading and reproducing client-side code, and that it is not a substitute for server-side authority. We say so consistently across the site, including on pages where it would be commercially easier not to. A control that runs on hardware the other party owns is advisory, so anything that genuinely matters belongs behind a decision your server makes.

Do you handle customer source code, and how?

Some workflows send selected JavaScript to the hosted protection service and some keep the source body on the machine. The local modes in the Windows application and the command line package do the latter, with an online entitlement check that carries no source. Virtual machine protection remains hosted by design. The processing documentation describes what is transmitted, what is retained and for how long.

Can I get security or compliance documentation for a vendor review?

Yes, and the site is organised so that most of it can be collected without contacting us first. There are pages covering source handling, the evidence model, and how a protection pipeline interacts with several regulatory frameworks. Assembling that material before a questionnaire arrives is considerably less painful than assembling it afterwards.

How do I get support?

Through the contact page, which routes to the same people who build the product. There is no separate outsourced support tier. For questions that turn out to be about how a transform behaves rather than about an account, the documentation section is usually faster, and the error explanation and compatibility tooling can often identify the cause before a conversation is needed.

Do you offer trials or evaluations?

The online tool lets you see the transforms on real code immediately with no account, within the sample size limits, and that answers most evaluation questions about output quality. For evaluating the workflow rather than the output, contact us and describe what you are trying to protect, because the right recommendation differs quite a lot between a widget, a desktop application and a self-hosted product.

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]