TLDR
Commander singleton rule explained in one sentence: a normal Constructed Commander deck contains exactly 100 cards, including its commander, and cannot contain two cards with the same English name unless they are basic lands or a card’s rules text expressly permits additional copies. Different artwork, sets, languages, borders, and foil treatments do not turn the same named card into a different card.
In practical terms, you can play multiple basic lands but only one Sol Ring, one Counterspell, and one copy of any other ordinary nonbasic card. You can still build consistency by using differently named cards that perform similar jobs. That is one of the central challenges of Commander deckbuilding.
What the Commander singleton rule actually requires
The official Commander rules establish two connected deck-construction requirements: the deck has exactly 100 cards including its commander, and, other than basic lands, no two cards may share an English name.
With one commander, that normally means choosing the commander plus 99 cards for the library. The commander is not an extra 101st card. It occupies one of the 100 slots even though it begins the game in the command zone rather than in the library.
| Situation | Allowed in normal Commander? | Reason |
|---|---|---|
| Two copies of the same nonbasic card | No | They share the same English card name. |
| Two printings of the same card | No | Set, artwork, frame, and treatment do not change the card’s name. |
| Multiple basic lands | Yes | Basic lands are the standard exception to singleton. |
| Different cards with similar effects | Yes | Singleton compares names, not strategic roles. |
| Multiple copies expressly permitted by card text | Yes | The card’s own text can override the normal restriction. |
| A companion as card 101 | Potentially | A legal companion is outside the 100-card deck but must satisfy Commander restrictions. |
The practical test is the English card name
When checking for duplicates, compare the cards’ English names. If those names match, the cards count as copies of the same card for Commander deck construction. This remains true when the cards look completely different.
For example, an original printing and an alternate-art reprint of the same named card are not two singleton-legal choices. A foil version and a nonfoil version are still duplicates. The same applies when one copy has an older frame, a promotional treatment, or text printed in another language. The restriction follows the English name rather than the physical edition.
This distinction matters when importing a decklist or sorting a collection. A visual scan can miss duplicates when two editions use very different artwork. Checking names in the completed list is more reliable than checking art or set symbols.
Why basic lands can repeat
Basic lands are the everyday exception. A deck would struggle to function if every land needed a different name, so the singleton rule expressly excludes basic lands from its same-name restriction. You can therefore include multiple copies of an appropriate basic land while filling out your mana base.
That exception does not mean every land can repeat. A nonbasic land remains subject to singleton even when it produces the same kind of mana as a basic land. One Command Tower is legal; two copies are not. Likewise, two differently named nonbasic lands are permitted even if their strategic purpose is nearly identical.
Singleton is only one part of mana-base construction. You still need enough lands, the right color sources, and fixing that matches your curve. The Commander mana-base guide explains how to evaluate those questions after the duplicate check is complete.
Card text can create a narrow exception
Magic cards can sometimes override a normal deckbuilding restriction. The Commander rules recognize this and identify Relentless Rats as an example of a card whose text permits multiple copies. If a card expressly says that a deck may contain more copies than usual, that instruction can override singleton.
Treat this as a card-specific exception, not as a category you can infer from theme or creature type. A Rat, Sliver, Goblin, or other kindred deck does not automatically gain permission to repeat its creatures. The permission needs to come from the applicable card text.
Also read the exact permission before deciding how many copies to add. Some effects may permit any number, while another design could specify a particular limit. The safe process is to check current Oracle text and then apply exactly what it says rather than relying on memory or an older printing.
Different names can perform the same job
Singleton limits duplicate names, not functional redundancy. You may use several differently named cards that ramp, draw cards, remove permanents, protect your board, or advance the same win condition. This is how Commander decks become consistent without repeated copies of ordinary nonbasic cards.
Suppose a deck needs reliable two-mana ramp. You cannot add four copies of one mana rock, but you can choose several differently named rocks that fit the commander’s colors and game plan. The same principle applies to removal: multiple one-for-one removal spells are legal when each has a distinct name.
Do not select substitutes only because their text appears similar. Compare mana value, timing restrictions, card type, color requirements, and what each effect can target. A slower substitute might be acceptable in a relaxed pod but fail to interact in time at a faster table. A more conditional card may be excellent in one archetype and unreliable in another.
Role compression also matters. A creature that draws cards while supporting a kindred plan may be more useful than a generic draw spell, even when both occupy the same strategic category. The goal is not to find 99 isolated good cards; it is to build packages that support one another. The Commander deckbuilding process offers a broader framework for balancing those packages.
Singleton and color identity are separate checks
A card passing the singleton test does not automatically make it legal in your deck. Commander also requires cards to conform to the commander’s color identity. This is a separate deck-construction restriction. A list can contain no duplicate names and still be illegal because one card falls outside the commander’s color identity.
Format legality is another separate question. A card being a one-of does not override the Commander banned list or any other applicable restriction. Run three checks when reviewing a list:
- Confirm that the deck has exactly 100 cards, including its commander.
- Check that ordinary nonbasic cards do not share an English name.
- Check color identity and current Commander legality separately.
This order makes troubleshooting easier. If a deck builder reports an error, you can identify whether the problem is deck size, duplication, color identity, or legality rather than treating all invalid cards as singleton problems.
Does a companion count toward the 100 cards?
A companion, when used, sits outside the 100-card Commander deck. It must still satisfy the Commander color-identity and singleton requirements in addition to its own companion condition.
The practical consequence is that a companion is not a free duplicate. If the same named card is already in the 100-card deck, you cannot use a second copy as the companion. The companion also cannot introduce an off-color card that the main deck could not legally include.
Commander Draft can use different construction rules
Do not assume every product or event using the Commander label follows normal Constructed deckbuilding. The Commander Legends Draft rules expressly suspended the usual singleton restriction and allowed players to use multiple copies of cards they drafted.
That was a rule for a particular Draft environment, not blanket permission to put duplicates into a regular Commander deck. When joining another Commander Draft or limited event, use the construction rules published for that event rather than automatically applying either normal singleton or the Commander Legends exception.
Do Commander Brackets change singleton?
No. Commander Brackets are intended to help players describe decks and align expectations before a game; they are not presented as a replacement singleton construction system. Wizards currently describes the system as optional, and its February 9, 2026 update said the beta remained guidance for pregame conversations.
Brackets can affect what power level or play pattern a group expects, but that is a different issue from whether a deck follows normal construction rules. A deck does not gain permission to run duplicate nonbasic cards merely because it is assigned to a particular bracket.
Can a playgroup ignore singleton?
A casual group can agree to a house rule that permits duplicates. Commander is often customized by mutual agreement, and nothing prevents friends from enjoying a variant they all understand. However, a deck using that exception is not following the normal singleton construction rule.
Discuss the change before shuffling, especially when playing with new people. Repeated copies can substantially increase consistency, so the relevant conversation is not only whether duplicates are allowed but also what they do to the deck’s speed and reliability. The Commander house-rules guide provides a framework for making those agreements clear without turning the pregame discussion into a rules negotiation.
If the exception applies to only one card or theme, define it precisely. “Two copies of this named card” is easier to understand than “duplicates are okay when they fit the deck.” Clear limits help everyone evaluate the deck on the same terms.
A quick duplicate-check workflow
Check singleton after assembling the full list but before buying cards or finalizing a physical test deck. If you are printing physical playtest cards, perform the same legality review before submitting the list so an accidental duplicate does not become part of the finished test build.
- Count the commander as part of the 100-card deck.
- Sort the list alphabetically by English card name.
- Ignore repeated basic lands, but inspect every repeated nonbasic name.
- For any apparent exception, verify the card’s current text rather than assuming it permits extra copies.
- Check the commander’s color identity and current format legality separately.
- If the list uses a companion, check it against both color identity and singleton.
- Replace accidental duplicates with differently named cards that perform the required role.
When replacing a duplicate, start with the job the card was supposed to do. If the removed copy was ramp, replace it with ramp rather than an unrelated favorite. Then compare cost, speed, restrictions, and synergy. This keeps the deck’s role balance intact while bringing the list into compliance.
The deckbuilding takeaway
Normal Constructed Commander allows one copy of each ordinary nonbasic English card name, with basic lands and explicit card-text permissions providing the important exceptions. Your commander is included in the 100 cards, while a legal companion sits outside the deck but still has to respect singleton and color identity.
The best response to singleton is not to accept an inconsistent deck. Build redundancy through differently named cards, select those cards for the speed and conditions of your pod, and check the completed list by name. If you want to break the rule for a themed casual build, make it a clear house-rule conversation rather than a surprise after the game begins.