Issues with Relume Figma Kit v3.0: Seeking Community Support

Nate L. · 2025-06-12 12:39:48.24342+00

Just joined here so apologies if this has been discussed - feel free to point me to the post containing the solution. I, along with much of the community based on the comments , am having trouble with the latest Relume Figma Kit (v3.0). We've been adding these kits continuously to Figma to export Relume Wireframes since v1.2 with no issues. The v3.0 has been added and published within our account but still am receiving this (attached) when running the Relume plugin within a Figma file.

Issues with Relume Figma Kit v3.0: Seeking Community Support | Relume Community

14 comments

· Sorted by Oldest

Matt J.
·
·
Nate L. make sure that you open the actual v3.0 figma kit file and not attach it as a library and then opening up a second file. Our figma plugin needs to detect certain elements in order to know that its the v3.0 plugin before attempting to import and does not support the figma kit being included as a library.
Matt J.
·
·
if thats not what you are trying to do - can you snap a screenshot of the app with the style guide page in the background just so we can rule this out?
Nate L.
·
·
Matt J. thank you for the reply, Matt! the Relume plugin operates as expected within the original v3.0 figma kit file - but we have dozens of ongoing projects (individual files) that need Relume Wireframes to be exported into. if publishing this library so I can add it to our starter template/existing files isn't supported, how am I to export the Relume Wireframes into files outside of this v3.0 file?
Matt J.
·
·
Nate L. for these other figma files - are they based on a relume figma kit previously or are they essentially blank/open figma files?
Nate L.
·
·
Matt J. the template that we duplicate for each project isn't necessarily a blank/open figma file - it has the most recent figma kit added to it, as well as variables and modes that we want retained for each project, the reason behind leveraging a template for us. I've always published the most recent kit, then in the template removed the old and added the most recent. this has caused no issues in leveraging Relume components and importing Relume wireframes over the past year+. if our process requires changing due to this newest version please guide me in how to navigate this if you're able to!
Nate L.
·
·
Matt J. just following up in here - happy to take this to DMs as well if that would be helpful.
Matt J.
·
·
Nate L. Apologies for the delay Nate. If its an older figma kit (previous to 3.0) then you won't be able to import a style guide from Site Builder. You should be able to import wireframes and sitemaps into older figma kits (see screenshot). I am not sure in what use case yet why you'd receive the screen above but I have a feeling its because the figma plugin can not detect what version of the figma kit you are using. The workaround for this would be to open up the figma kit directly that you are using as a library, import wireframes and copy/paste them into your master file.
Matt J.
·
·
There's also a potential that depending on the edits you are making to the figma kit, it could be causing other issues as well. I too make customizations to the figma kit - and have for years now, but I just learned that the figma plugin depends on certain sections existing as they are. Starting to think it might be better to leave the style guide page as is, and create a new one and then link the variables up - if you are trying to change the presentation or something. I still dont have the full context of your workflow though so this is just me shooting in the dark.
Nate L.
·
·
Matt J. Thanks, Matt! To your first point, not importing the Style Guide is fine as we only want the Wireframes anyways, however I'm still having trouble adding Wireframes via the Relume plugin on older projects that have the prior version kit added. Receiving the screenshot I sent last message. To the second, this does seem like the only workaround I've found but given how many different Wireframes (clients) we import into Figma this isn't ideal for our workflow and we'd much rather export into each clients' dedicated file. Lastly, the third, we do not make any edits whatsoever to the kits. Not to the variables, Style Guide, components, etc. The variables I'm creating are not attached to anything in our template, we attach to the design once we've imported the Wireframes for each individual file. I've duplicated the 3.0 kit to see if I can repurpose it as our new template and I'm able to import Wireframes, however, there is an issue in this export.. See screenshot.
Matt J.
·
·
so you have a single Relume figma kit as a figma library, serving multiple individual client figma file projects?
Nate L.
·
·
Matt J.
·
·
thinking we might have our wires a bit crossed so to prevent any further confusion - do you think it would be at all possible for a quick loom to walk me through your workflow?
Nate L.
·
·
Matt J. I've revised that last message a bit. I would very much appreciate that! thank you for all attention here.
Matt J.
·
·
okay, yeah I would need a loom from you to better understand your workflow. In regards to your screenshot - you attempted to import INTO the figma kit directly? Did you see any errors that might have shown up while importing? This typically happens if its 1. Not a Relume figma kit 2. the font it wants to use, is missing from your system.

