Why does Deck exist?
Designers make great slides in design tools, then lose hours rebuilding them in PowerPoint because clients need an editable file. Exporting images loses editability, and rebuilding by hand loses fidelity. Deck removes that step.
How does it work?
- Install Deck from Figma Community.
- Select the frames you want as slides.
- Export. Each frame becomes an editable PowerPoint slide with real text and shapes.
The free tier converts 50 slides a month; Pro is a one-time $89.
How it grew
- Dec 2017First version for Sketch, built with almost no coding experience
- 2020Deck 1.0 and the Figma plugin
- 2025Relaunched with a paid tier after five free years
- 2026163k users on Figma Community, 1M+ presentations
What eight years taught me
Deck is how I learned to code. I started it in December 2017 with almost no coding experience, and keeping it working since has taught me more than any course.
The first lesson was file formats. A PowerPoint file is a ZIP of XML parts, and every shape, text box and image has to be written exactly right before PowerPoint will open it. Getting that right, slide after slide, showed me how a file format is really put together.
The second was how design tools work underneath. To convert a design, Deck has to read it the way the tool stores it, first in Sketch and then in Figma: a tree of layers with their own layout, styles and constraints, exposed through the plugin API. Turning that model into PowerPoint's taught me how interface software is built, not just how to use it.
Both lessons ended up as the groundwork for .gui. Designing an open file format for interfaces meant knowing how design tools structure a screen and what their APIs expose, and Deck had already taught me both.
