Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

Gemini API now takes Office files and returns files

Written November 6, 2026

The Gemini API accepts legacy Office and ODF inputs and returns multimodal function-response files. What builders can send now — and its limits.

What changed on November 5

The November 5, 2026 entry in the Google AI Studio changelog adds two things: new file types the Gemini API accepts as input, and new file types tools can return in function responses.

On the input side, the API now accepts PowerPoint 97-2003 (PPT), OpenDocument Presentation (ODP), and OpenDocument Spreadsheet (ODS) files, and adds page-image processing for Word 97-2003 (DOC) files. DOC, PPT, and ODP files are rendered as page images. For ODS files, the model receives the data and formulas from the first sheet. Processing for DOCX, DOTX, ODT, PPTX, XLSX, and XLS files is unchanged.

On the function-response side, tools can now return Office and OpenDocument files, audio, and video to the model. In the GenerateContent API, function response parts now accept audio, video, and Office and OpenDocument files, in addition to images, PDFs, and plain text. They also accept fileData, so tools can return a Files API URI instead of inline bytes. displayName is now available on both inlineData and fileData, and video parts accept mediaProcessing (STATIC or AGENTIC). In the Interactions API, function_result steps now accept document, audio, and video content blocks, in addition to text and image, by inline data or URI.

What builders can send now

The limits

What to do with it

  1. Drop the conversion step for legacy files. If your pipeline converts PPT or DOC to something else before sending it to Gemini, try sending the original. Keep the conversion as a fallback until you have seen the page-image rendering on your own documents.
  2. Check the first-sheet rule before sending a spreadsheet. Open the ODS file, confirm the data you need is on the first sheet, and move it there if it is not.
  3. Use fileData for tool returns. When a tool returns a file to the model, a Files API URI keeps the response small and avoids stuffing bytes into the function response. Note that video blocks in the Interactions API are available in v1beta and v1alpha.
  4. Remember the December 1 date on the same changelog. Gemini 2.5 Pro and Flash retire on December 1, with API calls rerouted to their replacements. See Gemini 2.5 Pro and Flash retire December 1, and the full list of upcoming dates in agent change deadlines.

Related playbooks

Sources

Back to: Coding playbooks hub · Also: Gemini 2.5 Pro and Flash retire December 1 · Model specs: context, tools, and cutoffs in one table · Agent change deadlines: retirements and shutdowns