What Figma is for slides
Figma is not a Google Slides template mall. Teams use it when a “theme” is a system: color variables, type styles, and components that also show up in the product UI. You can build a slide kit here, then present in Figma or rebuild in Canva or native Slides.
Figma Slides launched around 2024. It lets design teams present from the same file they already use for UI kits. Components and variables keep a launch deck aligned with the product. That is a different promise from Slidesgo, which hands you a copy-to-Drive theme, and from Canva, which hands you a Brand Kit and a template mall.
Who it is for
- Product and design teams whose deck must match the design system
- Brand teams building a reusable slide kit (cover, quote, two-column, metric) as components
- Anyone presenting a designed artifact—launch, rebrand, research playback—to an audience that will not edit the file
It is not for weekly Drive editing. If five people must update numbers in Google Slides on Friday, do not make Figma the source of truth. Start at the Google Slides hub.
Figma Slides, components, and variables
The useful mental model is “slides as UI.” A title is a component. A metric tile is a component. Spacing comes from the same variables as the product. When the brand navy changes, the deck can follow. That is why Figma beats a one-off Canva export for design orgs, and why it loses to Slides for school and ops teams.
Present in Figma when you can. That path keeps components live. Exporting is how fidelity dies.
PPTX import: what actually survives
PPTX import exists. Treat it as a rough transfer, not a migration:
- Fonts often go to Inter
- Tables, videos, diagrams, and animations are frequently dropped
- Complex masters do not become a clean Figma variable system
If the file started in PowerPoint, keep it there unless you are willing to rebuild. If it started in Slides, keep it in Slides. Import into Figma only when you are redesigning the deck as an artifact.
When to skip Figma for decks
Skip Figma when the job is a themed talk tonight. That is Slidesgo or SlidesCarnival. Skip it when Brand Kit marketing is the need—Canva is faster. Skip it when the workplace standard is PPTX and Slide Master—Microsoft Create plus desktop PowerPoint. Skip it when you only needed a palette—Coolors or Realtime Colors.
Also skip Figma if nobody on the team lives in the file daily. A slide kit that only one designer can update is a bottleneck, not a system.
Figma vs other slides tools
| Tool | Best first use |
|---|---|
| Figma / Figma Slides | Design-system decks, present in Figma |
| Canva | Brand Kit, marketing/event templates, export |
| Google Slides | Drive co-editing + library themes |
| PowerPoint | Workplace PPTX, strongest Slide Master |
| Beautiful.ai | Auto-reflow layouts, paid after trial |
| Gamma | Prompt-to-deck, web-native cards |
More context: best slides tools and Canva vs Google Slides.
Practical path if you still need a Slides or PPT file
- Design the kit in Figma (covers, type ramp, metric tiles).
- Present from Figma Slides when the audience can take a link.
- If Office or Drive is mandatory, rebuild the master in PowerPoint or Slides using the hex and type decisions—not a pixel-perfect export of every frame.
- For a grab-and-go theme instead of a rebuild, start from Slidesgo and recolor with Theme → Colors.
Do not promise stakeholders “we will just import the PPTX.” Fonts to Inter and dropped tables are the usual result.
When Figma Slides is the honest present path
The audience is a design critique, a launch review, or a brand playback. People will not edit the file. They will comment in Figma or sit in the room. Components stay live. Variables still match the product. That is the honest path.
The dishonest path is “we will import the sales PPTX and present tomorrow.” Fonts go to Inter. Tables vanish. Videos and diagrams drop. You spend the night rebuilding tiles that already existed as components. If sales owns the file, leave it in PowerPoint. If the class owns the file, leave it in Google Slides.
Build a small kit, not a 80-frame museum: cover, section, two-column, quote, metric, closing. Bind them to variables. Document which components are allowed. A kit one designer can update is a bottleneck; a kit the design org understands is a system.
Common mistakes
Using Figma because it is where you already work, even though Friday’s editors only have Slides. Treating PPTX import as a migration. Exporting frames as images into Slides and calling it a theme—those images will not reflow. Skipping Canva when the job is a Brand Kit marketing mall, not a component library. Generating a new palette in Coolors instead of using existing variables.
Present in Figma when you can. Rebuild a real master only when Office or Drive is mandatory—and rebuild from tokens, not from a hopeful import.