D DeckLab.
Magic: The Gathering

5 MTG deck & play tools — built for the table, not the spreadsheet

These five calculators cover the questions an experienced MTG player asks between games: is my curve safe? should I keep this opener? am I actually building a 99 or a 112? Every tool runs in your browser, so paste a deck list freely — it never leaves your device.

Mana Curve Analyzer

Paste a deck list (one card per line, e.g. 4 Lightning Bolt) and the tool computes your converted mana cost distribution, gives a real visual histogram, and assigns a curve-quality score from 0–100. Unlike generic histogram tools, we factor in average mana value, drop-off between adjacent slots, and the "spike" risk if your top end is too heavy.

How the curve-quality score works
  • 20 pts for a single dominant peak (typically CMC 2 or 3 in aggro, 3 or 4 in midrange).
  • 20 pts for a smooth drop-off (no CMC slot 3× the previous slot).
  • 20 pts for telling "early plays" (CMC 1–2) ≥ 30% of the deck.
  • 20 pts for keeping CMC ≥ 6 under 15% (commander excluded).
  • 20 pts for a low average CMC (lower = better, capped at 2.5 for the bonus).

Minimum Deck Size Solver

A common rookie question: "do I really need 60 cards in Standard?" — yes, but why? This solver takes your core playset counts and the expected number of games, then computes the smallest deck size where the probability of drawing one of your key cards by turn N still clears a target threshold. The answer is usually 60, but for singleton formats it can be lower.

Opening Hand Simulator

We don't just shuffle 7 random cards. This tool draws N virtual opening hands from your deck, applies the current mulligan rule you select (Vancouver, London, Paris), and rates each hand with the actual keep / mulligan verdict you'd give at the table: lands, color-sources for spells, and curve fit. There's no auto-pilot — you see the proposed decision and decide.

Run 1,000+ hands in seconds and look at the distribution of "keepable" percentages across the deck — a much better deck-health indicator than a single sample hand.

Uses crypto.getRandomValues for fair shuffles. Numbers update in real time as you change inputs.

Color Identity & Pip Analyzer

Counts mana pips (W/U/B/R/G) and on-color sources (lands that can produce them). Flags decks where the dominant color lacks enough sources (≥ 8 sources for an off-color splash is a common failure mode), and warns when a splash is so deep that you really need 4 fetch lands, not 2.

Commander Damage Tracker

Four players, twenty-one commander hits each, poison, commander tax, emblems, one-tap undo. Built for phones so the player across the table can read it. No logins, no auto-rollback. State lives in your browser; we never see it.

MTG tool FAQ & usage notes

Why does the curve score punish "all 2-drops"?

A deck of 20 two-drops and 40 lands drops everything on curve but can't close games. The score penalizes flatness at CMC 2 because real games need a top end. The exception: hyper-aggro decks in Modern/Legacy can safely ignore this.

Should I trust the London vs. Paris mulligan math?

Use London for competitive and most casual play (post-2019). Paris is only relevant for very casual tables. The simulator implements both because the answer can change by 4–6 percentage points for low-color decks.

Why no card database on the curve tool?

CMC is a static number; we parse it from your input. Pulling Scryfall for every card would slow the tool and send your deck to a third party — defeating the privacy promise.

Why doesn't the commander tracker auto-detect who's who?

Auto-detection would need camera + card-recognition, which is a privacy and battery hazard. Clicking is faster than that and works offline.

Sponsored editorial slot.

Reading the five MTG tools correctly: a manual companion to the page

The MTG page covers the five questions that come up between games: is my curve safe, how small can my deck be, can I keep this hand, does my colour base hold up, and where does everyone stand on life totals. Each answer here is a calculator with a specific input contract, and two of them deliberately trade precision for speed. This usage guide walks through every tool step-by-step, explains what each output actually measures, and lists the common mistakes that turn a correct deck into a misleading number. It also sets out the limits of the page, so you know exactly when to check the official format policy instead of the tool.

① Mana Curve Analyzer — reading the score and its notes

  • Paste one card per line with the copy count in front, for example 4 Lightning Bolt, and keep the sideboard out of the paste.
  • The tool buckets cards by mana value into 0, 1, 2, 3, 4, 5, 6 and 7+, then awards up to twenty points for each of five conditions: a clear peak, a smooth drop-off, at least thirty per cent early plays, a controlled top end, and a low average mana value.
  • Read the notes under the histogram first. Each note names the condition you failed, and that line is the fastest diagnosis of what to change in the list.
  • Watch out for the pricing fallback: cards outside the built-in lookup are priced from the trailing number in the name, then from a letter-count heuristic, so unusual names should be checked against their real mana value.

