LinkedIn analytics tracking pixel for AIDOLS AI consulting website performance measurement
Deployment & Operations

Chunking Strategy

A chunking strategy is the rule set used to split source documents into retrievable units before embedding, which directly determines retrieval recall and answer faithfulness in a RAG system.

Full definition

Common strategies: fixed-token chunks with overlap (simple, baseline), recursive character splitting (respects markdown/code structure), semantic chunking (split at embedding-distance boundaries), hierarchical chunking (parent-child with small chunks pointing to larger context), and proposition chunking (atomic factual claims). Chunk size 256-512 tokens with 10-20% overlap is the typical starting point. Too small loses context; too large dilutes retrieval signal.

Why it matters

Chunking is the most underrated lever in RAG. Teams that obsess over embedding-model choice while ignoring chunking leave 10-30% of retrieval quality on the table. Reviewing chunks against real failed queries is the highest-ROI debugging step.

Example

A medical-records RAG fails on patient-history questions; chunks are 200 tokens but symptoms appear 600 tokens before diagnoses. Switching to hierarchical chunks with 1500-token parent context fixes 70% of failures.

Source & further reading

Primary source: Anthropic — "Contextual Retrieval" (2024).

Citation policy: this entry is part of the AIDOLS AI Implementation Glossary and may be quoted for research, journalism, and education with attribution to aidolsgroup.com/es/glossary/chunking-strategy/.