TFT Augments
Browse all augments in TFT.
About TFT augments
Augments are offered mid-game and change how a board works rather than how strong it is — a rule change rather than a statistics boost. They are the mechanic that most distinguishes TFT from the autobattlers it grew out of.
The list is large and it turns over every set, with each augment tiered by how much it swings a game. Reading them as a set shows the format's design intent more plainly than any single unit does.
Several augments only make sense alongside a specific trait or cost tier, so this index is best read next to the traits and the roster rather than on its own.
Augments are the mechanic most likely to change between sets, because they are the easiest place to try an idea without touching the roster. Reading two sets' augment lists side by side is the quickest way to see what the designers decided had worked.
Where this data comes from
TFT augments are read from Riot's own public data feeds rather than typed out or scraped from a wiki. That means an entry reflects the patch currently live: when Riot ships a change, the next collection run carries it, and nothing here is a hand-maintained copy that can quietly fall a season behind.
It also means the gaps are honest ones. Where Riot publishes no value for a field, this database shows none rather than guessing, and where a field exists only in one game's feed it is not invented for the others. The endpoints, their URL shapes and the versioning that governs them are documented in full in the Data Dragon and Community Dragon reference, including the two set identifiers a numeric loop silently skips.
The rest of the TFT database
The same data set, cut by kind. Augments is one section; the others below hold the rest of what TFT ships, read from the same source on the same patch.
Every entry in this database describes a character, object or place that belongs to Runeterra, and the archive carries the stories they come from. The Archive of Runeterra indexes those works, the timeline puts them in in-world order, and the Data Dragon reference documents the public endpoints this data is read from.