To handle Chunking, confirm the input/format and output requirements, then follow the steps and verify the result. Chunk by semantics/headings and cap tokens per chunk.
Why it matters
Defining the output first avoids finishing before discovering the format/size/quality is wrong.
Overlap improves recall but costs more.
Step by step
- Confirm the model context and output budget.
- Paste the prompt/document and estimate tokens/usage.
- Above 80-90%, split, summarize or retrieve.
- Count system prompts/tool schemas too.
- Verify billing/hard limits with the official tokenizer.
Common mistakes
- Treating character count as token count.
- Ignoring output/system prompt usage.
- Assuming all models use the same tokenizer.
- Stuffing a long document instead of retrieving/summarizing.
Checklist
- Model context confirmed.
- Output budget reserved.
- System/tool prompts counted.
- Long text retrieved/split.
- Critical cases checked with the official tokenizer.
Key facts
- Overlap improves recall but costs more.
- Split code by function/file.
FAQ
How do I handle Chunking?
To handle Chunking, confirm the input/format and output requirements, then follow the steps and verify the result. Chunk by semantics/headings and cap tokens per chunk.
How long does it take?
Usually 1-3 minutes; for intermittent issues, run 30 seconds and retest elsewhere.
Is data uploaded?
Runs locally and does not upload video/audio; extensions may still read the page.
Source: RAG chunking