Half the lists circulating for codes contain entries from an older version that simply do nothing now.

Short answer

Enter them exactly as written, on the platform-appropriate input, and expect achievements to be disabled for that save.

Console entry uses button sequences with tight timing, and mistiming reads as a broken code. Achievement locking is usually per-save rather than per-account, but not always. Half the pages on this topic were written for a build that no longer exists, which is why they stop matching what you see.

What each one actually does

Case and spacing matter more than the lists suggest. Codes typically do not persist through a reload, which surprises people who use them for convenience. Most of the disagreement you will find online is two people describing different builds. A code that softlocks a mission is a known risk in more than one of these games.

Anything that requires downloading a program is not a cheat code. Patch notes move numbers around constantly; the shape of the answer holds even when a specific value shifts. Some effects stack in ways the developers did not intend and the game does not handle gracefully.

Codes that no longer work

Nothing here assumes a particular playstyle beyond wanting the thing to work. If you are coming to this after a long break, the terminology has probably moved on. Treat anything stated without a version number as provisional.

  • Expect achievements to lock for that save file.
  • Ignore any list that asks you to install something first.
  • Check the version you are actually running before assuming anything is broken.
  • Re-enter the same code to toggle an effect off.
  • Save manually before using anything irreversible.

How to enter them

None of this needs a paid tool, a third-party launcher or an account on a site you have never heard of. The community wisdom on this is roughly half right, and the half that is wrong costs the most time. There is no hidden trick here that the game is keeping from you. Overwatch 2 is not shy about hiding useful information two menus deep, so some of this is simply knowing where to look.

Everything below is framed around the current state of Overwatch 2 rather than a launch-week impression. There is usually a fast way and a reliable way, and it is worth knowing which one you are choosing. If your result differs from what is described here, note what is different first rather than starting over.

What you give up

A single check up front replaces a lot of guessing later. Screenshots age faster than text, which is why this describes rather than shows. The developers have changed their mind about this at least once, which explains the older advice.

Where two approaches both work, the one with fewer moving parts is the one to keep. The short version is near the top on purpose; the reasoning is there if you want to know why. What follows assumes you are on a current install and have not modified it.

Anything promising online effects

Anything that behaves differently on console than on PC is flagged where it matters. Where something depends on your platform or region, that is called out rather than glossed over. The awkward part is rarely the step itself, it is knowing which step comes first.

Where people go wrong

  • Rushing the last step, which is usually the one with the actual requirement in it.
  • Treating a rare edge case as the normal behaviour and planning around it.
  • Grinding a method that was patched months ago because a thread still ranks well.

Overwatch 2 FAQ

Do I need any mods or third-party tools for this?

No. Everything described here works with the base game on any supported platform.

Will using these get me banned?

Not in single-player, where they are an intended feature. Anything claiming to do the same online will absolutely get an account banned.

Is this still accurate after the latest Overwatch 2 update?

The method is; individual numbers may not be. If a value on your screen differs, trust the screen and keep the sequence.

What if none of this works for me?

Then something in your setup differs from the assumption — version, region or platform. Check those three before anything else.

If you only take one thing from this: the answer near the top is the part that matters, the rest is context.