Where codes come from
Reward codes are not something we generate — they are released by each game's developers and we track them from public signals. In practice a code reaches us from one of a few places: an official developer post (in the experience description, a pinned announcement, or a verified social account), an in-game event or update screen, a public community channel, observable Roblox activity around a launch, or a direct player report submitted through the site.
We rank these by trust. An official developer source is the strongest signal and can move a code to working on its own. Anything weaker is held in a checking state until enough independent evidence — repeat sightings, successful player redemptions, or a matching official post — supports the status we show.
The status lifecycle
Every code carries exactly one status, and it can only change with evidence:
- Working — traced to a credible source and not contradicted by recent checks or player reports.
- Needs verification— seen somewhere public but not yet confirmed. It stays out of the headline "active" list until it earns the working status.
- Expired — confirmed dead by a failed check, a removed source, or a developer notice. We move codes here instead of deleting them, so the page keeps an honest history rather than quietly shrinking.
Timestamps and re-checking
Codes expire constantly because developers tie them to launches, updates, holidays, and follower or visit milestones. A list is only as trustworthy as its last check, so we stamp each tracked game with when it was last reviewed and surface that date on the page. Tracked games are re-checked on a recurring schedule, and a code that fails a re-check is demoted rather than left as filler.
We never invent codes
If a code cannot be traced to a public signal or a player report, we do not list it as working — full stop. We would rather show a shorter, honest list than pad it with guesses. The most common reason a genuinely valid code "fails" for a player is a typo or a trailing space, since codes are case-sensitive; it is almost never an account problem, and we never ask for a password or route you to a "free Robux" generator.
When you report a broken code
Player reports feed directly into the re-check queue. If a working code starts failing for players, that signal is reviewed and — if confirmed — the code is moved to expired. You can report a code from any code list, or read more about our standards in the editorial policy and how our metrics are computed in the methodology.