Frequently asked questions
Everything you need to know about Veilcode — from how it works to what it can't do.
What exactly does Veilcode do?
Veilcode takes your Lua source code and makes it harder to read: comments are removed, local variable and parameter names are replaced with random identifiers, text strings are encrypted, and the code is compacted onto fewer lines. The script's behavior stays the same.
Does my code ever leave my browser?
No. All processing happens directly in your browser via JavaScript. Nothing is sent to or stored on a server.
Is obfuscated code completely unreadable?
No, and Veilcode doesn't claim that either. Obfuscation makes reading and understanding the code significantly harder, but given enough time, obfuscated code can still be analyzed. It's a deterrent, not an absolute protection.
Will the code still work in Roblox afterward?
Yes. Renaming and encryption only change names and text values, not the logic. Still, test the output before using it in production, especially for complex scripts with many global references.
When is FiveM support coming?
FiveM support is in progress. Since FiveM uses its own Lua extensions and conventions, obfuscation for it needs its own adjustments so nothing breaks.
Can I reverse the obfuscation afterward?
No, Veilcode doesn't store a mapping between original and obfuscated names. Always keep an unobfuscated copy of your original script.
Is there a size limit?
There's no hard limit, but very large scripts (tens of thousands of lines) may take noticeably longer to process, since everything runs client-side.