How we check Roblox codes

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. A third-party public list is useful for discovery, but it does not prove that a code redeems. Those rows say Source-listed and Check in game. An official developer listing receives an Official source label, while In-game verified is reserved for an explicitly recorded successful redemption test.

Evidence and lifecycle are shown separately so a fresh timestamp cannot be mistaken for a redemption:

• Source-listed · Check in game — present on the named public source with a specific reward text, but not confirmed by us inside the game.
• Official source — listed by Roblox or the developer. This is strong provenance, but developers can still disable a code without warning.
• In-game verified — an explicit successful redemption check is recorded. The check time is shown; it is not a permanent guarantee.
• Checking— waiting for stronger evidence, or discovered without a usable reward description. Unknown-reward rows do not stay in the primary "codes to try" list.
• Expired — no longer treated as a current code after a failed check, removed source, developer notice, or reviewed player signal. We retain it as history.

A game only stays in the public collection when it has enough source-listed codes with concrete rewards, a hand-written session plan, and an editorial review date. We would rather remove a thin page than keep a table of empty "reward not confirmed" rows that look complete but do not help a player decide what to redeem.

Each published code page also ranks which codes to try first for that game's progression — for example saving XP boosts for a grind window, or treating cosmetics as optional flair — so the page is a plan, not only a mirror of another site's list.

Codes expire constantly because developers tie them to launches, updates, holidays, and follower or visit milestones. Each row can show a source-checked time: when we last observed its public source. That timestamp does not say the code was redeemed. A completed in-game check is labeled separately. Tracked sources are revisited on a recurring schedule, and contradictory evidence sends a row to checking or expired review.

If a code cannot be traced to a public signal or a player report, we do not call it source-listed, official, or in-game verified. 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.

Player reports feed into the re-check queue. A vote is a useful signal, not automatic proof. If a listed code starts failing for players, that signal is reviewed and the row can move to checking or 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.