Figma exports as PNG when your browser or system settings override the SVG format you selected

When you click "Export as SVG" in Figma but the file arrives as PNG, one of three things usually happened: your browser's download settings automatically converted the file, your operating system intercepted it, or Figma itself fell back to PNG because your design contains elements that SVG cannot render. The most common culprit is your browser's download behavior — many browsers are set to convert certain file types automatically or to ask you where to save files, and during that process the format can change.

Understanding which of these three caused the problem matters because the fix is different for each one. A browser setting is quick to change. A system-level issue may need a restart. A design problem means you need to simplify what you're exporting before SVG will work at all.

Key Takeaways

  • Check your browser's download settings first — Chrome, Firefox, Safari, and Edge all have options that can auto-convert file types or change extensions during download.
  • Figma automatically exports as PNG instead of SVG if your design uses raster images, certain blend modes, or effects that SVG format cannot support.
  • Right-click the exported file and check its properties or file info to confirm whether it is actually a PNG or a mislabeled SVG file.
  • If the file is truly PNG, re-export from Figma and watch the download dialog carefully — the format can change in the final step before the file lands on your computer.

How to check what Figma actually exported

Before you change any settings, confirm whether Figma sent you a real PNG or a file that is actually SVG but has the wrong name. Right-click the downloaded file on your computer and open "Properties" (Windows) or "Get Info" (Mac). Look at the file type listed there — not just the extension at the end of the filename, but the actual file type your system recognizes.

You can also open the file in a text editor like Notepad (Windows) or TextEdit (Mac). The very first line of a real SVG file starts with <svg or <?xml. If you see those characters, the file is SVG and Figma did its job correctly — your browser or system just renamed it. If you see binary gibberish or PNG header data, the file is genuinely PNG and Figma converted it during export.

Why Figma converts SVG to PNG automatically

Figma will not export as SVG if your design contains elements that the SVG format cannot handle. The most common blockers are raster images (photos or bitmap graphics you placed in your design), blend modes like "Multiply" or "Screen" that don't translate cleanly to SVG, and certain effects like blur or shadow applied in ways that SVG interprets differently than Figma does.

When Figma detects these, it silently exports as PNG instead, even though you selected SVG. You will not get a warning — the export dialog will still say "SVG" but the file that downloads is PNG. To fix this, select the element causing the problem (Figma will not tell you which one), delete it or convert it, and try exporting again. If you have a photo in your design, delete it before exporting as SVG. If you used blend modes, flatten the layers or remove the effect.

Browser download settings that change file formats

Chrome, Firefox, Safari, and Edge all have download settings that can interfere with file types. In Chrome, go to Settings > Downloads and look for "Ask where to save each file before downloading" — if this is off, Chrome may auto-convert certain formats. Firefox has a similar setting under Preferences > Files. Safari does not have a direct toggle, but it automatically opens safe file types after download, which can trigger conversion.

The safest approach is to turn on "Ask where to save each file" in your browser. This forces a download dialog to appear, and you can watch the filename and extension as it saves. If the extension changes from .svg to .png in that dialog, your browser is doing the conversion. You can then cancel, change the filename back to .svg, and save it again — though the file will still be PNG if Figma sent PNG.

Windows and Mac system settings that affect downloads

Some Windows systems have file type associations that auto-convert on download. If you have set PNG as the default handler for image files, Windows may convert SVG to PNG when it lands in your Downloads folder. Check this by going to Settings > Apps > Default Apps and searching for SVG — if no application is listed, Windows will not auto-convert. If an image editor is listed, that app may be interfering.

On Mac, check System Preferences > General and look for "Remove duplicates from the Downloads folder" and "Remove items from the Trash after 30 days" — these are not the culprit, but if you have antivirus software installed, it may scan downloads and convert formats. Temporarily disable antivirus, export again, and see if the format stays correct. If it does, add Figma to your antivirus exclusion list.

How to export SVG correctly from Figma

In Figma, select the frame or component you want to export. On the right panel, scroll to the "Export" section and click the plus icon. In the dropdown that appears, select "SVG" — not "PNG" or "JPG". Before you click "Export", make sure your design does not contain any raster images, unusual blend modes, or effects that might trigger automatic conversion.

When the download dialog appears, watch the filename carefully. It should end in .svg. If it ends in .png, cancel the download, go back to Figma, and check your design for the elements listed above. If the filename is correct but you still receive PNG, your browser or system is converting it — try a different browser to test whether the problem follows you or stays with your original one.

Testing with a different browser or computer

If you have tried the steps above and SVG still arrives as PNG, test with a different browser on the same computer. Open Figma in Firefox if you normally use Chrome, or vice versa. Export the same file and check what you receive. If the second browser exports correctly as SVG, the problem is your first browser's settings — go back and adjust them as described above.

If both browsers send PNG, the problem is either Figma's conversion (your design has incompatible elements) or a system-level setting. Try exporting on a different computer if you have access to one. If that computer receives SVG correctly, your original computer has a system setting or antivirus rule that is converting the file. If the second computer also receives PNG, Figma is converting it because of your design.

Frequently Asked Questions

Can I convert the PNG back to SVG after Figma exports it?

No — once Figma exports as PNG, the vector information is gone. PNG is a raster format and cannot be converted back to true vector SVG without tracing software, which produces poor results. The only solution is to export correctly from Figma the first time by removing the elements that triggered the conversion.

Does Figma tell you when it is converting SVG to PNG?

No. Figma will not warn you or show an error message. The export dialog still says "SVG" but the file that downloads is PNG. You have to check the file yourself after download to know what actually happened.

What if I need the raster image in my SVG export?

SVG can technically contain embedded raster images, but Figma does not support exporting them that way. If you need both the vector and the image, export the vector parts as SVG and the image separately as PNG, then combine them in your code or design tool afterward.

Why does Figma not just warn me before converting?

Figma treats SVG export as a best-effort feature — it assumes you know your design may not be fully compatible with SVG format. The responsibility is on you to check what you exported and test it in your intended use case.