Treat rarity as a way to control frequency, complexity, Draft signaling, and the texture of a custom environment—not as a score for how powerful or impressive a card is. Commons establish normal gameplay, uncommons direct themes and support build-arounds, rares create less frequent or more specialized moments, and mythics are best reserved for especially singular designs. Assign a provisional rarity, place the card in its intended set or Cube, and change it when playtesting shows that it appears too often, communicates poorly, or overwhelms other strategies.
Good custom mtg card rarity design starts with one question: where will this card be played? Rarity has limited mechanical significance on a standalone Rule 0 card, but it becomes a major system-level decision in a draftable custom set. It determines how frequently an effect appears, how often players must process it, and how reliably it can support an archetype.
That is why a powerful removal spell might be common while a strange, narrow build-around belongs at rare. The first may be necessary for ordinary games to function; the second may need more text, unusual deck construction, or protection from showing up repeatedly. Wizards’ design discussions similarly describe rarity as a combination of complexity, Limited impact, narrowness, splash, flavor, and established expectations—not raw strength alone. The official discussion of how Magic uses rarity provides useful context for custom designers.
For one custom Commander, joke card, token, or story-driven design, rarity is mainly a presentation and flavor choice. You can mark a legendary centerpiece as mythic because that treatment communicates importance, but doing so does not balance its mana cost or make an oppressive ability acceptable. A standalone card still needs the normal review process: define its purpose, compare it with relevant official cards, check the wording and layout, and test it in the intended playgroup. The broader custom MTG card design workflow explains that process.
A custom Draft set has a different problem. Here, rarity regulates repetition. If an effect appears at common, players may encounter several copies across a draft or game. That makes common the wrong place for mechanics that require frequent rules consultations, create persistent memory burdens, or become miserable in multiples. Conversely, moving every useful role to rare leaves the environment inconsistent and can make its advertised themes difficult to draft.
Cube sits between those cases. A singleton Cube does not use ordinary booster rarity, but rarity labels can still communicate the intended importance of a custom card. If the Cube includes duplicates or uses rarity-weighted packs, the labels become distribution controls again. Decide how packs or pools are assembled before treating a rarity choice as meaningful.
The following jobs are useful starting points rather than binding rules. A card can break the pattern when its environment provides a good reason.
| Rarity | Primary design job | Common warning sign |
|---|---|---|
| Common | Establish normal gameplay, core mechanics, creature sizing, interaction, and the set’s visible themes | Too much text, excessive tracking, repeated board stalls, or an effect that becomes oppressive in multiples |
| Uncommon | Signal Draft archetypes, reward synergy, introduce selective build-arounds, and support moderately complex effects | The card is so essential that an archetype fails whenever drafters do not see it |
| Rare | Provide narrow build-arounds, unusual effects, splashy moments, and cards whose repeated Limited impact should be constrained | The rare is only a more efficient version of an effect the set already supports cleanly at lower rarity |
| Mythic rare | Present especially singular characters, stories, effects, or experiences that should occur very infrequently | Mythic is being used merely to label the set’s strongest cards |
Wizards has described commons as central to a set’s theme and ordinary gameplay, with higher rarities carrying more specialized, exciting, or complex designs. Uncommons are particularly important in Draft because they appear often enough to influence decisions while still feeling directional. They can reward a color pair, point toward an archetype, or invite players to build around a condition that would be too repetitive at common.
Imagine one copy in a game, then imagine three. If the third copy makes the board state repetitive, locks out normal interaction, or turns a novelty into a routine, start above common. Frequency also matters for answers: efficient removal, combat tricks, and smoothing effects may need to appear regularly enough for the environment to function.
Count decisions and tracking demands, not just lines of text. A short ability can still be complex if it changes combat rules, modifies cards in hidden zones, or creates a delayed effect players must remember. Common cards should usually be understandable on first or second reading because they form most of the environment’s repeated gameplay.
Ask whether the card is a healthy incentive, a reliable role-player, or a reason to abandon previous picks. A strong card need not automatically move to rare, but a card that dominates games with little setup may need lower frequency in addition to a power adjustment. Rarity can reduce repetition; it cannot repair an unreasonable rate, weak counterplay, or a fundamentally unhealthy play pattern.
Broad effects belong lower when they support many decks and keep games moving. Narrow cards can move upward because they require particular creatures, counters, zones, or draft strategies. A narrow card at common risks becoming dead material for most players, while a narrow uncommon can act as a deliberate invitation to pursue a theme.
Rarity also communicates creative frequency. Ordinary soldiers, local wildlife, and routine spells naturally populate common. Named leaders, unique relics, and setting-defining events tend to feel rarer. This is not an absolute rule—a legendary theme can deliberately challenge it—but aligning mechanical and creative frequency makes a set easier to understand.
A custom set’s identity must be visible at common. If the theme is graveyard play but almost every enabler appears at rare, most drafts will not feel like graveyard drafts. Commons need to demonstrate the set’s basic actions: which creatures attack or block, what resources matter, how colors interact, and what players can expect from combat and removal.
Common is therefore a demanding design constraint rather than a label for weak cards. A successful common is useful, readable, and repeatable without making every game feel identical. It should also leave room for higher rarities to elaborate on the theme rather than forcing them to explain it from scratch.
Uncommons connect those pieces. A signpost uncommon usually gives a color pair or archetype a visible direction, such as rewarding modified creatures, cards leaving the graveyard, or casting a second spell. It should point toward cards that already exist at common. If the signpost invents an unsupported strategy by itself, it is less a signpost than an isolated build-around.
Place these cards in a set skeleton rather than evaluating them one at a time. Map each color’s common creatures, interaction, enablers, and payoffs, then check whether the uncommons reinforce what those commons already promise. The custom MTG set planning guide covers themes, mechanics, archetypes, and balance at that larger scale.
Rares have room for effects that are narrow, unusual, text-heavy, or undesirable in multiples. They can support decks that will not appear in every draft, create a memorable moment, or express a part of the setting that does not belong in routine gameplay. None of those qualities requires the card to be more efficient than a good common.
Mythic rare should be even more selective. Use it when the design is meant to feel singular: a central character, a world-changing event, or an effect whose scale and presentation would lose impact if encountered regularly. Do not use mythic as a patch for a card that wins too easily. First adjust its cost, timing, repeatability, resilience, or output. Then decide how frequently the corrected design should appear.
A useful test is to remove the rarity symbol and read the card again. If the only argument for mythic is “this is very strong,” the design probably needs another pass. If the effect feels narratively and mechanically exceptional even at a fair rate, mythic may fit.
Use one recognizable set-symbol shape across the project, then apply its rarity treatment consistently. The symbol needs to remain distinct at final card size; tiny interior details often collapse into an unrecognizable mark. Review it alongside the type line, rules box, power and toughness, and other high-priority information rather than judging a large isolated graphic.
Magic’s rules describe the expansion symbol as a visual element that normally appears below the illustration and uses conventional treatments to indicate rarity. The symbol itself has no effect on gameplay. For a custom project, color can reinforce rarity, but it should not be the only clue. Keep card lists, pack collation notes, or another readable label so that players are not forced to distinguish rarity solely by a small color change.
A custom set symbol also does not make a card official or legal in sanctioned play. Custom and proxy-style cards should not be presented as authentic or used where event rules require authentic cards.
Rarity should remain provisional until the surrounding environment has been tested. Put the card into a complete list or design skeleton, create representative packs or pools, and record what happens when players encounter it at the intended frequency.
Moving a card from common to uncommon may reduce repetition, but it can also remove infrastructure that an archetype needs. Moving an uncommon to rare can make a build-around too unreliable to draft. Use the custom MTG Draft playtesting workflow to examine those effects across picks, deck construction, and actual games.
Once the environment is stable, a Cube-oriented project can move from files and test slips toward a physical build through a custom Cube printing workflow. That step should come after the frequency and readability tests; polished copies make iteration slower if the rarity structure is still moving.
No. Strength is only one consideration. Efficient commons can be necessary for interaction and normal gameplay. If a card is too strong, fix the rate or play pattern directly; use rarity to control how often the corrected card appears.
Choose the treatment that matches its creative importance, often rare or mythic, but recognize that the label is mostly presentational outside a rarity-based environment. Commander balance depends on cost, color identity, repeatability, access from the command zone, and the expectations established in the Rule 0 conversation. See the custom Commander Rule 0 design guide for that review.
No. A small set, Cube module, teaching environment, or non-booster project may not benefit from a separate mythic tier. Add mythics only when their lower frequency and singular presentation serve the project.
Yes. It should. Rarity is part of the design, and playtesting may reveal that a common is burdensome in multiples, an uncommon archetype card is not seen often enough, or a rare is too scarce to evaluate. Record why you moved it so later revisions do not undo the change accidentally.
Assign rarity by deciding what the card must do for its environment. Put foundational, readable gameplay at common; directional rewards and selective build-arounds at uncommon; narrow, unusual, or repetition-sensitive effects at rare; and truly singular experiences at mythic. Then test the card at that frequency. Your next revision should answer two separate questions: is the card itself healthy, and does the environment encounter it the right number of times?
