How to redeem codes in Universal Tower Defense Z

The redemption how-to for Universal Tower Defense Z: where the Codes button lives, why the exclamation mark matters, and what to do when a code refuses to work.

Last updated 2026-07-14 · By Jim Liu

TL;DR
Open the game, find the Codes button on the right-hand menu, type the code exactly including the exclamation mark on the end, press Redeem. If it fails, it is expired far more often than it is mistyped. This page is the how-to. The actual working list, with dates, lives on the codes page and moves faster than this one does.

The four steps

It takes under a minute once you know where the button is.

  1. Open Universal Tower Defense Z on Roblox.
  2. Find the Codes button on the right-hand menu.
  3. Type the code exactly as written, including the exclamation mark.
  4. Press Redeem. A code that fails is almost always expired rather than mistyped, though it is worth checking your capitalisation first.

Every step of that is boring except the third one, and the third one is where nearly everybody loses a valid code. The exclamation mark at the end of a code like WeLoveUTDZ! is part of the code. It is not enthusiasm someone added to the end of a sentence in a video description.

Why your code just failed

In the order the causes actually occur, not in the order guides list them.

  • It expired. This is the answer most of the time. Codes in this game are short-lived, and a list that was accurate a week ago is partly fiction today.
  • You dropped the exclamation mark. Second most common, and the easiest to fix.
  • Capitalisation. Type it exactly as written rather than as your phone keyboard would like to write it.
  • You already redeemed it. One per account. A code you used on release day reads as invalid now, which looks identical to expiry from the player side.

When new codes appear

There is a pattern here and it is not a weekly schedule.

Look at the names on the active list and the pattern gives itself away. Codes such as UTDZApologyForBugs! and SrryForWhoopsie! are apology gifts, issued after something broke. UniversalDelayDefense! and UniverseFestDelay4! point at a delayed release.

So the useful signal is not the calendar. It is trouble. When the game has a rough patch day, a rollback or a delayed update, that is when to come back and check, and that is when we re-check too.

Not verified yet. We do not list what each code pays out. The community lists that quote reward amounts do not agree with each other, and a reward figure is exactly the kind of detail that is easy to invent and impossible for you to check before you have already spent the code.

Where the actual list lives

Deliberately not on this page.

This page teaches the process, which barely changes. The codes page carries the list, which changes constantly, and it carries a date against every entry so you can see how stale you are looking at. Expired codes move to an archive there instead of being deleted, because "did this used to work" is a question people genuinely ask.

FAQ

Where is the Codes button in Universal Tower Defense Z?
On the right-hand menu in the main lobby. It is a menu button rather than a settings option, which is why people who go looking in settings first conclude the game has no codes.
Why does my code say invalid?
Almost always because it expired. Codes in this game are short-lived and several of them are apology gifts issued after an outage, so they turn over faster than the average Roblox game. Check the capitalisation and the exclamation mark before you assume the code is dead, then assume it is dead.
Do I need to type the exclamation mark at the end of the code?
Yes. Most codes in this game end with one and it is part of the code, not punctuation someone added to a sentence. Leaving it off is the second most common reason a valid code is rejected.
Can I redeem the same code twice?
No. Codes are one redemption per account, which is why a code that worked yesterday reads as invalid today on the same account.
How often should I check for new codes?
After any outage or rollback, and around a patch. Both are the moments this developer historically ships codes, and both are more reliable signals than checking on a schedule.

Where to go next