Does this send my code anywhere?

No. Obfuscation runs entirely in your browser using javascript-obfuscator.

Is obfuscation the same as security?

No. Obfuscation makes code harder to read, not impossible to reverse-engineer. Never rely on it to protect secrets like API keys; those should never ship in client-side code at all.

Are all variable names renamed, including globals?

No. Only local, function-scoped identifiers are renamed to short, hex-like names. Global-scope variables and function names are left unrenamed, since this tool disables `renameGlobals`, which avoids breaking references your code or other scripts might make to a global.

Does obfuscating also remove comments and formatting?

Yes. Comments and the original formatting are stripped as part of the transform, and the output is reprinted compactly, so obfuscation here has a minifying side effect even though that isn't its primary purpose.

JavaScript Obfuscator - Obfuscate JS Online

Overview

Introduction

Sometimes you want client-side JavaScript to be harder to casually read or copy, even knowing that determined reverse-engineering is always possible.

This tool obfuscates JavaScript using javascript-obfuscator, entirely in your browser.

What Is JavaScript Obfuscator?

An obfuscator that renames variables, extracts string literals into an encoded array, and otherwise transforms code to be harder to read while preserving its behavior.

It's the same library used by many browser-based obfuscation tools and CLI pipelines.

How JavaScript Obfuscator Works

The code is parsed into an AST, transformed (identifier renaming, string array extraction), and re-printed as compact, harder-to-read JavaScript.

A syntax error in the input is reported instead of producing output.

When To Use JavaScript Obfuscator

Use it for casual deterrence of copying client-side logic, such as a small game script or a demo you don't want trivially reused verbatim.

It's also useful for obscuring implementation details of a client-side script from casual viewing (like someone opening browser dev tools), without expecting it to stop a determined analysis.

Often used alongside JavaScript Minifier and JavaScript Formatter.

Features

Advantages

Runs entirely client-side.
Uses a widely adopted obfuscation library rather than a simple find/replace trick.
Moves string literals into an array referenced by index rather than leaving them as plain readable text, which raises the bar above simple minification alone.

Limitations

Obfuscation is not encryption or security. A motivated person can still deobfuscate or step through the code in a debugger.
Never put real secrets (API keys, credentials) in client-side code; obfuscating them doesn't make them safe.

Examples

Simple function

Input

function greet(name) {
  return "Hello, " + name;
}

Output

var _0x1a2b=["Hello, "];function greet(_0x3c4d){return _0x1a2b[0]+_0x3c4d;}

The string literal is moved into an array and the parameter is renamed to a hex-like identifier.

Best Practices & Notes

Best Practices

Test obfuscated output thoroughly; aggressive transforms can occasionally interact badly with code that inspects function names or source text.
Avoid obfuscating code that relies on `Function.prototype.name`, reflection, or matching against the original source text; renamed identifiers can change that behavior even though runtime logic is preserved.

Developer Notes

Uses `javascript-obfuscator`'s `obfuscate()` with `stringArray` enabled and `controlFlowFlattening` disabled to keep output size and transform time reasonable, dynamically imported.

JavaScript Obfuscator Use Cases

Deterring casual copying of a client-side script or demo
Making a small utility script harder to skim at a glance

Common Mistakes

Using obfuscation as a substitute for keeping real secrets out of client-side code entirely.
Treating obfuscated output as unreadable; with browser dev tools and enough time, obfuscated JavaScript can still be stepped through and understood, it's a deterrent, not a lock.

Tips

Keep an unobfuscated source copy; obfuscated output is not meant to be maintained directly.
If output size matters, note this tool disables control flow flattening, so it favors reasonable output size over maximum obfuscation strength.

JavaScript Obfuscator