Most people who ask ChatGPT for a deck accept whatever look it invents, then spend an hour dragging logos, fixing fonts and recolouring charts. What most of them do not know is that ChatGPT Slides can take an example deck as a style reference. Hand it last quarter's approved deck and it will try to copy the layout, not just the topic.
OpenAI added Slides to its release notes on 16 October 2026. This guide shows you how to brief it with a reference deck, which editing control to use for which fix, and the export and sharing traps worth knowing before a client sees anything.
What is ChatGPT Slides and who can use it?
ChatGPT Slides is a presentation editor inside ChatGPT Space. You create a deck from a conversation, attached files or an outline, edit it directly or by asking ChatGPT, collaborate with teammates in real time, then present it or export it. It is rolling out to Pro, Business and Enterprise plans with Space access.
According to OpenAI's help article on Slides, there are two ways to start. You can ask for a deck in Work, describing the topic, audience and material, or open Space and choose Create, then Slide, with a blank slide or a template.
Access details matter before you plan a workflow around it:
--- Plans: Pro, Business and Enterprise with Space access. Free, Go and Plus are not listed.
--- Rollout: gradual, so it may not appear on your account yet.
--- Web: full creation, editing, sharing and export to PowerPoint, PDF or Google Slides.
--- Windows desktop: without a component called MXC, the app produces plain .pptx files instead of collaborative Slides. Windows 10 does not support it, so use the web version.
If you are on Plus, OpenAI's separate ChatGPT for PowerPoint add-in still covers more plans, as Powerdrill's 19 October explainer notes.
Why does an example deck change ChatGPT's slide output?
An example deck gives ChatGPT a concrete visual target. Without one, it guesses a generic layout and you rebuild the look by hand. With one, it can copy your title style, slide structure and chart treatment. OpenAI says to share an example deck "to guide the style and layout", though matching still needs a manual check.
Think of it as few-shot prompting for design. A text prompt such as "make it look professional" is ambiguous. A real deck shows the model what professional means for your team: where the headline sits, how dense a slide is allowed to be, how numbers are highlighted.
The help article gives its own example request: create a six-slide project update from notes, covering progress, risks and next steps, using "my project update template" to guide style and layout. Notice what it includes. A slide count, named sections and a named reference.
Choose the reference carefully. The best example is a recent deck your manager or client already approved, with the same audience as the new one. A beautiful deck made for a different audience teaches the model the wrong density and tone.
There is also a reuse path. OpenAI says you can build your own templates with template-creator and share them with a team through team Plugins. If you produce the same deck every month, saving a template once beats attaching a reference file every time.
The honest caveat: OpenAI's own guidance warns that template matching and advanced edits to charts, shapes and formatting may still need manual refinement. Treat the reference deck as a strong hint, not a guarantee.
How do you write a reference-deck brief for ChatGPT Slides?
A reference-deck brief is a short request with six labelled parts: the reference deck, what to keep from it, what must change, the sources, how to handle gaps and a final check. Labels stop ChatGPT from mixing old content from the reference into the new deck, which is the most common failure.
That mixing problem is real. If you attach last quarter's deck as a style guide and do not say "style only", the model may reuse last quarter's numbers. The KEEP and CHANGE lines prevent it.
Try this prompt:
Create an 8-slide monthly marketing update in Space.
REFERENCE: The attached deck "Sept-update.pptx". Use it for style and layout only. Do not reuse any of its text, numbers or charts.
KEEP: Title slide layout, one headline per slide written as a full sentence, maximum 4 bullets per slide, charts with a single highlighted bar.
CHANGE: All content comes from October. Replace the September agenda with: results, campaign highlights, what did not work, budget, next month.
SOURCES: Use only "Oct-metrics.xlsx" and "campaign-notes.docx". Every number on a slide must come from these files.
GAPS: If a number or fact is missing, write [MISSING: what you need] on the slide instead of estimating.
CHECK: After the deck is built, list every number you used with its source file and cell or paragraph, then list any slide where you could not match the reference layout.
The CHECK line is the part people skip. It turns a finished-looking deck into something you can verify in five minutes, because you only need to trace the list rather than reread every slide.
The [MISSING] marker does the same job for gaps. A visible placeholder is safer than a confident invented figure sitting in a polished chart.
Should you use Request edits, the prompt bar or manual edits?
Use manual edits for small fixes such as a typo or a colour. Use Request edits when one element needs reworking, like a single chart or slide. Use the prompt bar for changes across the whole deck, such as shortening every slide. Matching the control to the size of the change avoids side effects elsewhere.
OpenAI's help article lists text, images, shapes, tables and charts as directly editable. To involve ChatGPT on one element, select it, choose Request edits and describe the change. For deck-wide changes, type into the prompt bar.
A practical rule of thumb:
--- Under 10 seconds by hand: do it yourself. Asking the model costs more time and can disturb nearby elements.
--- One element, real thinking needed: Request edits. Example: "Rebuild this chart from the October column of Oct-metrics.xlsx and keep the reference colour for the highlighted bar."
--- Pattern across slides: prompt bar. Example: "Cut every slide to 3 bullets maximum without removing any number."
Collaboration follows the same logic. In shared comments you can @mention a teammate, or @mention ChatGPT to have it make a change. That keeps the request next to the slide it concerns, which is easier to audit than a long chat thread.
What breaks when you export or share a ChatGPT Slides deck?
Exports can shift fonts and layouts, linked files keep their own permissions, and there is no comment-only role at launch. OpenAI explicitly tells users to open every exported presentation and check content and formatting. Plan a short review before anything leaves your team, especially decks going to clients.
The gotchas worth writing on a sticky note:
--- Fonts differ by surface. On the web, the font picker only shows fonts available in your browser. The desktop app can use fonts installed on your computer. A deck built on desktop can look different on a colleague's web session.
--- No comment-only access. Sharing is view or edit. A manager who only needs to leave notes gets full edit rights, or you send a PDF instead. DigitBin's 18 October review flags this as the gap most likely to bite client work.
--- Linked files keep their own permissions. A teammate who can open the deck may not be able to open the spreadsheet behind it.
--- Outside content can carry instructions. OpenAI's admin guidance warns that pages, files and tool results may contain prompt injections. Be careful with decks built from web pages or third-party files.
--- Unknown limits. OpenAI has not published slide count, file size or export limits, so test with a real deck before relying on it for a large one.
How can you test ChatGPT Slides on a real deck in 20 minutes?
Pick a deck you produce regularly and already know well, such as a monthly update. Brief ChatGPT with last month's deck as the reference and this month's files as sources, verify the number list, then export once and compare. Count the fixes you made by hand. That number tells you whether next month should start here.
--- Minutes 0 to 5: gather last month's approved deck and this month's source files. Adjust the brief above to your sections.
--- Minutes 5 to 10: run the brief in Work and open the result in Space.
--- Minutes 10 to 15: trace three numbers from the CHECK list back to the source. Search the deck for [MISSING].
--- Minutes 15 to 20: export to PowerPoint or Google Slides and scan for moved text boxes, swapped fonts and broken charts.
If you also build decks in Claude, the same discipline applies there. Our Claude Slides deck guide uses an evidence-first brief that pairs well with the reference-deck approach. Either way, the deck is only as good as the rules you give it. We understand AI. We understand you better. With UD by your side, AI doesn't feel cold.
Reviewed by the UD AI team. Feature details reflect OpenAI's Help Center and 16 October 2026 release notes, plus reporting by Powerdrill (19 October) and DigitBin (18 October). Plan access and rollout may change.
See how your AI skills rank against your peers
Briefing AI with references, sources and checks is a skill you can measure. Take UD's free AI Rank test to see where your team stands, and when you are ready to build workflows like this into daily work, we'll walk you through every step, from tool setup to workflow design and deployment.