Honkai Impact 3rd Codes

Working Honkai Impact 3rd codes

4 working codes right now

Source column shows who carries the code as active today. Last checked is the date we last opened those sources and looked — it is the same date on every row because the whole list is gone through in one pass. It is not a claim that a source confirmed the code that day. The wiki list was opened on 26 Sep 2026. Nothing here was tested by redeeming it ourselves, so a code can still fail for reasons we cannot see from outside the game.

The server is the gate, not the code

On most games the server is something you set once and forget. Here it is the first thing to check, because a code that is alive and correct can still be refused for the account you typed it into. The list we read is explicit about it: these codes are Global only, covering NA and EU, and on any other region — SEA, CN, JP or KR — they will not work at all.

It shows up in how players share codes between each other, too. In the invitation threads we follow, the pinned instruction is not about the code at all — it is about the server, and every reply tags theirs next to the string, because a code handed to someone on the wrong server is wasted. Those invitation codes are a different thing from the promotional codes listed above, but the rule they are obeying is the same one: the account's server decides whether the string is worth anything.

One practical consequence for this page. A code that reads as working above is working for the servers the source covers. If you play on SEA, JP, KR or CN, our working column is not a promise about your account, and the honest answer is that the sources we read do not cover yours.

“Already used up”, or the screen that never finishes

Two different failures get reported constantly in the threads we follow, and they need different answers. One is the code being spent. The other is the redemption screen doing nothing at all.

The code has already been used up

This one is exactly what it says. Codes are single-use, so a code that has been claimed on an account is spent for that account, and a widely shared code is spent for everybody once its usage limit is reached. The way players put it in the threads we follow, quoted as written:

“Exchange Failed. Redemption code already used up.”

“Problem redeeming codes”

Neither is a fault on your side, and neither is fixable by retrying. What is worth doing is checking the server first — a code entered on the wrong server fails too, and that one is worth retrying on the right account.

The screen hangs and nothing happens

The second failure looks worse than it is. A player asking about it, in the threads we track:

“It stays like that for a few minutes and nothing changes, I do have internet, can someone explain?”

The replies are short and they agree with each other — wait, or restart:

• “Try to restart. If it doesn't work then idk”
• “this happened to me as well, i just wait for 2 minutes”
• “This happens to me too, I can confirm this usually works.”

Two minutes, or a restart, is the answer the players who hit it settled on. It is not a published instruction from the developer, and we are reporting it as what those players say, because it is the answer to the question this page exists for.

How to redeem Honkai Impact 3rd codes

There is one route, and it is inside the game. There is no separate public redemption website for this title the way there is for the other HoYoverse games, so a “where do I enter this” search has only one correct answer here.

1. Open the game and go to the Bridge.
2. Tap your name in the upper-left corner of the screen.
3. Select Account on the right.
4. Highlight the Exchange Rewards box and type or paste the code there.
5. Confirm, then check your in-game mail for the reward.

Because everything happens inside the client, a code can only be entered on the account you are logged into — which is why the server question above comes before anything else, and why a code that works for a friend can still fail for you.

Expired Honkai Impact 3rd codes

We keep expired codes instead of deleting them, because you may want to check whether you already claimed one, and because a code that reads “expired” on one page is often still printed as active on a page that was never updated. Where a source does not state the exact expiry date, we say so rather than guess.

The source records the date each code was posted and moves it to a Legacy list once it stops working, but it does not publish an expiry date, so the column above says so rather than inventing one. The six kept here are the birthday-event and milestone codes from June to August 2026, the stretch that people are most likely to still be trying. We have not copied the source's full historical archive — a wall of long-dead codes pushes the four that work off the first screen.

How we set a code's status

• Working — at least one source on our list carries the code as active, and none carries it as expired.
• Not verified yet — no source on the list carries it, or two of them disagree.
• Expired — a source on the list carries it as expired, and none carries it as active.

Our source list is fixed: the developer's own announcements and community channels, the in-game redemption menu, and the code pages currently ranking in front of us for this search. Nothing outside that list counts. On this page the readable source today was the community wiki's Exchange Rewards list, opened on 26 Sep 2026, which records the official posts each code came from.

Last checked is the last date a source on our list carried that code, so it is not the date of our last pass — that one is in the line at the top of this page, and it is the same for every row. The date is shaded by how recent it is: near-black for today, mid grey for yesterday, lighter for two days ago, barely-there grey after that. A row whose date stops moving is a row nothing out there is listing any more.

Ten days without a source. If no source on our list carries a code for more than ten days, the row drops out of Working into Not verified yet and picks up a Likely expired note. That happens automatically, not by hand. Ten days is our own threshold — the developer publishes no such rule — and we would rather show a code as unconfirmed than keep calling it working on no evidence.

Frequently asked questions