Dashboard
The current workspace puts file upload, protection settings and output together. API access is managed separately.
Navigation
Obfuscate
- What it does
- Select or drop a Roblox Luau file, choose options, run Obfuscate, and manage Local build history below the upload card.
Access token
- What it does
- View the workspace credential, remaining web runs and next reset. This is separate from the API key.
API access
- What it does
- Create or manage the API credential used by external build tools, and view its usage.
Documentation
- What it does
- Read request examples, authentication, options, response fields and errors.
Source and output
- Import accepts .lua, .luau and .txt files; the source must be Roblox Luau.
- Keep a version-controlled original. Clear and overwrite actions are not a backup mechanism.
- Copy and Download operate on the current Output pane. Save the protected file before leaving the page.
Local build history
Local build history below the Obfuscate upload card lets you open, copy, download and delete saved output. Successful dashboard builds are automatically stored in localStorage on this browser and site. History persists across sign-ins on this browser; it is not synced across devices. Only the protected output, file name and save time are stored, not the readable source.
Files larger than 5 MiB (5,242,880 UTF-8 bytes) are not saved. If browser storage is full, the oldest history records are evicted until the new result fits. If the new result cannot fit alone, existing records are preserved. Other settings and session data are not removed. Use Download for a lasting copy; clearing site data also clears history.
Usage
Default web access allows three successful builds per 24-hour window, starting with your first build, with a 60-second success cooldown and a 30-second code-error cooldown. Configured managed access can have different limits. Read the values shown for your account.
Protection settings
Options contains Intense VM Structure and Fast runtime. The protection options guide explains what they enable and the performance tradeoffs.