Matt J.
·
·
Nate L. make sure that you open the actual v3.0 figma kit file and not attach it as a library and then opening up a second file. Our figma plugin needs to detect certain elements in order to know that its the v3.0 plugin before attempting to import and does not support the figma kit being included as a library.
Matt J.
·
·
if thats not what you are trying to do - can you snap a screenshot of the app with the style guide page in the background just so we can rule this out?
Nate L.
·
·
Matt J. thank you for the reply, Matt! the Relume plugin operates as expected within the original v3.0 figma kit file - but we have dozens of ongoing projects (individual files) that need Relume Wireframes to be exported into. if publishing this library so I can add it to our starter template/existing files isn't supported, how am I to export the Relume Wireframes into files outside of this v3.0 file?
Matt J.
·
·
Nate L. for these other figma files - are they based on a relume figma kit previously or are they essentially blank/open figma files?
Nate L.
·
·
Matt J. the template that we duplicate for each project isn't necessarily a blank/open figma file - it has the most recent figma kit added to it, as well as variables and modes that we want retained for each project, the reason behind leveraging a template for us. I've always published the most recent kit, then in the template removed the old and added the most recent. this has caused no issues in leveraging Relume components and importing Relume wireframes over the past year+. if our process requires changing due to this newest version please guide me in how to navigate this if you're able to!
Nate L.
·
·
Matt J. just following up in here - happy to take this to DMs as well if that would be helpful.
Matt J.
·
·
Nate L. Apologies for the delay Nate. If its an older figma kit (previous to 3.0) then you won't be able to import a style guide from Site Builder. You should be able to import wireframes and sitemaps into older figma kits (see screenshot). I am not sure in what use case yet why you'd receive the screen above but I have a feeling its because the figma plugin can not detect what version of the figma kit you are using. The workaround for this would be to open up the figma kit directly that you are using as a library, import wireframes and copy/paste them into your master file.
Matt J.
·
·
There's also a potential that depending on the edits you are making to the figma kit, it could be causing other issues as well. I too make customizations to the figma kit - and have for years now, but I just learned that the figma plugin depends on certain sections existing as they are. Starting to think it might be better to leave the style guide page as is, and create a new one and then link the variables up - if you are trying to change the presentation or something. I still dont have the full context of your workflow though so this is just me shooting in the dark.
Nate L.
·
·
Matt J. Thanks, Matt! To your first point, not importing the Style Guide is fine as we only want the Wireframes anyways, however I'm still having trouble adding Wireframes via the Relume plugin on older projects that have the prior version kit added. Receiving the screenshot I sent last message. To the second, this does seem like the only workaround I've found but given how many different Wireframes (clients) we import into Figma this isn't ideal for our workflow and we'd much rather export into each clients' dedicated file. Lastly, the third, we do not make any edits whatsoever to the kits. Not to the variables, Style Guide, components, etc. The variables I'm creating are not attached to anything in our template, we attach to the design once we've imported the Wireframes for each individual file. I've duplicated the 3.0 kit to see if I can repurpose it as our new template and I'm able to import Wireframes, however, there is an issue in this export.. See screenshot.
Matt J.
·
·
so you have a single Relume figma kit as a figma library, serving multiple individual client figma file projects?
Nate L.
·
·
Matt J.
·
·
thinking we might have our wires a bit crossed so to prevent any further confusion - do you think it would be at all possible for a quick loom to walk me through your workflow?
Nate L.
·
·
Matt J. I've revised that last message a bit. I would very much appreciate that! thank you for all attention here.
Matt J.
·
·
okay, yeah I would need a loom from you to better understand your workflow. In regards to your screenshot - you attempted to import INTO the figma kit directly? Did you see any errors that might have shown up while importing? This typically happens if its 1. Not a Relume figma kit 2. the font it wants to use, is missing from your system.