The current public Web Rush sources confirm that the game contains many suits and that cash buys new suits, but they do not publish a complete authoritative name-and-price catalog. This Suit Dex therefore starts with verified catalog groups and exact record fields. It does not turn video thumbnails, copyrighted character guesses, or exploit menus into official entries.
Currently documented suit groups
Official loop
Cash-purchasable suits
Type: suit catalog group
Source: official Web Rush description
Cost: cash; individual values require live cards
Effect: unknown by group
Availability: current catalog required
Group confirmed • checked 2026-08-13Community reported
Robux suit options
Type: purchase group
Source: current player discussion
Cost: individual Robux values not recorded here
Effect: not established
Availability: inspect current cards
Community reported • live confirmation neededCurrent title signal
New-suit update entry
Type: currently highlighted suit
Source: `[NEW SUIT]` Roblox title tag
Name: not stated by the title
Cost/effect: unknown
Availability: inspect current menu
Identity and fields need in-game confirmationWhy named rows are not guessed
A suit image can resemble a familiar comic design without proving the in-game displayed name, license label, acquisition type, or effect. A script page can enumerate internal or unauthorized selections without proving normal availability. A video title can call one option “best” without showing controlled comparison.
The useful catalog begins with the current suit menu. Record only the displayed English name and the card shown by Web Rush. If the same suit has an older Web Strike label, keep that as an alias on the same record rather than making a duplicate.
Suit Dex record template
How to capture the current list
Join the official game, open the suit menu, and move through every visible category without purchasing. Record the number of cards only if the interface clearly shows the full list rather than a filtered tab. Open each card to read the name and cost. If a card is locked, capture the written requirement without guessing what satisfies it.
Change any category or filter deliberately and note it. A Robux tab, owned tab, or limited section can make a partial list look complete. Rejoin once to see whether the same catalog loads and whether account ownership changes what is visible.
Filter suits for a decision
Filter first by acquisition you accept: available cash, affordable Robux, completed requirement, or owned. Then separate documented gameplay effects from cosmetic choices. Finally compare appearance and personal preference. This order prevents a visually exciting but unreachable card from dominating the decision.
If a suit has a verified ability, use the Abilities Guide to keep the effect and unlock route in one place. If the suit only changes appearance, describe it honestly without downgrading its value to a player who wants that look.
Detect stale or duplicate entries
Use the displayed name, icon, acquisition route, and effect together. A renamed card with the same model and ownership may be one continuing item; two similar models with different cards may be separate. Do not merge or split based on appearance alone.
If an old Web Strike guide lists a suit that no longer appears, mark it historical only after checking every relevant tab and the current version. Do not call it removed when it might be event-limited, account-specific, or renamed.
Verify effects fairly
Use the same movement route, thug encounter, cash balance, and ability state before and after equipping. Record the suit, version, server, and visible description. If no consistent difference appears, keep the effect field empty.
Damage, speed, cooldown, and cash multipliers require repeated numerical evidence. A smoother run can come from practice or a different route. A suit card’s written rule is the starting point, not proof of every possible interaction.
Use the list without a false completion claim
Call a capture “currently documented” when the interface may be filtered or evolving. A complete claim needs every accessible category, account condition, and current limited section. Early development makes that especially difficult, so the Dex is designed to remain useful even when one field is absent.
Continue with How to Get Suits for the purchase path and Best Suits for goal-based comparison. Use Updates when the title or description signals a catalog change.
Video catalog companion
This community walkthrough is directly focused on obtaining Web Rush suits. Use it to recognize the current interface and route, then confirm every name and price in your live build.
Evidence note: suit purchasing with cash is official; Robux availability and any video-shown menu details remain community reported until confirmed live. Checked August 13, 2026.