Direct answer: the number on a wall card — say, 14/30 — is the uses the submitter says are still left, on the wall's out-of-30 scale, moved down when visitors mark "I Used" after redeeming. It is not Muse's own count, it is not a reservation, and it is not a promise the code will work. Read it as a decision, not a guarantee: plenty left means paste it, 1–3 left means redeem now or pick a fuller card, 0/30 means finished, and no number at all means you cannot check the code. This guide decodes the number piece by piece, including the two ways it misleads: an overstated submission and a number that moves while you are looking at it.
The numerator is uses left, as reported. When a card reads 14/30, the claim is: 14 redemptions are still available on this code, according to the wall's records. That record starts with the submitter, who posts the code with a uses-left count (defaulting to 30), and then moves only one way: down, by one, each time a visitor marks "I Used" — and only once per visitor per code, so one person cannot drain a card's displayed count by clicking repeatedly. Nothing else moves it. No system checks with Muse, no automatic sync, no correction when someone redeems without marking. The numerator is therefore a human-maintained claim, not a meter reading.
The denominator is the wall's scale, not Muse's cap. Cards show uses out of 30 because that is the scale submissions use on this wall. It is not a verified statement that Muse allows 30 redemptions per code — published reports disagree on the cap, and the uses-count page lays out that dispute without picking a winner. The practical consequence is simple: do not plan around the denominator at all. A card reading 27/30 does not mean "27 of Muse's allowance remain"; it means "the wall's record says 27 remain." The remainder is actionable either way — that is why every decision in this guide uses the numerator, never the cap.
Zero has a visible form. At 0/30 the wall greys the card out and disables its copy button. That is not decoration; it is the wall telling you the decision before you make it. A greyed-out card needs no further reading.
The four cards below are constructed scenes, not real visitor cases — they show the decision each reading forces.
Card A — 27/30: paste it. Maya opens the wall, sees a card at 27/30, copies exactly from the card, and redeems. Plenty of room, currently listed, exact copy: nothing in the number argues against trying. If it fails anyway, the failure is a diagnosis question, not a reading error — run the invalid-code diagnosis in order.
Card B — 3/30: a race, not a rejection. Luis finds only low cards. 3/30 is not dead — it is a code with a short fuse. His correct move is to redeem immediately, not to bookmark it and come back after lunch, because three uses can go to three other readers in the meantime. If he cannot redeem right now, a fuller card is the better pick even if it takes an extra minute to find.
Card C — 0/30, greyed out: skip it. Priya's eye lands on a greyed-out card with its copy button disabled. She does not paste it "just to be sure" — the wall has already done the checking. She picks the next card showing uses left instead.
Card D — no number at all: uncheckable. Sam pastes a code from a friend's screenshot. There is no card, no number, no progress bar — nothing to read. That absence is the verdict: the code cannot be checked before pasting, so pasting it is a guess. The fix is not a better guess; it is a wall card with a visible number. (The full pre-paste check is on the dead-before-trying page.)
An overstated submission. A submitter posts a code at 30/30 that they have already shared elsewhere, where half its uses are gone. The wall has no way to know: it records the submitted count, and the card looks full. You paste it, it fails as already redeemed, and you feel tricked — but the wall never claimed the number was verified, only reported. The defence is procedural, not personal: one failed paste is a verdict on that code, not a reason to keep retrying it. Diagnose it, pick the next live card, and report the dead one (one report per visitor per code) so the next reader's number gets truer.
A number that moves while you look. You see 2/30, you hesitate, you go to check something else — and by the time you paste, two other readers have redeemed and the code is at zero. Nothing was wrong with the reading; the reading was simply old. With low cards, the gap between seeing and pasting is the risk. The rule that follows is blunt: the lower the number, the shorter the gap you can afford. A 27/30 card tolerates a pause. A 2/30 card does not.
If your redeem goes through, mark "I Used" on the card. That single mark is what keeps the next reader's number closer to the truth — it is the wall's only mechanism for moving a count down, and it only works if the people who actually redeemed use it. If your redeem fails, do not mark it: a failed paste consumes no use, and marking one would make the next reader's number wrongly lower. Marking honestly is a small act, but on a wall where the number is the whole check, it is the difference between a useful number and a decorative one.
No. A use is a successful redeem, not a copy or a failed paste — the uses-count page explains what one use means.
Because 30 is the wall's display scale, set when a code is submitted — not a settled Muse cap. Published reports disagree on the cap, so this site states no single cap as fact; the remainder on the card is what you act on.
Yes. It is submitter-reported and moved only by visitors' "I Used" marks, never checked against Muse — so it can overstate the truth, and it can lag behind real redemptions. A live-looking card can still fail.
No. Once a code's uses are gone they are gone; a holder's new code, if any, is a separate posting — the runs-out page covers the zero state.
You can read the number now: plenty means paste it, low means redeem now or pick a fuller card, zero means skip it, and no number means do not guess. The wall below shows cards with their numbers visible. Pick one with room, copy it exactly from the card, and redeem it while your window is open.
Try a code that still has uses →
Disclaimer: all codes on this site are user-submitted and NOT guaranteed valid (they may be used up, revoked, or expired). Paid placement does not mean verified. This site is not affiliated with Meta or Muse and is not an official channel. Reward amounts vary by account; this site promises no reward amount.