Retrieval

Chunking Visualised

Play a short animation of one sentence split into readable text chunks. The same words separate in 3D, showing why each cut changes the context a retrieval system can see.

Ready · 1 / 4

One sentence, all its context

Read the sentence. Press Play to split these words into three smaller pieces.

Northbank approves UK travel,

pays invoices within thirty days,

and keeps receipts for six years.

One short UK business example. The cut points are chosen for this demonstration.

Press Play to see one sentence become three chunks. Two cut lines appear, then the original text pieces lift away from the page. Every word, space and punctuation mark stays in its source order. The cut points are handpicked for this small demonstration.

Chunking divides source material into pieces that can be indexed and retrieved separately. A useful chunk keeps enough context to stand on its own. Here, the later pieces no longer name Northbank. This makes a simple limitation visible: preserving every character does not guarantee that each separate piece makes sense.

Real document pipelines can use sentence, paragraph, fixed-size or semantic boundaries. Larger chunks, overlap or added source context can help preserve relationships across a cut. The appropriate choice depends on the material and the questions readers ask. This animation illustrates the mechanism; it does not run an embedding model or choose an optimal production chunk size.

Sources and model assumptions

Follow the original mechanism behind this explainer. The interactive examples identify their toy data and simplifying assumptions above.

Put it to work

Related terms

More visualisations

Building with language models?

These explainers come out of the work. If you want the same thinking applied to your own system, that is what I do.

See how I can help