Luaunite documentation
Getting started with Luaunite
Create a build, select a protection profile, and test the generated output in the environment where it will run.
Last reviewed: 10 November 2026
Create your first build
- 1Sign in and open the Obfuscator.
- 2Paste your source or add a file, then choose Basic, Starter, or Pro. Controls only enable options available to your plan.
- 3Review the displayed credit cost and select Obfuscate.
- 4Download the result and run it with the same runtime, globals, and dependencies used in production.
Supported source files
Luaunite accepts pasted Luau source and .lua, .luau, or .txt files. The current limits are 100 KB for Basic, 250 KB for Starter, and 1 MB for Pro. Submit plain source rather than a previously protected build.
The hosted compiler accepts the Luau dialect. Runtime-provided APIs, globals, and modules are supplied by your target environment, not Luaunite.
Understand build output
Luaunite returns protected Luau output. Its structure and enabled defences vary by profile and build, so generated output is not a stable public interface.
local function welcome(name)
return "Hello, " .. name
end
print(welcome("Ada"))-- Luaunite protected output
-- Structure intentionally varies by build.Treat the downloaded file as a build artefact. Keep its filename and version alongside the original source so you can reproduce or roll back a release.
Protection profiles
Basic, Starter, and Pro are starting presets. You can toggle individual protection passes on or off in the Obfuscator settings, and the server checks every request against your active subscription before building.
| Profile | Service limit | Availability |
|---|---|---|
| Basic | 100 KB input, 10-second compile budget | Free and paid plans |
| Starter | 250 KB input, 15-second compile budget | Starter, Pro, Studio |
| Pro | 1 MB input, 30-second compile budget | Pro, Studio |
Compare eligibility and credit packs on Plans.
Protection passes
Every build already compiles into Luaunite's custom VM with a randomised codebook and encrypted payload. The toggles in Customize settings layer extra defences on top of that VM. By default, everything unlocked by your plan stays on.
Control Flow
These passes mess with the shape of your functions so someone reading a dump can't just trace if blocks and calls top to bottom.
- Env-slot permutation (Basic+) — scrambles where upvalues and environment slots sit so slot numbers mean nothing across builds.
- NOP record injection, Macro fusion & Superinstructions (Starter+) — drops fake no-op instructions between real ones and merges common call/branch pairs into custom single opcodes.
- Control-flow flattening, Region shattering & Function topology (Pro) — breaks functions into shuffled chunks across separate pages and replaces normal jumps with a state dispatcher.
- Hot/cold page policy (Pro) — keeps tight loops fast on lighter pages while throwing heavy transforms at everything outside the hot path.
-- Original:
if isAdmin then grantAccess() else kick() end
-- After flattening + shattering:
-- Branches turn into state hops across separate pages with fake NOPs mixed in.Data & Literals
Strings, numbers, and local variables are usually the first thing someone searches for in a script dump. These passes keep them from sitting out in the open.
- Constant pool shuffling & JIT string decryption (Basic+) — shuffles every constant table and encrypts strings inline so they only exist in memory right when that line runs.
- Literal reconstruction, Op decomposition & MBA branches (Starter+) — rewrites plain numbers and comparisons into bitwise/arithmetic identities that evaluate to the exact same answer.
- Variable multiplexing (Starter+) — packs unrelated locals into shared register slots instead of giving every variable its own obvious slot.
- Runtime plaintext clearing, Value fragmentation & Coherent decoys (Pro) — wipes temp values after use, splits sensitive strings (URLs, keys, service names) across steps, and adds dead branches that look real.
-- Original:
local key = 42
-- With literal reconstruction & JIT strings:
-- Numbers become bitwise identities; strings decrypt right before use and clear right after.VM & Crypto
Instead of one static decoder, these passes tie decryption keys directly to the script's own structure and execution order.
- Constant-pool integrity binding (Basic+) — XOR-binds pool lookups to a checksum of that page's constant pool so editing constants breaks decoding.
- Cell-map & Region-transition binding (Starter+) — ties register mappings and jump offsets to page integrity.
- Rolling page crypto & Per-page opcode maps (Pro) — chains page keys along real control-flow edges and gives every page its own shuffled opcode numbering.
- Multiple VM domains, Diversified dispatcher & Dynamic state (Pro) — splits closures across two incompatible VMs, randomises the dispatcher layout, and folds rolling runtime state into instructions.
Anti-Tamper
Runtime checks that catch hooked environments or modified wrappers while the script is running.
- Roblox env probes & Instrumentation resilience (Pro) — mixes live Roblox environment checks into key derivation and spreads invariant checks across execution.
- Anti-hook metamethod detection (Pro, Opt-in) — off by default. Turn this on if you want the script to error when core functions or Roblox instance metatables (
__namecall/__index) have been hooked. Test in your target executor first, since custom sandboxes can trip it.
Compatibility and limitations
Luaunite is intended for compatible Lua and Luau-style runtimes, but behaviour is not guaranteed for every script or runtime. Test the protected build, not only the original source.
Dynamic source and loadstring
Code that creates Lua source at runtime and passes it to loadstring can require changes. Keep those paths simple, test them separately, and use the optional Basic loadstring shell only where it is needed for compatibility.
Credits and billing
Basic accounts receive 3 credits each day, up to a balance of 16. Build cost depends on submitted source size and is shown before you start a build.
Paid plans use plan credits and unlock profiles by tier. Credits are charged for successful builds only; a service-side failure after a charge is reversed automatically.
View plans and credit packsAPI
Create a personal API key in the Obfuscator settings. Use it as a Bearer token with POST /api/v1/obfuscate; it has the same plan, profile, input-size, and credit rules as the web editor.
curl https://833s.net/api/v1/obfuscate \
-H "Authorization: Bearer lui_live_…" \
-H "Content-Type: application/json" \
-d '{"source":"print(\"hello\")","dialect":"luau","profile":"basic"}'Retrieve public profile limits from GET /api/v1/profiles. Keys are shown once when created, stored only as hashes, and may be revoked from settings.
Source retention and privacy
Keep your original source in your own backup. Basic source is kept for 3 days; source submitted under a paid plan may be retained for up to 90 days. Build output is available in build history for a limited time, so download the version you need.
Read the Privacy Policy for full retention details and choices.
Troubleshooting
Syntax error
Correct the reported location in the original source, then create a new build. Do not edit generated output to repair source syntax.
Protected output does not run
First protect and test a small version in the target runtime. Add the remaining code back in stages to isolate an unsupported construct, missing global, or dynamic-loading path.
Credits did not update
Allow a short time for the build status to settle. If the balance is still wrong, contact support with the approximate build time and profile used.