Direct answer: a Muse invite code can be redeemed a limited number of times, and then it is finished — but the exact cap is not a number you should plan around, because published reports disagree about it. On this wall, the number that decides your next move is not the cap, it is the card's remaining-uses number: a card showing uses left is still alive, a card showing 0/30 is done, and a low number means redeem now or pick a fuller card. This guide resolves the conflicting cap figures honestly, explains what one "use" actually means, and gives you the decision rule for low numbers.
If you search this question, you will find two different answers, and both look confident. One set of third-party guides reports that each code works for up to 30 redemptions. Another reports, citing Meta's own social posts, that each person can invite up to 20 friends. Those two figures cannot both be the same cap, and this site has no official Muse source that settles which one is current — so this page does not pick one and present it as fact. Treating either figure as settled would be exactly the kind of invented precision this site refuses to publish. What is verified is the wall's own scale: cards here show uses left as a number out of 30, because that is the scale submitters post on, and visitors mark uses with the "I Used" button. So a card reading 27/30 means 27 uses left on the wall's scale — that remainder is actionable whether the true underlying cap is 20 or 30. The cap is trivia; the remainder is the decision.
A use is one successful redeem by one account. It is not one view, one copy, or one failed paste: copying a code without redeeming it consumes nothing, and a paste that fails (a typo, a spent code, a closed window) does not consume a use either — it just fails. What consumes a use is a redeem that goes through. Two consequences follow. First, a code's remaining count only falls when people actually get in with it, which is why a popular card's number can drop fast: every successful join is one fewer use for everyone after. Second, the count on a card you found elsewhere — a screenshot, a chat message, a frozen list — is unknown, because no number travels with a bare code string. Only a wall card carries a number, and that number is the only remainder you can check before pasting. (How to run that pre-paste check in full is the subject of the dead-before-trying guide.)
Forget the cap and read the card:
One more rule about timing: a code's uses and your joining window are two separate clocks. A code can run out while your window is still open, and your window can close while a code still has uses left. The window rule lives on the redeem page — this post does not re-explain it, it just flags that a live code does not help once the window has closed, and a closed window is not a reason to blame the code.
Example 1 — 27/30, comfortable. Maya copies a card showing 27/30 and redeems at once. The redeem goes through; the card now shows one fewer use for the next person. The cap never entered her decision — the remainder did, and it was plenty.
Example 2 — 2/30, a race she loses. Ben sees a card at 2/30, switches apps to check something, and comes back ten minutes later. The card now shows 0/30: two other readers redeemed in between. His mistake was not picking a low card — it was treating a low card as if it would wait. With 1–3 uses left, redeem immediately or pick a fuller card.
Example 3 — 0/30, correctly skipped. Priya scans the wall, sees a greyed-out 0/30 card with its copy button disabled, and moves on without pasting. The wall greyed it out precisely so she would not waste a paste — or window time — on a finished code. What happens at zero in full is covered on the runs-out page.
Example 4 — No number, a blind paste that fails. Tom pastes a code from a group-chat message. It fails as already redeemed — the code's uses were gone before he ever saw it, and nothing in the message could have told him. The failure was not bad luck; it was the predictable result of pasting without a number. His fix is the wall, where the number is visible before the paste.
The same arithmetic runs in reverse for sharers. Post a code with an honest uses-left count, and every successful redeem by a stranger reduces it; when it hits zero, the card greys out and stops being copyable. A used-up code does not refill, and you cannot top it up — if you receive a new code, that is a separate code, posted as a separate submission with its own count. Whether sharing earns the sharer anything is a separate question, and rewards vary by account: that question belongs to the sharers-rewards page, not this one, and this site promises no reward amount. How the wall's free pool and paid slots display those counts is explained on the wall-mechanics page.
A limited number of times — but published reports disagree on the cap (20 vs 30), so no single cap figure is stated as fact here. On this wall, act on the card's remaining-uses number, not on the cap.
No. One account redeems one code; a second code has nothing left to do for an account that is already in. If you can already use Muse, you do not need another code at all.
No. A used-up code does not refill. A holder's new code, if any, is a separate posting with its own count.
Copy it exactly and redeem it at once, inside your 48-hour window — or pick a card with more uses left. A low number can hit zero between the moment you see it and the moment you paste it.
You know the rule now: ignore the disputed cap, read the remainder, and treat a low number as a race. The wall below shows live codes with their uses-left numbers — pick one that still has room, copy it exactly, and redeem it before your window closes.
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.