hide.lat

Lua / release workflow

How to obfuscate a Lua script

Check the original, make a Lite build, then run both versions in the game or app you support. A download only tells you the compiler finished.

1. Check the original source

Save a copy of your source before changing it. Run the original script and note what it should do: output, return values, events, files it touches, and how long it takes to start. If it already fails, fix that first. Obfuscation will make an existing bug harder to trace.

Check your Lua runtime before building. Roblox uses Luau. MoonLoader scripts often depend on LuaJIT, FFI, or game hooks. A script can parse in one runtime and fail in another. Script Doctor can flag some mismatches; it cannot run your game-specific code.

2. Make a Lite build

  1. Sign in with a verified email, then open the hide.lat Lua obfuscator.
  2. Paste your source or open a .lua or .luau file. Leave the protection level on Lite for the first test.
  3. Choose whether to randomize the build seed. A fixed seed makes it easier to reproduce the same build while you debug a specific source revision.
  4. Click Obfuscate source. Download the protected .lua file and its build report.

Lite is free with a verified account. Advanced and Maximum require reviewed access. Start with Lite so you have a working baseline before trying a heavier build.

3. Compare behavior in the target runtime

Run the protected file in the same runtime as the original. Compare startup, output, event callbacks, error handling, and cleanup. Test more than a one-line print: use a representative script that includes the loops, closures, metatables, host APIs, and asynchronous behavior your release depends on.

For Roblox, test in the place and on the devices where the script will run. For MoonLoader or SA:MP, use the same game, loader, and modules as your users. Syntax checks cannot test game APIs. The Roblox guide and MoonLoader guide cover those checks.

4. Keep a release record

Store the original revision, protected output, build report, and test result together. The report includes the engine version, seed, and output hash so you can identify the exact build that was released. Test again after each source change; passing once does not validate later builds.

If a protected build fails

Check that the original still works in the same runtime. Then reduce the failure to a small script that still shows the difference. Record the build identifier, target runtime, expected behavior, actual behavior, and any error text. Remove credentials and private data before opening a support ticket.

What obfuscation can and cannot do

Obfuscation makes a script harder to read. It does not protect secrets or payment decisions inside code someone else runs. Keep those on your server. Use license keys to control distribution and obfuscation to slow down copying.

Try a free Lite build with a representative script, or check Lua 5.1 versus Luau differences first.