# Troubleshooting Pitchdeck
- Frames used as slides should all be the same size
- Thin white line around image exports
- Google Slides only supports "custom" Google Fonts
- Misaligned editable text in PPTX file exports
- Pixelated image exports
- Google Slides will downscale any image over 1600x1600 pixels
- Slides not uploading from the plugin, or images not loading in the web app
- The "100% of memory used" Figma memory leak issue
- Gradients not supported for editable text in .pptx exports
- GIFs embedded in Figma documents
- Blank file extensions using Figma desktop app on Windows
- Google Slides 100mb file size limit
- PNG images and forcing background transparency
- Install custom fonts that are missing in .pptx exports
- Presentation URL expiry after 30 days
- VPN may be required in China
# Frames used as slides should all be the same size
Please ensure all your frames are the same size; 16:9 ratio frames are recommended (eg. 1280x720 or 1920x1080) for the best presentation results across most monitors and TV screens.
# Thin white line around image exports
Occassionally some images will contain a faint, thin white line around the edges. Figma does this (opens new window) if a layer isn't positioned on a rounded pixel value (eg. Y: 156.76 or X: 56.3) will automatically result in this sub-pixel line getting included in the export. To resolve the issue, please ensure that your layer positions are all rounded pixel values.
# Google Slides only supports "custom" Google Fonts
If you're using third party fonts to design your slides in Figma, and exporting your presentation for Google Slides, please note that Google Slides won't be able to render the font (even if it's installed on your computer), as it only supports any font that is available via Google Fonts (opens new window).
# Misaligned editable text in PPTX file exports
This is often caused by text layers having a fixed width/height in Figma on the text layer's bounding box which is smaller than the size of the text content itself, which causes an incorrect position offset. Setting the text layer resize option in Figma to "Auto Height" should resolve this.
The other cause of this is usually a text layer in Figma that contains multiple line-height or font size values in the same block of text. Unlike Figma, unfortunately PPTX files only support a single/overriding line-height value per text layer, and having multiple font sizes per text block will also throw out the vertical flow in your PPTX file.
To resolve this issue, you can split out the text content inside of your Figma text layer with a different line-height or font size into its own layer, and position that where you need to be in relation to the other text layer(s); this way each text block will have its own single line-height and font size value.
# Pixelated image exports
If you're exporting a presentation while the image assets in Figma are still progressively loading, they may be exported looking pixelated, as the image wasn't fully loaded in the Figma file before it was exported. To resolve this, please ensure that all of the images have loaded 100% and are looking sharp inside the Figma file before exporting your presentation with the Pitchdeck plugin.
To help further with solving this issue, you can use the "Downsizer" feature (opens new window) in our TinyImage Figma plugin (opens new window) to shrink down your image fills to match their layer size, which will shrink their file size and ensure they load much faster in your Figma file.
# Google Slides will downscale any image over 1600x1600 pixels
If you're exporting your designs to use in Google Slides, please note that Google Slides will automatically "downscale" any images in your deck that are bigger than 1600 pixels; this can cause them to lose some visual quality if you're exporting them to a .pptx file with larger images than the upper limit.
To help avoid this, if you select the Google Slides option in the export settings, Pitchdeck will automatically ensure your images sizes are capped at 1600px to avoid them getting compressed when imported into Google Slides.
# Slides not uploading from the plugin, or images not loading in the web app
One reason this might be happening is if your ISP (internet service provider) is blocking the QUIC protocol. You can confirm this by opening up your developer console in the browser or in Figma and see the error message
There are a couple of workarounds for this issue:
- Switching to your mobile phone's Wi-Fi hotspot/tether for you computer's internet connection
- Disabling QUIC (opens new window) in your browser
# The "100% of memory used" Figma memory leak issue
There's a rare/known bug where Figma will run out of memory while trying to extract SVG image data from certain complex layers; these usually include groups that contain multiple text layers or single complex text layers (often using a custom font, which requires more memory in Figma).
If you run into this error, the Pitchdeck plugin will display a notification at the bottom of the screen telling you which frame, and which layer specifically is causing the memory issue.
It will also tell you to click the "reload page" in the Figma warning dialog, and then once the page reloads, to add
[PNG] to the start of the problematic layer name (eg. "[PNG] My original layer name"). This will let the Pitchdeck plugin know to fetch PNG image data for that specific layer instead of SVG image data, which resolves the memory issue.
# Gradients not supported for editable text in .pptx exports
If you're using a gradient fill(s) for a text layer in your Figma design, Pitchdeck will automatically take the first gradient fill and use the first colour of that gradient as the "solid" colour in your
# GIFs embedded in Figma documents
Due to GIF export not being natively supported in Figma, any GIFs added "directly" inside your Figma designs won't be animated; to use animated GIFs, please add them as URLs inside the Pitchdeck plugin.
# Blank file extensions using Figma desktop app on Windows
There's a known issue with the Figma desktop app (only on Windows), which also happens for normal file exports from Figma. When you go to save your file, you may see an "all files" label. If you ignore this and continue by clicking "Save", it should still save the file with the correct extension and allow you to open it as expected after it has downloaded to your computer. If it still saves the file with a blank extension, you should be able to rename the file to manually append the correct extension to the file name.
# Google Slides 100mb file size limit
Google Slides has a 100mb limit per PPTX file getting imported; one workaround for this is to split up the PPTX file you'd like to import into smaller files (using a tool like this (opens new window)) and then upload them into your Google Slides file one at a time (which gets around the upload size limit issue, and still lets you have all the slides in one file).
# PNG images and forcing background transparency
Pitchdeck will try to automatically detect if a layer contains areas of full transparency and set PNG as the default export format, otherwise it will be set to JPG. You can override this by adding [PNG] to the Figma layer name, or by setting the export setting format of any layer to JPG or PNG in Figma's right-hand column.
# Install custom fonts that are missing in .pptx exports
Please 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 where needed.
# Presentation URL expiry after 30 days
Presentation URLs will automatically expire after a 30 day period of inactivity (30 days after the link was last accessed and viewed); if you would like to re-activate the URL after it has expired, simply run Pitchdeck in the Figma file and click Upload Web Presentation.
# VPN may be required in China
Please note, if you're in China, the accounts server may be blocked by "The Great Firewall of China". If you're seeing a activation error, despite using a valid key, you will likely need to use a VPN (opens new window) to resolve the issue.