After a document is ingested, Vertex AI RAG Engine runs a set of transformations to
prepare the data for indexing. You can control your use cases using the
following parameters: A smaller chunk size means the embeddings are more precise. A larger chunk size
means that the embeddings might be more general but might miss specific details. For example, if you convert 1,000 words into an embedding array that was meant
for 200 words, you might lose details. The embedding capacity is fixed for each
chunk. A large chunk of text may not fit into a small-window model.
Parameter
Description
chunk_size
When documents are ingested into an index, they're split into chunks. The
chunk_size
parameter (in tokens) specifies the size of the chunk. The default chunk size is 1,024 tokens.
chunk_overlap
By default, documents are split into chunks with a certain amount of overlap to improve relevance and retrieval quality. The default chunk overlap is 256 tokens.
What's next
Fine-tune RAG transformations
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-21 UTC.