② Minimum Deck Size Solver — the number behind the number

  • Enter how many copies of the key card you run, how many cards the deck holds now, the turn by which you need the card, and the probability you are willing to miss.
  • The headline figure is the chance of having seen at least one copy once you have drawn a hand plus one card per turn, so a turn-four question counts ten seen cards.
  • The second line is the smallest deck that clears your target, searched in whole-card steps from forty up to a hundred, so the answer is a floor rather than an optimum.
  • Key caution: the search range has a ceiling, so a target that needs more redundancy than a hundred cards can offer reports a hundred and no more.

③ Opening Hand Simulator — what it simulates, and what it does not

  • Choose the hand size, the number of samples, and the mulligan system, then read the keep percentage and the land-count histogram underneath it.
  • It builds a synthetic sixty-card deck with twenty-four lands and a fixed spread of mana values, shuffles it with a cryptographic generator, and rates each hand as keep or mulligan.
  • The keep rule is deliberately simple: two to five lands, plus at least two early spells under the London system, while the Paris and Vancouver settings use the land count alone.
  • The most common mistake is easy to get wrong here: the simulator never reads your deck list, so the number is a baseline for a generic deck, not a measurement of yours.

④ Colour Identity and Pip Analyzer — where phantom pips come from

  • List each card with its colour letters after the name, such as 4 Lightning Bolt R, and the tool separates pip demand from the sources that can pay for it.
  • Lands are recognised by name, and their colour letters are counted as sources; everything else contributes pips in proportion to its copy count.
  • The warning fires when a colour holds more than five per cent of the pips but less than ten per cent of the sources, which is the classic splash failure mode.
  • The key trap: every W, U, B, R or G letter in the text counts, so a land such as Bloodstained Mire contributes a phantom black pip and any unfamiliar land may be misfiled as a spell.
Three common mistakes: ① dropping the copy count from a deck line, because a bare card name is read as a single copy and every histogram, average and score shifts downward; ② quoting the curve-quality score as a measurement when unknown cards are priced by a fallback heuristic — verify the mana values of anything unusual before you trust the shape; ③ reading the opening-hand keep-rate as a property of your own deck when the simulator builds a generic sixty-card deck with its own land count, and every curve number includes the commander card if you paste it.
How do I use these five tools step-by-step?

Work from the deck outwards. Paste the list into the curve analyzer and fix the notes it prints; use the deck-size solver to justify how many copies of your key card you can afford; check the colour analyzer for a splash that your land base cannot pay for; then run a few thousand simulated hands to see whether the deck keeps what it should. Keep the commander damage tracker open separately during the game — it tracks life, poison and per-source commander damage with a single-tap undo, and it deliberately does not model emblems, commander tax or copy effects.

Why does the curve analyzer price cards from the name?

Because the tool never contacts a card database — that would mean sending your deck list to a third party, which breaks the privacy promise of the page. It uses a small built-in table for common cards, then a trailing-number rule, and only then a rough fallback based on the length of the name. That fallback is the part to watch: for an unfamiliar or custom card the price can be off by a mana value or more, which is enough to move a histogram bucket. If a deck uses many such cards, price them by hand first.

What are the common mistakes in a deck-list paste?

Four account for most broken results. Missing copy counts, since a bare name means one card. Splitting one card across two lines, which creates two entries instead of one. Leaving the sideboard in the paste, which inflates the card total and the average. And including the commander card when you want a Constructed reading of the curve, since every line you paste is scored and counted.

What are the limits of these MTG tools, and what is this not for?

This page does not read the current banlist, the format rotation, card legality or the tournament policy, and it is not a card database, so always confirm the format and card legality with the official publisher and tournament organiser before entering a sanctioned event. The maths also carries modelling limits: the deck-size solver ignores mulligans and card selection, the hand simulator uses a generic deck, and the curve score is a heuristic built on five rules rather than a proven model. Nothing here guarantees a result at the table.

Scope and limits: every tool runs locally in your browser, no deck list is uploaded, and no state is saved between visits unless you copy it yourself. Scores, keep-rates and probability estimates are informational and assume standard rules and a generic deck where noted. Card lists, product contents, prices and legality differ by product and by region and change with every release, so verify against the official publisher and the current format policy before you build, trade or compete.