✍️ Figma Buzz – What We Heard and What’s Next
🙏🏼 Thank you for sharing your feedback on Figma Buzz!
Hi everyone! We want to start by thanking each of you who took the time to dive into Figma Buzz and share your thoughts following our Config 2025 announcements. Your feedback has been helpful in surfacing what’s working well, and where we can improve across different workflows, use cases, and team sizes.
We know everyone approaches Figma with different goals, roles, and challenges — whether you’re creating campaigns, managing brand assets, or enabling teams at scale. The diversity of your input is what makes this feedback so valuable.
This summary reflects what we’ve learned from your feedback on Figma Buzz so far in this thread and outlines how we’re using it to guide ongoing improvements.
🔍 Top 5 Themes That Came Up in This Thread
1. Bulk Create: Excel limitations, missing URL/SVG support and file size limits
Bulk creation using Excel surfaced a few recurring challenges — especially around inserting images or linking assets. While some found workarounds using Google Sheets, others pointed to large file sizes and the lack of support for URLs or SVGs as blockers in their workflow.
"Having to include the images in a cell makes the files pretty heavy – I got a 15mb spreadsheet just for 3 rows of info. Using URLs instead would make the spreadsheets way lighter." – @Anders Gressli
"I’ve tried 5 different ways of placing the images into cells. No dice, no matter how I format it… Tried with Google Sheets and it works perfectly." – @Ryan48
2. Auto Layout and Responsiveness Needs
There was consistent interest in more responsive layout behavior within Figma Buzz. The current limitation on applying auto layout to the parent frame, along with restricted control over vertical scaling, was seen as a hurdle to building assets that adapt across formats like mobile, desktop, and email.
"The part I’m struggling with is getting auto-layout in the main frame/container. I could only figure out how to resize the template by typing in values. I need a template that will scale responsively vertically so we can use one to cover desktop or mobile." – @John43
3. Template Usability: Locking, Notes, and Responsive Behavior
When working with templates across teams, several contributors noted friction points, including limited options for locking fields, adding helper notes, or swapping instances more intuitively. The lack of hug-content or responsive scaling was also raised as a factor that could make templates feel too rigid in some workflows.
"The ‘Swap content’ feature is not immediately clear for marketing users... I wouldn’t count on my teammate to click the small ‘Swap content’ button if they didn’t know those variants existed in the first place." – @Cindy_Wong1
"It should be possible to remove the possibility to remove restrictions… otherwise users will just unlock everything and we’ll lose brand control." – @SSB
"The fact that templates cannot be set to hug content is deeply frustrating… If the template isn’t responsive, then it’s really only useful for generating static social media content." – @Neil_Norman
4. Design System and Component Sync Gaps
Some users shared challenges when trying to connect Figma Buzz with existing design systems. Updates made in Figma Design didn’t always reflect automatically in Figma Buzz, which led to extra manual steps. Limited access to shared libraries and the lack of plugin support also seemed to create friction for teams aiming to stay consistent across assets.
"You update the component in Figma Design and publish it. There is no update in Buzz… You have to manually replace every single asset from scratch." – @JustAnotherIsaac
5. Print and Video Support Requests
Several replies raised the need for broader export options — including CMYK support for print, multi-page PDFs, and grouped exports. Video preview and export were also mentioned as important for social media workflows and broader content strategies.
"Will we get video preview and video export for Buzz? Another question — will we get CMYK and print export for Buzz?" – @Richard_Meechan
🛠️ What we're doing with this feedback
Some of the feedback shared here has already helped shape updates or surfaced issues we’ve since addressed, while other themes are informing ongoing conversations within our product teams.
Here’s what we can share for now:
- ✅ Excel image upload issues — This has been fixed. Images embedded in Excel files now upload as expected, thanks to early reports in this thread!
- ⚙️ Auto layout at the parent frame level — This is currently not supported, but your use cases are being reviewed as the team explores layout flexibility in future iterations.
- 🔄 Swap Content, multi-editing, and content editing controls
These features exist today but aren’t always intuitive, especially for non-designers. The product team is aware of this friction, and this feedback will help inform future improvements to clarity and in-product guidance.
In the meantime, to multi-edit in Figma Buzz, here’s a loom on how to access that: Watch the Loom video (from amxyz (in reply to Kate Reeves)
- 📌 Template locking and guidance
Suggestions around stricter locking and helper notes have been passed along. While this isn’t something the team is actively exploring at the moment, the feedback has been shared internally and may help inform future discussions.
- 🧩 Component sync from Figma Design — We’ve heard the need for easier updates between Figma Design and Figma Buzz. While automatic syncing isn’t available yet, this is an area the team is actively exploring internally.
- 🔗Library and plugin access —We’re exploring ways to make default libraries more configurable in Figma Buzz, including how colors, fonts, and inserts appear. Plugin support is also being looked into, with more to come, stay tuned!
- 🖨️ Export options (CMYK, multi-page PDFs, video) — The team is currently working on improved video capabilities and requests for CMYK and PDF are on the team’s radar for future consideration.
- 🌍Font, encoding, and language support – Issues with diacritics, font compatibility, and encoding (e.g., in Oakes Grotesk) are being investigated, with some bugs possibly tied to Excel vs. Google Sheets handling.
While we don’t have a specific timeline to share, any updates that are released will be documented in our release notes and relevant forum threads.
💬 What’s next — want to keep the conversation going?
If you still have questions, ideas, or things you want to see improved, here’s where to go:
Tip: Before starting a new topic, try searching the forum — there may already be discussions related to what you're thinking. It’s a great way to join ongoing conversations and discover helpful insights shared by others.
Thanks again for contributing to the Figma community. We hope this summary brings more clarity to how your feedback is being heard.
Looking forward to seeing what you create with Figma Buzz!
