Roblox Executors, tracked and compared in one dashboard

A Roblox executor is a third-party program that injects a Lua/Luau interpreter into the Roblox client and runs custom scripts inside it — anything from a simple ESP overlay to a full auto-farm game hub. Executors are unofficial: Roblox does not build, endorse or support them, and using one sits outside Roblox's Terms of Service. Executors are also called "Roblox exploits," and both terms are used interchangeably across the scripting community.

How executors actually work

Roblox ships with an anti-cheat layer (Byfron/Hyperion) that tries to detect processes attaching to or injecting code into the game client. An executor's core job is to attach to a running Roblox process, bypass or evade that detection long enough to load a script interpreter, then expose a set of functions (the "API") that scripts can call. The percentage of standard functions that actually work is what the UNC and sUNC benchmarks below measure.

Why UNC and sUNC scores matter

Two community-maintained test suites — UNC (Unified Naming Convention) and sUNC (synapse UNC, a stricter superset) — run a battery of function calls against an executor and report the percentage that behave correctly. A script hub built for a 95%+ UNC executor will likely throw errors on a 60% UNC one. These scores are self-reported, executor-specific, and can move up or down after a Roblox patch, so they're a starting signal, not a guarantee.

Key systems, explained

Some executors gate access behind a "key" — typically a short link-shortener or ad-verification flow you complete to get a temporary or permanent access key. Others are "keyless," skipping that step entirely. Keyless is more convenient, but it is not automatically safer or more actively maintained; judge an executor by its update cadence and community status, not by whether it has a key screen.