Google's Gemini API adds Office and OpenDocument file input with content slicing
The Gemini API now takes Word, PowerPoint, Excel and OpenDocument files directly and can process only selected parts of documents, spreadsheets, videos and audio.
Google's Gemini API now accepts Microsoft Word, PowerPoint and Excel files, plus OpenDocument files, passed directly to the API. A Gemini API changelog entry dated November 18, 2026, reports the change. The same update lets developers slice documents, spreadsheets, videos and audio inside user prompts and function responses. A request can target part of a file instead of the whole thing.
Slicing options are specific. Developers can select page ranges in a document, worksheet tabs or cell ranges in a spreadsheet, and time intervals in video or audio. The changelog also lists content layers, such as page images, extracted text, formulas or video transcripts. Google says this lets developers process and pay for only the content they need. The changelog does not explain how slices are written into a request or how they are billed. It refers readers to its document, video and audio understanding documentation for those details.
What changed
The Gemini API now accepts Microsoft Word, PowerPoint and Excel files and OpenDocument files directly, and can process only selected parts of documents, spreadsheets, videos and audio.
Type: New capability · Takes effect: Wednesday, November 18, 2026 · Applies to: Gemini API, Microsoft Word, PowerPoint, Excel, OpenDocument
Why it matters
Teams processing office files with Gemini can send native Word, PowerPoint and Excel documents without converting them first. They can also pay only for the sections they select.
What you can do
Developers who handle Office or OpenDocument files should test whether slicing by page, sheet or cell range lowers their processing costs.
How the story developed
Google's changelog adds that the slicing can target worksheet tabs, cell ranges, time intervals and content layers such as formulas or video transcripts, and links to the relevant documentation.
Original source
Where we saw it
Gemini API changelog
AI wrote this summary from the sources listed, and nobody reviewed it individually before publication. Check the original source before you rely on it. How it works