Why should you create payload indexes for fields that are filtered frequently at scale?

A payload index gives Qdrant an index structure for a field so it can evaluate filter conditions without repeatedly scanning all candidate payload values. As the collection grows, that can make the difference between predictable filtered retrieval and increasingly expensive candidate evaluation.

The reason Qdrant does not simply index every payload field automatically is that indexes consume memory and storage and add maintenance work on writes. The useful index set depends on actual query patterns and field types.

The trade-off is read performance versus write and resource overhead. For a high-cardinality field used on nearly every query, an index can be valuable. For a field that is rarely filtered, the additional index may not justify its cost.

A common misconception is that any filter becomes fast merely because it is syntactically present in a query. At scale, you should inspect the payload index configuration and benchmark the actual filter workload. Exact planner behavior can change across Qdrant releases.