How to Use Claude for Google Slides: Draft, Edit, Check

You can use Claude for Google Slides through its Google Workspace sidebar, its Google Slides connector, or a presentation exported for transfer. Choose the route your account supports, supply a clear presentation brief and approved sources, then review the deck in Google Slides before presenting.

fenbs can preserve the audience, source list, and revision decisions when the deck moves between Claude, Google Slides, and reviewers. Keep the presentation itself in the tool where you will deliver it.

How do you prepare the first draft?

1. Write the audience, the decision you want them to make, the presentation length, and the final delivery tool.
2. Provide approved notes, evidence, and the existing template. Label estimates and missing information before asking for slides.
3. Ask for an outline with one main point per slide, proposed evidence, and speaker notes. Review the story before generating layouts.
4. Choose an available direct editing or file transfer route. Request editable slides if reviewers need to change them.
5. Open the finished result in Google Slides and check claims, charts, layout, speaker notes, and audience access.

For example, a studio reporting on a website project might need a decision about launch readiness. Its deck should explain what was completed, what was checked, and which issue still blocks release. A general company introduction would answer a different question, even if it used the same brand template.

If you are new to the assistant, what Claude is provides the basics. The steps below focus on creating and revising a Google Slides presentation.

Which editing or transfer route should you choose?

Anthropic documents a Google Workspace sidebar↗ (opens in a new tab) that edits the open Slides file. Separately, its Google Workspace connectors↗ (opens in a new tab) can create and edit Google files from Claude. Check current availability, account permissions, and administrator settings in those guides.

A Drive connection and a Slides editing connection have different jobs. Use the documented route for the action you need, then confirm what Claude actually did. A link in an answer is not proof that it created or changed the intended presentation.

How do you work inside an existing Slides deck?

Follow Anthropic's setup overview↗ (opens in a new tab): install the approved Marketplace add-on, open the native Slides file, and choose Extensions, then Claude, then Open Claude. Sign in with your Claude account. If installation is blocked, the Workspace administrator needs to resolve that restriction.

Select the slides you want changed and give a narrow request: shorten the title, split one crowded slide, or align the terminology with the approved requirements. Keep the sidebar open while it works and use the review-before-editing mode while establishing the workflow.

Ask for a read-only critique before a broad revision. For example: identify slides that repeat a point, cite where a number appears, and propose changes without applying them. Then approve a manageable set of edits and inspect the result.

The sidebar guide explains that edits appear under your name in Google version history. Preserve a review copy before major changes. Document work has separate constraints, covered in whether Claude can edit Google Docs.

How do you move a deck from Claude into Google Slides?

Ask explicitly for Google Slides when using the relevant connector. When creating a presentation artifact, inspect its export options; the current Artifacts guide↗ (opens in a new tab) documents editable Google Slides export for decks. Confirm the resulting file opens in the correct Google account.

For a PowerPoint handoff, download the presentation and open it through Drive using Google Slides. Google explains opening Office presentations in its PowerPoint-to-Slides guide↗ (opens in a new tab). Convert the file to native Google Slides before using a sidebar extension that requires the native format.

Do not assume conversion preserves every detail. Compare titles, line breaks, chart labels, image crops, and speaker notes with the reviewed version. For a small deck, copying approved text into your established Slides template may require less cleanup than transferring elaborate generated layouts.

If visual composition is the main challenge, the Claude Design guide covers that related workflow. Keep presentation requirements in fenbs when several output routes need to follow the same approved brief.

What prompt keeps the deck tied to the evidence?

Audience: project owner deciding whether to approve launch.
Delivery: Google Slides; editable text and speaker notes.
Use only the supplied project report and test summary.
Propose an outline before making slides.
Each slide needs one point and a source reference.
Separate completed work, unchecked work, and open decisions.
Keep estimates labeled and do not invent results.
End with the decision needed and the next action.

For each factual slide, compare the claim with its source. A source about completed development does not establish that acceptance testing passed. Replace unsupported claims with a clearly labeled question or remove them until someone supplies evidence.

Check chart behavior separately. The sidebar documentation says charts Claude creates are images rather than linked spreadsheet charts. If the underlying figures change, arrange an explicit update and review; do not expect the slide to become current by itself.

Read the deck in presentation mode. A useful title states the point, a visual supports it, and notes hold detail the audience does not need on screen. Ask a colleague unfamiliar with the project to explain the requested decision after viewing the final slide.

How to do this with fenbs

1. Create a free account and add a project for the presentation, with its audience and required decision.
2. Keep the deck and approved source references in Links and listings. Write the current presentation brief in AI context notes.
3. Record reviewer decisions in Decisions and rules, and create tasks for factual corrections and other requested changes.
4. Connect a supported assistant through Integrations. Ask it to read the context before drafting and save progress, including the latest deck link and next review, before stopping.

fenbs does not edit Google Slides or transfer presentations into Google Drive. For a short deck made in one sitting, your source document and a review copy may be sufficient. Use fenbs when presentation requirements and decisions need to survive multiple reviewers or assistant sessions.

Keep one current deck reference and mark what remains unverified. Find more practical assistant workflows in AI at work.