Exporting your slides to Google Slides

Export slides from Figma to Google Slides with a direct, private upload or download a .pptx file for manual import.

Video Tutorial: Export presentations to Google Slides

This video walks through how to export your slide deck presentation designs from Figma to Google Slides using the Pitchdeck plugin.

Video Tutorial: Add Master Slides to PowerPoint exports from Figma

This video walks through how to export a PowerPoint file from Figma (with Master Slides) using the Pitchdeck plugin.

Video Tutorial: Export Figma Slides to Google Slides

This video walks through how to export your deck from Figma Slides to Google Slides using the Pitchdeck plugin

To use this option, click the Export Presentation button in the Pitchdeck toolbar, then choose one of the Google Slides export formats:

  • Google Slides (Direct API Upload) creates a new presentation in your connected Google Drive and opens it in Google Slides. Connect your Google account from the export panel first. Pitchdeck remembers the connection between Figma files, and you can sign out or switch accounts from the same panel.
  • Google Slides (.pptx file) downloads a local .pptx file that you can import manually. This remains available when you do not want to connect Google or need a local copy.

Configure the remaining export settings, then click Upload to Google Slides or Export to begin.

With direct upload, the presentation bytes go from the Pitchdeck plugin to Google Drive. Hypermatic's OAuth service facilitates the connection but does not store or proxy your presentation file.

Animations and videos won't be included in the exported Google Slides .pptx file. Note that any animations or video embeds included in the Pitchdeck plugin won't be included in your PowerPoint export. These are only used for a presentation uploaded to the Pitchdeck web app.

Using Retina @2x Images ​

Enabling the 2x Retina Images toggle option will automatically export any JPG and PNG images at retina (@2x) resolution. This will give you sharper looking images in your presentation, but will also increase the file sizes of any JPG and PNG images.

Compressing images ​

Enabling the Compress Images toggle option will compress any JPG and PNG images used in your presentation.

Downsizing your Figma layer fills ​

Enabling the Downsize Large Figma Image Fills toggle will automatically resize (and lightly compress) any Figma image fills on your layers to their actual layer size. This is useful if you've originally imported high resolution images to your Figma file, but then shrunk the layer dimensions down to be much smaller (with the original large image file still being used).

One common case of this would be adding a large image from Unsplash (or another stock photo site/plugin), the resizing that layer to be used as a much smaller "card" or "avatar" image. This can cause the performance of your Figma file to slow down and potentially crash when exporting these layers via the Pitchdeck export options; so using this feature will help save file size and improve page performance in your Figma file.

Using editable text ​

Enabling the Use Editable Text option will export your .pptx file with text that can be edited in PowerPoint/Keynote/Google Slides. When this option is not enabled, text is included in the exported layer images instead. Note that there may be some minor visual differences between editable text in PowerPoint/Keynote/Google Slides and Figma.

Editable text is placed above all non-text artwork so you can click directly into it in your presentation app. This applies with Smart Auto Layout enabled or disabled. Artwork that overlaps text in Figma will therefore sit behind the editable text in the export.

With Smart Auto Layout disabled, Pitchdeck surfaces nested text, keeps direct-child artwork as separate movable objects, and combines the remaining artwork into a slide background image. Artwork that depends on clipping or blending with neighboring layers stays in the composite background.

Ensure that any custom fonts are installed/replaced. Note that opening the exported .pptx file on a computer which doesn't have the fonts used in Figma installed will cause the text to look different than it does in the Figma design. Please ensure you install any required fonts or replace/substitute any missing fonts in PowerPoint/Keynote/Google Slides where needed.

If you want to exclude any layers from being rendered as rich text in your .pptx file exports, you can include [PNG] anywhere in the layer name of a parent layer (for example, Frame, Group, Component, Instance) that contains your text layers; this will automatically skip over any nested text layers inside that parent layer from being exported as rich text in your PowerPoint exports, and will render that entire layer as a static image instead.

Text used as a Master Slide placeholder supports one transparency value per text layer. If a single Figma text layer mixes different opacity values, split it into separate text layers before export when that difference needs to remain editable in a master layout.

Keeping Auto Layout and nested layers editable (Beta) ​

Enable Smart Auto Layout & Nested Layers (Beta) to export the children of safe layout-style frames, groups, components, and instances, including Auto Layout containers, as separate objects while keeping their Figma positions. Non-text objects keep their relative stacking order, with editable text placed above them. If a safe container has its own fill, Pitchdeck exports that background separately below its supported children. Pair this with Use Editable Text when you also want supported nested text layers to remain editable. The beta controls nested-layer decomposition only; the text, transparency, and native-shape improvements below apply to all PPTX exports.

Pitchdeck keeps supported solid rectangles, ellipses, flat-cap lines, transparency, and individual borders (for example, a bottom border) as native presentation shapes. With the beta enabled, supported text, bullets, icons, images, and lines nested inside safe containers can also remain separate from the container background. Vector-only icon and logo compositions stay together as one selectable object instead of being split into individual paths.

