> For the complete documentation index, see [llms.txt](https://merithic.gitbook.io/merithic-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://merithic.gitbook.io/merithic-docs/selling/obfuscator.md).

# Obfuscator+

Protects your Lua source before buyers receive it. Powered by [Umbra](https://nyxyl.dev).

{% hint style="info" %}
Obfuscator+ is included with [Updatr+](/merithic-docs/getting-started/updatr-plus.md). It isn't an integration and doesn't need installing, the **Obfuscate** tab appears in your dashboard once the studio owner has Updatr+.
{% endhint %}

## What it does

Your code is transformed so it still runs identically but is impractical to read or lift. Every build runs at full strength; there are no options to weaken it.

## Obfuscating on demand

Open **Obfuscate**, paste your Luau (or drop a `.lua` file), and hit **Obfuscate**. Copy or download the result.

Scripts are capped at 400 KB.

## Automatic obfuscation on download

Under **Auto-obfuscate on download**, expand a product and tick the scripts you want protected. From then on those scripts are obfuscated every time a buyer downloads that product, with no extra step from you.

Results are cached per script, so re-downloading an unchanged product costs nothing and is instant.

{% hint style="warning" %}
The script holding your license placeholder can't be selected, it's locked in the list. Keys are injected into that script *after* obfuscation, so a virtualized copy would have nothing left to inject into.
{% endhint %}

## Collaborators

Collaborators need the `use_obfuscator` permission. It only appears in the permission list when the studio owner has Updatr+, since the feature is keyed to their account.

## What to know

{% hint style="warning" %}
Obfuscation is processed by [Umbra](https://nyxyl.dev), which means your code is sent to their servers and handled under their terms. Only submit code you have the right to process.
{% endhint %}

Obfuscation raises the cost of stealing your work; it doesn't make it impossible. Pair it with proper runtime licensing, [`/unlock`](/merithic-docs/api-reference/endpoints/unlock.md) rather than just `/check`, so a lifted copy has nothing to run against.

Test the obfuscated build before shipping. Heavily dynamic code (lots of `getfenv`, string-built identifiers) is the usual source of surprises.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://merithic.gitbook.io/merithic-docs/selling/obfuscator.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.