What UNC actually is
UNC stands for Unified Naming Convention: a shared community standard for what functions a Roblox executor should provide and what each one should be called. The point of it is portability. Before UNC settled, every executor named its functions differently and script authors shipped compatibility shims for a dozen tools, which is why old scripts still carry blocks of aliases at the top.
A UNC test is itself a script. It walks that standard list, calls every function and reports the percentage the executor implements. Higher means more scripts run without modification. The important word is implements, because the classic UNC test mostly asks whether a function exists and returns something, not whether it does the right thing with what you gave it.
That gap is exactly where the number gets gamed. An executor can stub a function so it exists, returns a plausible value and passes the check, while any script that genuinely relies on it breaks the moment it is called. A 100% UNC score on a tool nobody has heard of is a claim, not a result.
What sUNC is, and why it matters more
sUNC is the stricter, more honest version of the same test. Plenty of executors can claim a high UNC by providing functions that technically exist but do not behave correctly. sUNC checks that functions actually work the way scripts expect, so it is much harder to fake. When two executors disagree, trust the sUNC number.
In practice sUNC verifies behaviour rather than presence. Does a hook actually redirect calls, does the closure it hands back behave like the original, does a garbage collector read return real contents, does a metatable operation survive the checks a game might run on it. Stubs fail all of that outright. This is why sUNC scores are almost always lower than UNC scores on the same tool, and why a wide gap between the two numbers is itself a signal worth reading.
On every product page here the live sUNC figure is pulled from the tracker rather than typed in by us, so you are seeing the current number rather than a marketing claim from launch day. The same feed drives the live status page, and our method is written up on how we test.
UNC vs sUNC: what each test proves
The cleanest way to hold the difference in your head is to ask what each test can and cannot be faked into saying.
| Test | What it checks | How easy it is to fake | Use it for |
|---|---|---|---|
| UNC | Whether the standard functions exist and are named correctly | Easy, a stub passes | A rough floor, nothing more |
| sUNC | Whether those functions actually behave the way scripts expect | Hard, stubs fail outright | The number you compare executors on |
| The gap between them | How much padding is in the advertised function list | Not fakeable, it is derived from the other two | Spotting inflated marketing claims |
What counts as a good sUNC score?
Treat the percentage as a band, not a precise ranking. The difference between 96% and 98% is noise. The difference between 95% and 65% is the difference between everything working and half your hub erroring out.
Among the products we track, Potassium publishes a 100% sUNC environment and Wave sits at or near full marks, which is a large part of why both lead our best Roblox executors roundup. Volt and Real also carry full sUNC support, and Cosmic offers sUNC support at the budget end, $14.97 lifetime against Potassium's $22.97. Always read the live figure on the product page rather than any paragraph, including this one, because scores move whenever an executor ships an update.
| sUNC band | What runs | What breaks | Verdict |
|---|---|---|---|
| 90 to 100% | Effectively every public script and major hub | Almost nothing, the occasional exotic function | Buy with confidence |
| 70 to 90% | Most hubs and everyday scripts | Heavier hubs and some game-specific features | Fine if the price is right |
| 50 to 70% | Simple scripts and basic automation | Anything leaning on advanced functions | Expect regular frustration |
| Below 50% | Very little reliably | Most modern hubs, immediately | Not worth paying for |
How to check an executor's sUNC score before you buy
This takes about two minutes and saves the most common wasted purchase in the scene: a key for a tool that cannot run the one hub you bought it for.
- 1Open the product page from the Roblox executors hub and read the sUNC figure in the live status block, not the seller's marketing copy.
- 2Check the update state on the same page or on the status page. A 100% sUNC score on an executor showing Not Updated is worth nothing today.
- 3Compare the UNC and sUNC figures side by side. A large gap means the tool is padding its function list, and the sUNC number is the one that will predict your experience.
- 4Cross-check the price for that exact key across sellers on the comparison page. The score is identical whoever you buy from, so there is no reason to pay more.
- 5Buy the shortest plan available first, a $2.47 day key on Wave or a $2.99 week on Real, and load the hub you actually care about before committing to a lifetime key.
- 6If a script still errors after all that, work through the executor not working guide before blaming the score.
Does a high sUNC score mean an executor is safe?
No, and this is the most common misreading of the number. sUNC measures compatibility and nothing else. It says nothing about detection, nothing about what the developer bundles in the installer, and nothing about how fast the team ships after a Roblox patch. A 100% sUNC executor that has been detected for a week is a worse buy than an 85% executor that updated this morning.
Ban risk comes from injection itself, from update lag, and from what you visibly do in game, all of which we cover in the executor ban guide. Malware risk is a separate axis again, covered in are Roblox executors viruses. Treat sUNC as one of three specs you check before paying, alongside live update status and current price.
Does sUNC matter if I only run script hubs?
Yes, more than for anyone else. Script hubs are the heaviest consumers of the environment: they hook functions, decompile, read the garbage collector and fire remotes in ways a simple autofarm never does. A hub that runs perfectly on a 100% sUNC executor can fail on a 70% one with an error naming a function you have never heard of, and the hub developer will correctly tell you the problem is your executor.
If you mostly run one hub, the practical test beats any spec sheet: buy the cheapest short key on a high-sUNC executor and load that hub. That is a $2.47 to $2.99 experiment. Our free versus paid comparison explains why free tools tend to score worse on sUNC and update slower after patches, and executor key systems explained covers the other tax free tools charge you in time.
Three things the scores do not tell you
- Update speed. The score is a snapshot of an environment, not a promise about how fast the team ships after the next Roblox patch, which is the spec that decides whether you can play at all this week.
- Detection state. Compatibility and detection are separate axes and a tool can be excellent on one and terrible on the other. Check both on the status page.
- Whether the product is an executor at all. Externals like Matcha and Severe do not run Lua scripts and have no meaningful sUNC score, which is not a flaw, just a different product type, as executor vs external vs internal sets out.
- Performance and stability. sUNC says nothing about injection speed, memory use, or how long a client survives a heavy hub in a full server.