The roster question people are really asking is which few to learn first, not how many exist.

Short answer

Learn two: one that is forgiving and one that fits how you already want to play. Breadth comes later.

A difficult pick with a high ceiling is worse than an easy one until you have put the hours in. Balance passes usually move numbers rather than reworking a kit, so the character still plays the same way. The community wisdom on this is roughly half right, and the half that is wrong costs the most time.

Good places to start

Role coverage inside a team matters more than the individual rating of any one pick. Tier lists describe a skill bracket, and most of them do not say which one. There is no hidden trick here that the game is keeping from you. Every roster has one entry that is quietly excellent and permanently unpopular.

The strongest pick in professional play is often the worst pick in a solo queue. Overwatch 2 is not shy about hiding useful information two menus deep, so some of this is simply knowing where to look. New additions are typically overtuned at release and corrected within two patches.

The picks that punish beginners

There is usually a fast way and a reliable way, and it is worth knowing which one you are choosing. Do the cheap check before the expensive one — that ordering alone saves most of the frustration. What follows assumes you are on a current install and have not modified it.

  • Watch one match of the pick before committing time to it.
  • Pick a role before picking a character.
  • Stop and reassess after two failed attempts rather than repeating the third.
  • Expect a new release to be nerfed within a month.
  • Learn one forgiving option properly before adding a second.

What changes between patches

Where something depends on your platform or region, that is called out rather than glossed over. A single check up front replaces a lot of guessing later. Where two approaches both work, the one with fewer moving parts is the one to keep. It helps to understand why a step exists, because then you can adapt it when your situation is slightly different.

Screenshots age faster than text, which is why this describes rather than shows. Anything that behaves differently on console than on PC is flagged where it matters. Patch notes move numbers around constantly; the shape of the answer holds even when a specific value shifts.

Why tier lists disagree

Half the pages on this topic were written for a build that no longer exists, which is why they stop matching what you see. Everything below is framed around the current state of Overwatch 2 rather than a launch-week impression. Treat anything stated without a version number as provisional.

None of this needs a paid tool, a third-party launcher or an account on a site you have never heard of. The developers have changed their mind about this at least once, which explains the older advice. If you are coming to this after a long break, the terminology has probably moved on.

How the roster breaks down

The short version is near the top on purpose; the reasoning is there if you want to know why. The awkward part is rarely the step itself, it is knowing which step comes first. Nothing here assumes a particular playstyle beyond wanting the thing to work.

Where people go wrong

  • Skipping the prerequisite because it looked optional in someone else's summary.
  • Grinding a method that was patched months ago because a thread still ranks well.
  • Rushing the last step, which is usually the one with the actual requirement in it.

Overwatch 2 FAQ

Who should I play first in Overwatch 2?

Something forgiving in the role you enjoy. The forgiving pick teaches the game; the flashy one teaches frustration.

Are tier lists worth reading?

The reasoning is. The ordering is a snapshot of one patch at one skill level.

Why do other guides describe this differently?

Most were written for an earlier version and never revisited. Compare the steps against what your build actually shows.

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.

Come back to the caveats list if it does not work first time — the answer is almost always in there.