A continuously curated, community-verified catalog of promotional codes across the Roblox ecosystem — where every entry is a small lantern lit for players wandering the maze of dead codes.
Repository: roblox-code-vault
License: MIT (see below)
Status: Actively maintained throughout 2026
Data philosophy: Transparent sourcing, human verification, zero guesswork
If you have ever spent twenty minutes pasting a code into a Roblox redemption box only to be greeted by an error, you already understand the problem this project solves. The internet is littered with stale code lists, auto-generated pages that were never verified, and expired promos that keep getting recycled by content farms. Roblox Code Vault exists as the antidote.
This is not a scraper dump. This is not a "copy-paste 500 codes and hope one works" spreadsheet. This is a hand-tended garden of redeemable rewards — each entry logged with its source trail, its verification timestamp, and its current status. When a code dies, it is marked, not deleted, so that history remains readable and the community can see what used to work and when it stopped.
The vault covers 19 game ecosystems, from the blocky battle royales to the quiet tycoon simulators, from the sprawling RPG adventures to the cozy roleplay worlds. Each game gets its own section, its own verification cadence, and its own quirks. Because no two Roblox games treat their redemption systems the same way.
The original inspiration was a dataset of 527 verified codes across 19 games, multi-source checked and released under an open license. That project proved something important: if you treat game codes like data — with provenance, timestamps, and confidence scores — the whole experience improves.
This repository takes that spark and runs with it. Instead of a static dataset, this is a living system. It has:
- A structured JSON schema for every code entry
- A verification log that tracks each code's journey
- A contribution workflow that rewards careful, patient checking over rapid-fire submission
- A philosophy that dead codes are still valuable — they teach us what the game publisher intended
Think of it less like a code list and more like a field guide to limited-time rewards.
Top-level layout (conceptual, not literal file paths to avoid clutter):
/data— the core JSON and YAML files, one per game, containing every code with metadata/logs— chronological verification records, including "this code died on X date"/docs— human-readable guides, game-by-game notes, and redemption walkthroughs/tools— lightweight scripts for validating entries and rendering the codebook/community— templates for contributions and issue reporting
Every code entry carries these fields: the code string itself, the reward description, the game name, the source URL trail, the first-seen date, the last-verified date, the current status (active, expired, unknown), and a confidence rating from 1 to 5.
Codes are not just "active" or "dead." They have a lifespan. Each entry records when it was first observed, when it last worked, and when it was retired. This means you can ask questions like "which codes survived more than a year?" or "did the developer reissue this reward under a new code?"
Every submission must cite at least two independent sources before it earns the "verified" badge. One source can be the game's official social channel, the other a community report. We do not accept single-source entries as verified.
The guides and redemption instructions are available in English, Spanish, Portuguese, and Japanese — because Roblox is a global platform and reward redemption should not be gated behind one language. Community translators are credited in the /docs folder.
The /tools folder includes a lightweight viewer that renders the entire codebook in any modern browser. It works on phones, tablets, and desktops. No frameworks, no build step, no tracking scripts.
Each code carries a confidence score that decays over time if it is not re-verified. A code that was verified in January 2026 but not touched since will slowly lose confidence until someone re-tests it. This keeps the catalog honest.
The repository discussion board and issue tracker are monitored around the clock by volunteer maintainers. If you find a code that no longer works, you can report it and expect a response within a day. This is the 24/7 customer support layer for the dataset itself.
Some games require you to enter codes in a specific menu. Some have cooldowns. Some silently accept codes but never grant the reward. Each game's section includes a quirks note explaining its redemption behavior.
This README is written to be discoverable by anyone searching for things like:
- Roblox code verification tools
- Active Roblox promotional codes 2026
- How to redeem Roblox game rewards
- Roblox code dataset open source
- Multi-source verified game codes
But we do not stuff keywords. Instead, the phrases appear where they belong — in headings, in the feature descriptions, and in the usage guidance. The goal is to be useful first, findable second.
You do not need to install anything to read the vault. The /data folder is plain text. Open it in any editor. Search for the game name. Read the entry.
If you want to consume the data programmatically, the JSON schema is stable and documented in /docs/schema.md. You can load it into your own project, a Discord bot, a mobile app, or a spreadsheet. The license permits it.
If you want to render the viewer, open the HTML file in /tools/viewer with any browser. That is all.
There is no package manager step. There is no environment variable to set. There is no secret key to configure. This is intentionally simple so that it remains accessible to everyone.
Contributions are welcome, but we ask for patience and rigor over speed. To submit a code:
- Check whether the code already exists in the vault. If it does but its status is "expired," you may submit a re-verification instead.
- Gather at least two independent sources. These can be official announcements, community screenshots, or reputable code-tracking sites.
- Open an issue with the
new-codetemplate. Include the code, game name, reward, sources, and the date you tested it. - A maintainer will test the code within 48 hours and either merge it, ask for more evidence, or mark it as unverifiable.
We celebrate careful contributions more than volume. One well-verified code is worth more than fifty guesses.
The entire repository — data, documentation, tools, and viewer — is released under the MIT License. This means you can use it commercially, modify it, redistribute it, and build on it, as long as you preserve the license notice.
A working link to the license is provided in the license section at the bottom of this file.
We chose the MIT License because we believe open data should be frictionless. There is no copyleft requirement here. If you build a product on top of this vault, you do not have to open-source your product. You just have to keep the license notice.
- Quarter 1: Migrate the entire dataset to the new schema with confidence scores
- Quarter 2: Launch the responsive viewer with multilingual interface support
- Quarter 3: Introduce automated link-checking for source URLs
- Quarter 4: Publish a quarterly "State of the Vault" report summarizing code lifespans and trends
This roadmap is a living document. It will shift as the community grows and as Roblox evolves its own promotional systems.
This project is an independent, community-driven catalog. It is not affiliated with, endorsed by, or sponsored by Roblox Corporation or any game developer represented in the dataset. All game names, logos, and trademarks belong to their respective owners. The codes listed here are promotional codes intended for legitimate redemption within their respective games. We do not host, distribute, or promote any unauthorized modifications, exploits, or unintended access methods. Users are responsible for complying with each game's terms of service. The maintainers make no guarantee that any code will work at any given time — the status field is a best-effort snapshot, not a promise.
This repository is licensed under the MIT License.
You can read the full license text here:
MIT License
Copyright (c) 2026 Roblox Code Vault contributors.
Thanks to the original dataset project for proving that verified game codes are worth treating as serious data. Thanks to every contributor who has ever tested a code, reported a dead one, or fixed a typo in a game name. Thanks to the translators who made the guides accessible beyond English. And thanks to the players who keep exploring Roblox worlds — you are the reason this vault exists.