An All Star Tower Defense unit list is useful only when it helps you decide what to keep, test, evolve, or place. The original game has years of summon, event, capsule, reward, and evolution additions, while community indexes can lag behind a live rotation. This page therefore organizes known examples by player job and verification need. It is not presented as a complete live inventory export.
Unit index by practical role
These examples are discovery anchors, not automatic recommendations. Similar names can have multiple forms, and the same character-inspired family can include units with different rarities, attack types, or abilities. Match the full inventory name before applying any note.
How to identify a unit correctly
Open the unit in your inventory and record its displayed name, star rarity, level, evolution state, and attack type. Then check whether an orb is equipped and whether the unit is in the leader slot. Those modifiers can make your observed stats differ from a community screenshot.
Next, locate the source. A unit may be in the hourly Summon Gate, a special summon, an event shop, a capsule, a mode reward, or an evolution recipe. Do not label a historical source as current simply because the unit still exists in an index. The live banner, shop, recipe, or completion panel is the authority for current availability.
Finally, test its upgrade path in a repeatable stage. Record placement cost, each upgrade price, attack interval, range, damage, area shape, and any ability added at a later upgrade. The Unit Stats guide provides a clean worksheet for comparisons.
Filter the roster by the problem you have
I lose in the opening waves
Filter for affordable ground or hill coverage with a useful first upgrade. Do not start with maximum damage; start with the cash needed to stop the first leak.
I cannot reach final upgrades
Inspect economy units and upgrade order. Calculate when each farm placement pays back, and stop investing when the remaining waves are too short.
A boss survives
Look for focused damage, control, or a timed team buff. Test against the same boss without changing several supports at once.
Late waves overwhelm the route
Filter for scalable area coverage, range, control uptime, and placement-limit efficiency. Infinite teams need a different balance from Story clears.
This approach keeps a huge list manageable. You only need to compare units capable of filling the missing role, not every name ever added to the game.
Rarity and evolution view
Rarity is a progression marker, not a complete ranking. Lower-rarity units can be stepping stones, evolution ingredients, early-wave defenders, or collection pieces. Six-star and seven-star units often require more account preparation, and their value depends on whether you can obtain and upgrade them reliably.
For a six-star target, open 6-Star Units and verify the exact base unit and recipe. For a seven-star target, use 7-Star Units and check whether its current route is evolution, special summon, event, or another source. The community evolution index currently warns that it is under revamp, so missing entries must not be interpreted as impossible evolutions.
Never feed or sell duplicates until you have inspected the live recipe. A duplicate that looks unnecessary can be a required ingredient. Lock the copy you actively use and separate planned evolution materials from experience fodder.
Attack and placement view
Group damage units by what they can actually cover: ground, hill, hybrid, single target, circle area, line or cone-like area, full-area effects, and manually triggered abilities. The exact labels may differ in the interface, but the operational question stays the same: which enemies enter the attack area and for how long?
Range alone is not enough. Map bends, split lanes, spawn spacing, and enemy speed decide whether that range produces useful hits. Test at likely placement points before calling one unit better. A smaller area with better route alignment can outperform a larger circle placed poorly.
Support units need a separate lens because ordinary damage-per-second tables may exclude their contribution. Read Support Units for economy, buff, slow, timestop, rewind, pushback, and healing roles.
Source and availability view
Use four source labels in your own list: live, recipe verified, community reported, and historical or unavailable. Add a check date to each. A summon unit is live only when it appears in the current pool; an evolution is recipe verified only when the current menu shows the ingredients; an event unit is historical when its event has closed and no replacement source is visible.
The official description says the Summon Gate changes hourly, which makes a screenshot of one rotation especially short-lived. Record the visible timer and currency, then decide whether to wait or summon. For capsules, inspect the current vending machine or event interface because older capsule types can become unavailable.
Build your own accurate list
Create one row per exact unit form with these fields: displayed name, rarity, level, role, placement type, attack shape, source, current availability, evolution target, equipped orb, verification status, check date, and a link to your detailed notes. Leave unknown cells blank. Do not estimate a damage value from a video frame or reuse a value recorded at a different level.
After each meaningful update, recheck only the fields most likely to change: source, recipe, costs, attack interval, range, ability text, and mode restrictions. Your list becomes more trustworthy by showing uncertainty clearly, not by pretending every old unit is fully documented.
Next decisions
Use the Units hub to map jobs, then compare candidates with Unit Stats. If the missing slot is economy or control, use Support Units. Once the role is known, the Tier List can judge that unit for Story or Infinite Mode without collapsing every use case into one rank.