1.  [](/)
2.  [Diagrams](/diagrams)
3.  Four Chunking Strategies, Same Document

[Back to Diagrams](/diagrams)Diagram Series

# Four Chunking Strategies, Same Document

Four Chunking Strategies, Same Document

![Four chunking strategies applied to the same document: fixed-size cuts mid-sentence, semantic splits on topic shifts, hierarchical nests children under retrievable parents, document-aware respects headings, code blocks, and tables.](/diagrams/chunking-strategies.webp)Full screen

Four Chunking Strategies, Same Document

Chunking is the highest impact, lowest visibility decision in a retrieval pipeline.

How you split a document decides what your search can ever find. Take one document, chunk it four different ways, and you get four different search experiences.

Fixed-size, say 512 tokens, is simple and predictable. It also slices through the middle of sentences, cuts code blocks in half, and breaks tables apart. Your embedding ends up holding half a thought.

Semantic chunking splits on topic shifts, detected by embedding similarity. Every chunk is coherent and captures one complete idea. The sizes swing hard, though. Some come out at 100 tokens, others at 2,000.

Hierarchical chunking nests small child chunks inside large parent chunks. You search the children for precision and pull the parent for context, so you get fine-grained matching without losing the surrounding meaning. The price is a more complex index.

Document-aware chunking splits on headings and keeps code blocks and tables intact. The chunks follow the document's own structure. A table stays a table, a function stays whole. It just needs format-specific parsing.

Rough guide: fixed-size for homogeneous text or a fast prototype, semantic for long-form articles and papers, hierarchical for Q&A and RAG where context carries the answer, document-aware for technical docs full of code and tables.

Most RAG failures aren't model failures. They're chunking failures.

## Where this diagram appears

*   [Guide: multimodal chunking strategies →](/guides/multimodal-chunking-strategies)

Run this on your own data

Mixpeek turns video, images, audio, and documents in your object storage into searchable, timestamped results through one API.

[Search your own data](https://studio.mixpeek.com/namespaces/create?mode=managed&utm_source=homepage&utm_medium=diagram_detail&utm_campaign=mvs_onramp)

## Related diagrams

[

![How you split a document decides what you can find: fixed-size chunks cut mid-sentence and strand the answer across two pieces, while splitting on meaning keeps each chunk a complete thought. Chunk too small and you lose the context that makes an answer usable; chunk too large and the relevant sentence is diluted by everything around it.](/diagrams/foundations/chunking.webp)

How you split decides what you find



](/diagrams/chunking)[

![Retrieval-augmented generation (RAG): a user asks a question, search retrieves the few most relevant passages from your indexed data, and the model answers from those passages placed in its prompt. The quality ceiling is retrieval, not the model: most hallucinations are retrieval failures, because the model can only answer with what it was fed.](/diagrams/foundations/rag.webp)

The model answers with what you feed it



](/diagrams/rag)[

![Documents fill empty buckets with a mean; queries sum and leave empty buckets zero: the asymmetry is what makes the FDE dot product approximate Chamfer / MaxSim.](/diagrams/muvera-query-doc-asymmetry.webp)

MUVERA: Why Query and Document Are Encoded Asymmetrically



](/diagrams/muvera-query-doc-asymmetry)