PowerPoint and Keynote retain editable text transparency stored in the .pptx. Google Slides keeps native shape and line transparency during conversion, but may make editable text colours opaque because its native text colour model does not expose transparency. If exact translucent text is more important than editability in Google Slides, add [PNG] to that text layer or a parent layer name so Pitchdeck keeps its appearance in an image.

When a styled frame or instance needs raster fallback, Pitchdeck can separate eligible text from its artwork. All resulting artwork images sit below the editable text, including images with large transparent areas. Text fully inside an opaque rectangular mask can remain editable, including mixed-color text.

With Smart Auto Layout enabled, some Figma compositing cannot be reproduced safely as separate presentation objects. Containers or text whose appearance depends on partial or non-rectangular masking, material clipping, effects, non-default blend modes, partial container opacity, rotation, or layer/background blur retain the fidelity-first raster fallback. Text fully inside an otherwise inert clip may still be editable. Add [PNG] to a container name to flatten its entire subtree, including text. Gradient and image-filled shapes also use the existing image fallback. The beta is disabled by default and does not remove Auto Layout or otherwise change your Figma layers.

Rendering bullet/number lists ​

Enabling the Render Bullet/Number Lists option will export your .pptx file with lists created in Figma text layers carried over.

Each hard return in a Figma list becomes a new bullet or numbered item in the PowerPoint-compatible export. Soft line breaks remain inside the current item, numbered lists continue in sequence, and normal paragraphs can remain unlisted alongside list paragraphs in the same text layer.

Google Slides uses a separate conversion path. For the most predictable Google Slides results, keep each list in its own Figma text layer and move normal text into another layer.

Including slide numbers ​

Enabling the Include Slide Number option will export your .pptx file with page numbering included. This will automatically add a page number to each of your slides in the position you've specified. To change the position of your slide numbers, you can click on the select boxes for horizontal (to select from Left, Center or Right) and vertical (to select from Top, Center or Bottom) positioning.

Using Figma Components as Master Slides ​

Video Tutorial: Add Master Slides to PowerPoint exports from Figma

This video walks through how to export a PowerPoint file from Figma (with Master Slides) using the Pitchdeck plugin.

Enabling the Create Master Slides from Components option will export your .pptx file with any slides created as a Figma Component automatically used as "Master Slides" that can be re-used as templates to create new slides from in PowerPoint, Keynote or Google Slides.

Image placeholders are only supported in PowerPoint Note that images (that aren't locked; see the tip below) will be turned into placeholders for master slides when the PowerPoint export option is selected. Unfortunately, the Google Slides and Keynote export options don't support image placeholders, so any image content will be static in your master slide templates.

Preventing certain image layers from becoming placeholder boxes. By default, any images (besides the slide background) will be turned into placeholder slots in your master slides. If you want to keep any of these image elements static, you can Lock any of those Figma layers (in the main Figma layers panel), and this will ensure that any locked image layers are kept "as-is" in your master slide.

Refreshing slides after editing a master slide in PowerPoint. If you update a master slide in PowerPoint and those changes don't immediately show up on slides already using that layout, select the affected slides and click Home > Reset (next to New Slide) to reapply the layout and refresh the inherited formatting. Here's a short video walkthrough.

Downloading your .pptx file ​

After clicking the Export button, you'll see a confirmation screen letting you know that your .pptx file is ready to download. To download the .pptx file from Figma to your computer, you can click the Download your .pptx file button in the Pitchdeck plugin.

Saving file downloads from Figma If you're using the Figma desktop app, you'll see a prompt appear to download your file. However, if you're using Figma in a web browser, your file will automatically be downloaded to your computer by default (usually to the Downloads directory on your computer).

Opening your .pptx file with Google Slides ​

You can open your .pptx file in Google Slides by going to File, Open, then Upload and drag and drop the .pptx file.

Click All to select all your slides, then ensure you uncheck the Keep original theme checkbox, and then click Import slides.

Replacing custom fonts in your Google Slides PPTX file ​

If you're exporting your Figma frames to a PPTX file for Google Slides that contains some custom fonts (which aren't supported in Google Slides), you can substitute these fonts by using native Figma text styles and using the Description input field to define the font you'd like to replace the font with when the designs are exported to PPTX.

You need to set the Description field of your text style (that your target Figma text layers are using) to this specific JSON string format below:

{ "family": "Inter", "style": "Bold Italic" }

You can replace the family value (for example, Inter) with your desired font family, and set the style value to the desired font style of your font family (for example, Regular, Bold, etc); Note that you need to ensure the font style you use is supported by the font family you've specified; also ensure that the font is a Google Font (which are automatically supported/loaded in Google Slides).

You can also optionally add an extra size (pixels) number property to the JSON string if you want to override the font size as well, like in the example below (which would set the font size to 64px in your PPTX file export):

{ "family": "Inter", "style": "Bold", "size": 64 }