Introduction
Google announced in-chat file editing on October 29, 2026. The update brings generation, preview, direct typing and targeted Gemini revisions into the same conversation. File generation had already been announced in April; the October news extends what a person can do with the resulting file.
What changed
Google's October 29 Workspace post distinguishes support by format and platform:
- PDFs: preview and editing on web and mobile.
- Documents and spreadsheets: supported on the web.
- Presentations: supported on the web.
- Markdown, TXT and code files: supported on the web.
The post also describes routes into Google Docs, Sheets and Slides, plus downloads for supported outputs. That does not establish that every export preserves every layout or formula. The practical distinction is between editing the draft in Gemini and inspecting the actual artifact another person receives.
A useful place to try it
Use a change record for a single revision rather than asking for a general polish. Consider a fictional one-page website brief with three agreed pages: Home, Services and Contact. The approved notes say photographs are still outstanding and no opening date has been agreed.
Start with this instruction: prepare the brief using those three pages; retain the outstanding photography item and leave the opening date unresolved. The first review checks facts and scope before tone. If the draft adds a booking page or a launch date, record that as an unwanted change even if the writing sounds plausible.
For the next pass, select only the introduction and ask for a shorter version. Keep a change record with four entries:
- Requested change: shorten the introduction while retaining the audience and primary contact action.
- Protected facts: three agreed pages, photographs outstanding, opening date undecided.
- Allowed changes: wording and paragraph length within the selected introduction.
- Acceptance check: compare the revised section and the protected facts against the starting draft.
The record makes two kinds of failure visible. A revision can fail by changing protected scope, or by shortening the text so far that the audience disappears. A reader can reject either result without debating whether the new prose feels more polished.
Next, export the document in the format the recipient needs. Open that exported copy and check headings, links, page breaks and the unresolved items. For a spreadsheet, add checks for formulas and displayed values; a good-looking preview does not prove the calculation is correct. Retain the reviewed export beside the change record so the send decision refers to a specific file.
Keep this as a proposed exercise until the actual export has been checked on the account and formats you intend to use.
Availability and limits
The October 29 Workspace announcement lists availability for Workspace customers, Workspace Individual subscribers and personal Google accounts with Gemini app access. It reports the feature as available then; account eligibility and administrator restrictions still need checking for a particular user.
The useful outcome is a traceable correction that survives export. Keep the original notes, the requested change and the reviewed file together, rather than treating the chat's latest response as the final deliverable.
