Choose the easiest way to protect your JavaScript

Start online when you want a quick test. Use the desktop app when you need larger projects or local processing. Editor and advanced integration options are available for teams that want protection closer to their daily tools.

The simplest path

Try a small sample, pick the protection strength, then use the desktop app when you need to protect real project files.

1. Open the online obfuscator and protect a small JavaScript sample.
2. Choose Standard, Balanced, or Maximum based on how much protection you need.
3. Download the desktop app when you want to protect folders, larger files, or embedded JavaScript.
4. Upgrade to a paid plan when the free limits are too small or you need stronger protection.
5. Use advanced integrations only when your technical team specifically needs them.

Editor options

If you already work in an editor, these tools make it easier to protect a file or selected code without switching windows.

IDE

VS Code extension

Protect the file you are working on without leaving VS Code. Best for quick checks and small edits.

Marketplace listing IDE

JetBrains plugin

Protect a file or selected code from JetBrains editors used by many web and application teams.

Plugin marketplace Advanced

Advanced package

Optional download for technical teams that want protection connected to an existing release process.

For technical teams

Advanced team integrations

Most customers can start with the online or desktop app. Use these options when your technical team wants JavaScript protection to run as part of an existing release process.

Vite

For teams that build their app with Vite and want protection applied during release preparation.

Webpack / Rspack

For teams using Webpack or Rspack who want protection handled near their existing production build.

Rollup

For Rollup projects that need protected JavaScript output ready for deployment.

esbuild

For esbuild projects where speed matters and protection still needs to be repeatable.

Next.js

For Next.js applications that need protected browser-side JavaScript before launch.

Parcel

For Parcel projects that need a straightforward way to protect final JavaScript files.

Metro / React Native

For mobile teams protecting JavaScript used in React Native applications.

Bun

For Bun-based projects where protection should stay inside the same release routine.

Other technical environments

If your organization does not use JavaScript tooling for releases, these options help a technical team connect protection from the environment they already use.

Advanced

Python

For teams whose release scripts, data products, or internal tools are already Python-based.

PyPI package Advanced

Go

For operations teams and internal tooling that use Go for release automation.

Go client Advanced

.NET

For companies that manage web assets inside a Microsoft or .NET release environment.

NuGet package Advanced

Ruby

For Rails and Ruby teams that want JavaScript protection in their existing release work.

RubyGems package Advanced

PHP

For Laravel, Symfony, WordPress, and other PHP-backed sites that ship public JavaScript.

Composer package Advanced

Rust

For Rust-heavy teams that want protection available from their existing tooling.

Rust crate Advanced

Java

For enterprise Java teams that need a protection option their build owners can review.

Maven package Spec

Custom environments

For teams with a custom release system that need technical reference material before connecting protection.

Technical reference Docs

All client options

A single overview for technical reviewers choosing the best fit for their environment.

Client overview Hook

Pre-release checks

For teams that want a quick guardrail before protected JavaScript moves toward release.

Optional technical setup

Team automation options

For organizations that want every public release protected the same way. These are usually handled by a technical owner after the plan and protection settings are chosen.

GitHub Actions

Use when your team already manages releases in GitHub.

GitLab CI

Use when your team already manages releases in GitLab.

CircleCI

Use when your team already manages releases in CircleCI.

Jenkinsfile

Use when your organization relies on Jenkins for release work.

Azure Pipelines

Use when your organization manages releases in Azure DevOps.

Bitbucket Pipelines

Use when your team already manages releases in Bitbucket.

Drone CI

Use when your team already uses Drone for automated releases.

Buildkite

Use when your team already uses Buildkite for release coordination.

Woodpecker CI

Use when your team already uses Woodpecker for release automation.

Tekton Pipelines

Use when your organization manages releases in Kubernetes-native environments.

TeamCity

Use when your organization relies on TeamCity for releases.

GoCD

Use when your organization relies on GoCD for release work.

Error-reporting support

Protected JavaScript can make production errors harder to read. These options help technical teams translate protected error reports during troubleshooting while keeping sensitive mapping data under customer control.

Reporter