PPTX ExportFigma to PPTX: a Real .pptx File, Not Pictures in a Wrapper
Plenty of tools hand you a file with a .pptx extension. Far fewer hand you a .pptx whose insides are PowerPoint objects. Here is exactly what gets written into the package.
What your Figma layers become
The converter walks your frame tree and maps each node to the closest native PowerPoint object. Where no honest native mapping exists, the node becomes a crisp PNG — and the reason is written into the report, never swallowed.
| Figma layer | Becomes in the .pptx | What survives |
|---|---|---|
| Text | Native text box | Font family, size, weight, italic, colour, alignment, line spacing, bullet lists, hyperlinks |
| Rectangle, Ellipse | Native shape | Solid fills, linear / radial / diamond gradients, strokes, corner radius, drop shadow |
| Line | Native line | Colour, weight, dash pattern — as long as the stroke is solid |
| Vector of straight segments | Native polyline | Arrows, ticks, dividers and triangle outlines stay vector |
| Polygon / Star, standard point count | Native preset shape | Triangle, diamond, pentagon, hexagon, heptagon, octagon; 4- to 12-point stars |
| Image fill | Embedded picture | Position and crop; optionally recompressed to keep the deck light |
| Frame / Group | Walked through | Children convert individually — the container is not flattened |
| Curved or filled vector, mask, blur, inner shadow, blend mode, conic gradient | High-resolution PNG | Exact appearance, plus a report line naming the node and the reason |
That last row is the honest part. Every exporter has the same limits — OOXML simply has no equivalent for a conic gradient or a Figma mask. The difference is whether the tool tells you. See what the report looks like →
No repair dialog. That is a test, not a promise.
A malformed .pptx is the classic failure of Figma-to-PowerPoint converters: the file downloads, PowerPoint opens it, and you get "PowerPoint found a problem with content." At that moment the deck is worthless to your client.
So file validity is enforced in the build, not hoped for. Every release runs against 16 synthetic fixtures plus a 10-deck stress suite — gradients, rotated text, nested masks, full-bleed photo backgrounds, hundreds of nodes per frame — and each generated file is opened through a real PowerPoint 16.0 COM instance. A repair prompt fails the build.
The package itself is plain Office Open XML: a ZIP holding presentation.xml, one slideN.xml per frame, media parts for images and font parts for embedded typefaces. No macros, no proprietary extensions, nothing that needs our software to read.
Slide geometry, done properly
PowerPoint measures slides in EMU — 914,400 English Metric Units per inch. Figma measures in pixels. Getting that conversion wrong is why exported decks so often arrive with stray white margins.
Frame → slide
Each selected frame becomes one slide, in the order you selected them. The slide canvas follows your frame's aspect ratio, so a 1920×1080 frame fills a 16:9 slide edge to edge.
Pixels → EMU
Every position and size goes through the same coordinate space, so a box that sat 40 px from the left edge in Figma lands at the matching fraction of the slide in PowerPoint.
Need the numbers?
The free slide size calculator converts px ↔ inches ↔ cm ↔ EMU for every common preset, so your frames match the deck before you export.
Frequently asked
Is .pptx the same as .ppt?
No. .ppt is the pre-2007 binary format; .pptx is the modern Office Open XML package (a ZIP of XML parts) that every current version of PowerPoint, Keynote and Google Slides reads. We write .pptx because that XML is what makes shapes and text boxes editable in the first place — the old binary format could not carry native gradients or embedded font parts the same way.
Which PowerPoint versions can open the file?
PowerPoint 2016 and newer on Windows, PowerPoint for Mac, PowerPoint on the web, Microsoft 365, Keynote and Google Slides. The generated package targets the standard OOXML presentation schema — no proprietary extensions, no macros.
Will PowerPoint show the "repair" dialog?
It should not. Every build is run against a fixture suite of 16 synthetic decks plus a 10-deck stress set, opened through a real PowerPoint 16.0 COM instance — a file that triggers the repair prompt fails the build. If you ever hit a repair dialog, mail the deck to ttrttr449@gmail.com and it becomes a fixture.
How big is the exported file?
A typical 5-slide deck lands under 5 MB in about 6 seconds. File-size optimization is on by default: photos are recompressed just enough to keep the deck light without visible loss. Photo-heavy decks get much bigger — a 54-frame deck with full-bleed imagery measured 55.8 MB with optimization on. You can switch optimization off when you want maximum fidelity.
Are the fonts really inside the file?
Yes, when embedding applies. The font bytes are written into the package as font parts — the same mechanism PowerPoint itself uses for "embed fonts in file". Eight popular families ship with the plugin; for anything else you upload a .ttf and it gets embedded too. The font compatibility checker tells you what happens to your specific typeface.
Related: Convert Figma to PPT · How honest conversion works · Step-by-step export guide
Hand off a deck people can actually edit
Editable where possible, embedded where it matters, transparent always — that's the whole promise.