Snowflake turns document libraries into rows of AI summaries—but not structured facts

Snowflake has put a multimodal summarizer behind a single SQL function. The September 14 public preview expands Cortex AI_SUMMARIZE to accept text or a staged file reference, including images and documents, and return a text summary. Snowflake says the managed function identifies themes, facts and relationships without a custom prompt, model choice or separate document-processing pipeline (release note).

The important part is the table boundary

The practical change is not merely that Snowflake can summarize one PDF. Its reference documentation shows users creating a table of file objects from a stage directory and then running SELECT AI_SUMMARIZE(doc) FROM doc_files to summarize every file as a row-producing SQL operation (function reference). That makes a document library composable with ordinary warehouse metadata: file name, content type, size, stage and modification time can be queried beside each generated summary (function reference).

This narrows an integration gap for data teams that already land contracts, reports or diagrams in Snowflake. They no longer need to select a model or build their own parsing and chunking pipeline for the summarization step, according to the release note (release note).

A summary is still not an extracted record

AI_SUMMARIZE returns text, not a typed set of fields. The docs also direct users to AI_AGG when summarizing across rows rather than concatenating rows before calling the function (function reference). Teams that need contract clauses, invoice amounts or other auditable fields should therefore treat this as a summarization stage, not a replacement for structured extraction and validation.

The operating boundaries matter. Inputs of 110 characters or fewer are returned unchanged, but processed tokens are still billed; row-level error details are optional; and Snowflake says multilingual quality can vary (function reference). File support also differs by region. The documented limits range from 4.5 MB and 100 pages for several document formats to 37.5 MB and 1,000 pages for PDF, TXT and Markdown in selected deployments, while Azure Global lists no document support in the current table (function reference).

For practitioners, the sensible rollout is a bounded one: start with one document class, retain the source-file metadata beside every summary, enable row-level error details, and evaluate factual retention before summaries feed search or agents. Snowflake has simplified the execution surface. It has not removed the need to test the output.