What reissuing actually changes
A friend code is not a per-console label. It is tied to the Nintendo Account, which is why the same code shows up on each console linked to that account.
A Nintendo Switch friend code is associated with the Nintendo Account, so the same account uses the same code across linked consoles. Source
That matters for the decision in front of you. If the code leaked from a screenshot, a stream overlay, a forum post or a group chat, reissuing gives you a new code for the account. It does not, by itself, remove people who already added you, hide your profile, or erase copies that other people saved. Treat it as replacing a public identifier, not as a cleanup of your whole account.
Decide whether reissuing is the right move
Reissuing is a one-step action with a built-in cooldown, so it is worth deciding before you act. Use the situation, not a general fear of exposure, to choose.
| Situation | Reissue now? | Why |
|---|---|---|
| The code is posted where strangers can copy it and you no longer want new requests from that audience | Usually yes | A new code stops the old one from being the current way to add you |
| The code appeared only in a private chat with people you know | Often no | You can ask those people to delete the message; reissuing also changes the code for everyone else who uses it legitimately |
| You shared it in a tournament, clan or community post and still want those players to add you | Not automatically | Reissuing makes the posted code stale, which may confuse people you wanted to hear from |
| The concern is a person already on your friends list | Reissuing does not solve it | The code is an add mechanism; existing friendships are a separate matter |
| You may need to reissue again soon | Plan ahead | The 30-day wait applies between reissues |
If the code is public and you want it replaced, the owner can do it from the console settings:
- Open your user icon.
- Go to User Settings.
- Open Friend Settings.
- Choose Reissue Friend Code.
The owner can open their user icon, User Settings, Friend Settings and Reissue Friend Code. Source
The cooldown is the part people miss. Once you reissue, you cannot simply reissue again if the new code also leaks or if you change your mind.
Nintendo requires a 30-day wait before reissuing the code again. Source
So decide first, then act once.
Replace the copies you control
The old code does not disappear from places you posted it. After reissuing, work through the copies you can still edit, and mark the ones you cannot.
- Your own posts and profiles: edit or delete the code in bios, pinned posts, community threads, clan pages and personal sites. If a platform does not let you edit, delete the post or reply with a correction that the code is no longer current.
- Screenshots and clips you uploaded: replace or remove images that show the code. A caption saying “old code” helps, but the image itself may still be copied.
- Stream overlays, panels and templates: update the saved layout so the next broadcast does not reintroduce the old code.
- Documents and spreadsheets you share: update the code in rosters, sign-up sheets and friend-code lists you maintain.
- Places you cannot edit: note them. A code quoted by someone else, archived by a third party, or saved in a private chat is outside your control. Reissuing is what limits its usefulness going forward.
Do not describe this as deleting the old code everywhere. You are replacing the current code and reducing the places where the old one still points to you.
Verify the new code before you share it
After reissuing, confirm what the account now shows rather than relying on memory.
- Open your user icon and check the friend code displayed there.
- If you use more than one linked console, check that the same new code appears on the other console as well.
- Compare the new code character by character with what you plan to post. Friend codes are easy to mistype, and a wrong code sends people nowhere useful.
- Update your main public listing first, then the secondary copies, so the most visible place is correct even if you are interrupted.
- Ask one trusted person who can add you to confirm the new code works before you rely on it in a public post.
If the new code does not appear where you expect, or the reissue option is unavailable, stop and check the account state rather than posting a code you have not confirmed. The 30-day rule is one reason the option may not be available.
What this does and does not fix
Reissuing changes the code associated with the account. It is not a privacy reset.
- It does not remove existing friends. People already on your list stay there unless you remove them through the separate friend-management options.
- It does not hide your account. A new code is still a way to find and add you; it is not an invisibility setting.
- It does not recall copies. Posts, screenshots and messages that contain the old code remain wherever they were saved.
- It does not lock the account. This is a code change, not a password or sign-in change.
- It does not prove who added you. A request that arrives with the new code tells you the person has the new code, not who they are.
If your concern is a specific person rather than the code itself, handle that through the friend and block options available on the console, and treat the code change as a separate step.
A realistic order of operations
- Confirm the code is actually public and identify where it appears.
- Decide whether a new code helps your situation, using the table above.
- Reissue once, accepting the 30-day wait.
- Verify the new code on each linked console.
- Replace the copies you control, starting with the most visible.
- Note the copies you cannot change.
- Share the new code only where you still want to be added.
Where this fits with other lookups
Reissuing a friend code is one narrow action. If your wider question is which gaming profiles are associated with a username, that is a different task with different evidence: a public match is a lead, not proof that the same person owns every account. The related guide on finding someone’s gaming accounts across Steam, Xbox and PSN covers that lookup process and its limits.
For your own footprint, keep the two questions separate: replacing a code you shared, and understanding what a username search can and cannot show. Neither one is a complete inventory of an account, and neither proves identity on its own.