Gemini now creates ready-to-use files inside chat

Google has turned Gemini chat into a file generator.

Google said on April 29, 2026 that Gemini can now create downloadable and shareable files directly inside a chat. The supported outputs include Google Docs, Sheets and Slides, PDF, Microsoft Word and Excel, CSV, LaTeX, TXT, RTF and Markdown. Google says the feature is available globally to Gemini users.

The important point for executives is not that a chatbot can export a document. The important point is that the workflow is moving from “AI as adviser” to “AI as producer of business files.” Budget proposals, project plans, meeting notes, governance documents and spreadsheets can now be created in one conversation and then downloaded or moved into Drive.

Fact: Google Workspace Updates describes the same capability for Workspace customers and says Gemini currently generates one file per prompt. Google also says there is no dedicated admin control for this specific feature; control is handled through access to the Gemini app. That is a practical CIO and CISO issue, not a helpdesk detail.

Assessment: This can improve productivity for knowledge workers, but it also makes information governance harder. When an AI assistant can write and package files in Office and Google formats, the enterprise needs to know which data was used in the prompt, where the file is stored, who owns it, and how the content is checked before it is shared externally.

For Norwegian and European organisations, three actions follow. First, update AI policy from “what employees may ask” to “which files AI may create and where they may be stored.” Second, test DLP, logging and classification on Gemini-generated files, not only on traditional documents. Third, set a simple quality rule for numbers, contract language and customer data. AI-generated spreadsheets and PDFs should be treated as drafts until a responsible human has validated them.

This is a small product update with real operating consequences. CIOs should not block it by reflex, but they should not let it enter document workflows as an invisible change either.