partition
Subtype: vlm
For more information about how the various partitioning strategies balance output quality, speed, and cost, see Partitioning.
Usage guidance
Use the Auto strategy when source documents have unknown or varied characteristics; for example, documents containing a mix of forms, tables, scanned pages, and extractable text. Each page is independently evaluated and routed to VLM, High Res, or Fast partitioning. Pages with tables are routed to High Res to support downstream enrichment nodes such as Table to HTML. For uniformly image-heavy or visually complex documents, use the VLM strategy instead.Settings
VLM provider to use if Auto routing selects the VLM strategy. Allowed values:
anthropic, auto, bedrock, openai, vertexai. Default: anthropic.If specified, overrides the default API key used for VLM provider calls. Default: none (uses Unstructured’s internal default).
VLM model to use if Auto routing selects the VLM strategy. Default:
claude-sonnet-4-20250514.For a full list of the models available in Unstructured, see Available models.Format of the partitioner response. Allowed values:
text/html, application/json. Default: text/html.If
true, applies Beautiful Soup’s prettify method to any HTML generated by the VLM partitioner, adding indentation for readability. Default: true.If
true, assigns UUIDs to element IDs, guaranteeing uniqueness (useful when used as database primary keys). If false, assigns a SHA-256 hash of the element’s text as its ID. Default: true.Must be
true to enable dynamic routing of pages to Fast, High Res, or VLM as needed for optimal performance and cost.Must be
true to allow routing of pages to Fast partitioning for better performance and cost savings.
