Gemini now edits PDFs, spreadsheets and slides in chat—but what really works?

Google had already announced file generation in April 2026. The new aspect of its October 29 announcement is inline previewing and editing: people can expand a document into a full-screen view, change text themselves or highlight a passage for Gemini to refine. Google explicitly distinguishes platforms. PDF previewing and editing work on web and mobile; Docs, Sheets, slide decks, Markdown, TXT and code are currently web-only. That device split matters much more than a broad promise that Gemini can now edit every kind of file everywhere.

The matrix below pairs each capability described by Google with a separate human verification checkpoint. Its last column is our editorial recommendation, not a vendor guarantee. Good-looking spreadsheets may contain incorrect formulas; polished presentations may repeat unsupported claims; and a PDF that looks fine in chat may be wrong after export. This is why editing support and trustworthy output should be evaluated separately.

Start with a non-sensitive sample and a narrowly defined request. Highlight specific sections and ask for targeted corrections rather than rewriting everything. Next, open the exported file in the application where it will actually be used and inspect calculations, references, formatting and differences from the original. Only then approve the final sharing or publication step. This is AgentenCode's recommended process, not a real-world product test that we performed. Generated code should be tested in an isolated environment.

Google's Workspace update lists personal Google accounts, Workspace Individual and Workspace customers. It says there is no separate admin control for this particular feature, while offering broader controls over access to the Gemini app. That does not establish unrestricted quotas or identical capabilities for every organization. Neither announcement establishes a new data-retention guarantee or permission to upload confidential customer records; organizations still need to apply their own policies.

Editing a document inside a conversation moves assistants beyond plain-text drafting, but does not establish autonomous authority to send a message, publish a document or operate external services. Capability and permission remain separate. Our analysis of Gemini Computer Use covers that different class of tool-driven browser action. A responsible workflow should preserve review and approval steps around both.

1. Pilot: Try a small, non-sensitive PDF or table and request one limited change.
2. Verify: Inspect the exported file, formulas, citations and layout outside Gemini.
3. Approve: Apply normal data-classification and sharing permissions before use.

There is no independent evidence here that the editor reduces errors or guarantees productivity gains. High-stakes content still needs qualified review.