Skip to content

AI Slide Editing And Chat

A generated slide deck opens in the Slide Deck Editor for review, layer editing, visual replacement, and conversational revision. Decks are self-contained HTML and can be exported to PowerPoint (.pptx) or PDF.

The Slide Deck Editor supports:

  • Paging through and reviewing every slide in the generated deck.
  • Editing the title, body, and other text layers on the active slide.
  • Replacing the active slide visual.
  • Revising the deck conversationally with chat.
  • Exporting the deck to PowerPoint or PDF.

When you upload a local image into a slide, the editor defaults that image to Fit instead of forcing it to fill the frame.

This matters for screenshots, diagrams, org charts, and other text-heavy reference images where cropping or aggressive scaling would make the text unreadable.

Use Image Tools to switch between:

  • Fit when you need to preserve the full image and keep embedded text legible.
  • Fill when you want the image to crop to the frame edge-to-edge like a presentation photo.

Describe the change you want and the assistant rewrites the deck for you, re-applying your brand rules so edits stay on-brand.

  1. Open a slide deck artifact.
  2. Open the chat panel.
  3. Describe the change (for example, “tighten the summary slide and add a closing call to action”).
  4. Review the revised deck.
  5. Save.

Because the deck is a single self-contained document, chat edits operate on the whole deck rather than a stored per-slide action log.

If results are not what you expected:

  • Verify source quality first (missing context, inconsistent structure, or conflicting inputs reduce output quality).
  • Re-check selected options and audience/profile settings before re-running.
  • If a job fails repeatedly, wait briefly and retry once; then escalate with the artifact or job context.

Regenerate when the core structure is wrong; use chat when only wording, ordering, or styling needs adjustment.

What is the best way to reduce iteration cycles?

Section titled “What is the best way to reduce iteration cycles?”

Start with clear scope, run smaller batches, and use review checkpoints after each major step.