If you have spent any time in React, you have seen the yellow warning in your console: “Each child in a list should have a unique ‘key’ prop.” It sounds like a polite suggestion, but React is actually warning you that it cannot tell your list items apart. Ignore it, and you will eventually ship a bug that is maddening to reproduce—state jumping to the wrong row, text inputs losing focus, or animations firing on the wrong element.

React’s rendering engine does not compare your UI pixel by pixel. It builds a lightweight tree of objects called the virtual DOM, compares the new tree to the previous one, and calculates the smallest set of changes needed for the real DOM. When you render a list, React sees an array of sibling elements. Without keys, it has no reliable way to know whether an item moved, was replaced, or was removed. It defaults to matching by position, which is fragile. Keys act as stable identities. They tell React, “This element is the same one as before, even if it is now in a different slot.” Get this wrong, and you trade deterministic updates for guesswork.

The Minimum Fix

The warning usually appears inside a map call. You must assign a unique value to the key attribute on the top-level element returned from the iterator.

Here is the pattern you see in every codebase that triggers the warning:

const UserList = ({ users }) => {
  return (
    <ul>
      {users.map((user) => (
        <li>{user.name}</li>
      ))}
    </ul>
  );
};

React sees three <li> tags and has no idea which is which. The correction is one attribute:

const UserList = ({ users }) => {
  return (
    <ul>
      {users.map((user) => (
        <li key={user.id}>{user.name}</li>
      ))}
    </ul>
  );
};

The key must be assigned to the element directly inside the map callback. If you extract the <li> into a separate UserItem component, the key still belongs on the component at the call site:

{users.map((user) => (
  <UserItem key={user.id} user={user} />
))}

Placing the key inside UserItem on its internal <div> will not silence the warning and will not fix the reconciliation behavior. React looks for the key on the element returned by the iterator.

Why Index as a Key Is Dangerous

It is tempting to silence the warning by reaching for the second argument of map:

{users.map((user, index) => (
  <li key={index}>{user.name}</li>
))}

This removes the console noise, but it does not solve the underlying problem. Array indices are not identities. They are positions, and positions change.

Imagine a list of three users rendered in this order:

  1. Alice (index 0)
  2. Bob (index 1)
  3. Charlie (index 2)

If you delete Alice, Bob shifts to index 0 and Charlie shifts to index 1. React compares the new tree to the old tree. It sees that index 0 now holds Bob’s data, so it mutates the existing DOM node that previously showed Alice. If that node had focus, the cursor stays in the first row, but the text changes to Bob. If the row contained an <input> with local state, that state remains stuck to index 0. The user types into what looks like Bob’s row, but the state belonged to Alice. The same chaos happens when you sort, filter, or prepend items. The only safe place for an index key is a list that is truly static: no reordering, no filtering, no inserting, and no deleting. Hardcoded navigation links that never change are a fair example. Everything else needs a real identifier.

Where to Find a Stable Key

The best key is a unique identifier that already exists in your data model. Database primary keys like id are ideal because they are guaranteed unique and they survive across renders. If your backend returns objects with uuid, slug, or some other naturally unique field, use that instead.

When your API response lacks any unique field, you have two practical paths. First, talk to your backend team and ask them to include an id. Shipping relational data without a primary key is a smell, and fixing it at the source removes ambiguity everywhere in your stack. Second, if you are generating items entirely on the client side—say, a todo list where users create tasks before anything hits the server—generate an ID once at creation time. Libraries like uuid or nanoid are built for exactly this. Generate the ID when the user submits the form, store it on the object, and use it for the key forever.

Never generate a key inside the render path. Calling Math.random() or Date.now() during a component render produces a new value on every pass. React sees a new key, assumes it is a brand new element, destroys the old DOM node, and creates a fresh one. Any state inside that element resets. Focus is lost. Performance tanks because React is doing unnecessary DOM work. A randomly generated key is worse than no key at all.

Fragments, Components, and Scope

Una trappola meno ovvia riguarda i React Fragment. Se esegui un map su dei dati e devi restituire più elementi fratelli senza un wrapper <div>, potresti ricorrere alla sintassi abbreviata:

{items.map((item) => (
  <>
    <dt>{item.term}</dt>
    <dd>{item.definition}</dd>
  </>
))}

La sintassi abbreviata <>...</> non supporta le props, il che significa che non puoi allegare una key. In questo caso, passa alla sintassi esplicita completa:

{items.map((item) => (
  <React.Fragment key={item.id}>
    <dt>{item.term}</dt>
    <dd>{item.definition}</dd>
  </React.Fragment>
))}

React ha bisogno di quella key sul Fragment per poter tracciare la coppia come un'unica unità attraverso i render.

Un altro punto sottile: le key non sono props nel senso comune del termine. Se scrivi <ListItem key={item.id} />, il componente ListItem non può leggere props.key. React la consuma internamente per la gestione interna. Se il tuo componente ha realmente bisogno dell'identificatore per la propria logica, passalo separatamente con un nome diverso, come itemId.

Regole pratiche per proteggerti

  • Preferisci gli ID del database. Sono univoci, basati su numeri o stringhe, e stabili.
  • Usa uuid o nanoid per i dati solo client. Genera l'ID una sola volta quando il record viene creato, non all'interno del render del componente.
  • Non derivare mai una key dall'indice dell'array se la lista può cambiare. Ordinamento, filtraggio ed eliminazione introdurranno bug visivi e di stato.
  • Non usare mai Math.random(), Date.now() o qualsiasi valore che cambi tra i render. Questo forza un unmounting e un remounting non necessari.
  • Ricorda che i Fragment richiedono la forma estesa se si trovano all'interno di un map e necessitano di una key.
  • Posiziona la key sull'elemento restituito da map, non all'interno di un componente figlio.

La lezione fondamentale

La prop key non è una regola di lint decorativa. È il modo in cui React mantiene l'identità attraverso i render. Pensala come una chiave primaria in una tabella di un database. Quando quell'identità è stabile, React può spostare, aggiornare e rimuovere gli elementi con precisione. Quando manca o è instabile, ne paghi le conseguenze con uno stato dell'interfaccia utente corrotto e una riconciliazione lenta. Risolvilo una volta a livello di dati e le tue liste si comporteranno in modo prevedibile, indipendentemente da quanto crescano o cambino.