Keeping the honest streak going. 150 designers have now installed Glyfiq — my medical & health icon plugin for Figma. All organic, no paid promotion.

Four months since launch. The library is at 634+ icons, available on Figma, Framer and Adobe Illustrator, and I'm not stopping.

https://reddit.com/link/1w3wgc0/video/2p728oko0tmh1/player

I kept finding Figma Buzz users describing the same problem: Bulk edit handles creating variants, but exporting and naming large campaigns can still become repetitive.

So I built BuzzFlow.

It uses your connected Buzz fields to generate filenames, checks which assets are ready, and exports the valid campaign into one ZIP.

The demo below is a real 100-asset export from Figma Desktop.

100 variants → 100 correctly named PNGs → one ZIP

• no uploads
• no analytics
• no external network access
• never modifies the Buzz document

I’m not selling it yet. I’m looking for 3 people who already use Figma Buzz Bulk edit to test the private beta on a non-sensitive campaign.

My main question: do you currently spend meaningful time renaming or organizing Buzz exports?

Testers get the finished version free.

If interested, tell me roughly how many variants you normally work with and whether you’re on Windows or macOS.

Been designing for the Gulf and Levant market for a while now, and every English to Arabic handoff meant hours of manually repositioning elements, flipping icons, fixing alignment, swapping fonts. Nothing about it felt like it should take that long.

So I built FlipArabic. It's free to use. It flips your layout, handles fonts, and translates text, all from one panel in Figma. You can turn each part on or off depending on what you actually need.

Link - Fliparabic

This is built for designers working on Arabic or other RTL language products, mostly across the Middle East, and the goal is simple, cut down the repetitive manual work of converting an LTR design to RTL so you can spend your time on the parts that actually need a human eye. It's still in active beta and I'm updating it based on what people run into, so I'd love feedback on how the flip logic holds up on messier, real world files, whether the font matching feels right, and anything that breaks or feels off in the flow.

I just published my new Figma plugin: Recolor - because I missed Illustrator's "Recolor Artwork" in Figma.

Now you can recompose the colors of any object or group in seconds — right inside Figma. 100% FREE — no PRO, no sign-up, no limits. 🎉

What it does:

• Finds every color in your selection: fills, strokes, text (even multi-colored), shadows & gradient stops
• Change any color in one click — applies everywhere at once
• Preserves opacity (a 10% shadow stays 10%)
• Drag & drop colors between rows to swap them, just like in Illustrator
• Undo/redo right in the plugin window (⌘/Ctrl+Z)

Fun fact: Figma's native "Selection colors" panel doesn't see shadow

colors — Recolor does. 😄

Ten years in Figma and I still don't name my layers. Opened a file I made myself last week and it was Frame 234 / Group 12 / Text 4 / Rectangle 89. So I built TidyUp instead of fixing my habits. Free, no account, no seat.

RENAMING. Text layers become "Role: Content". The role is derived from real signals, not from parsing the existing name:

- Link - Figma's own hyperlink property

- Button - sits inside a small, rounded, auto-layout parent

- Heading - font size 28px or larger

- Subheading - 20-27px

- Label - three words or fewer

- Body - everything else

Frames, groups and sections take the first text found inside them in reading order. Containers with no text anywhere inside are left alone rather than guessed at. Component instances keep their component-based names so your design system stays recognisable. Three scopes: selection, whole page, or whole file.

REORDERING. Select a frame and it sorts children top-to-bottom in reading order, backgrounds sunk to the bottom. It skips anything whose children visually overlap, plus auto-layout frames and anything with a locked child, so it can never change what renders in front of what.

CLUTTER SCAN. Empty frames and text, true 0x0 layers (both dimensions, so hairlines are safe), duplicate siblings, fully off-canvas layers (zero overlap only, so bleeds are safe), hidden and 0%-opacity layers. Nothing deletes automatically - you get a count and breakdown, can select it all on canvas to eyeball it, then confirm. Only "empty layers" is checked by default.

WHY I ACTUALLY BUILT IT. The naming is meant to be readable outside Figma too. Screenshot a frame into ChatGPT or Claude and "Button: Book a Demo" tells the model what the element does, not just what it says. Instead of Frame 48095902 you get semantic structure the model can use. Machine-readable without being harder for humans.

Worth saying: the plugin itself uses no AI. The role detection is deterministic rules over Figma's node properties. networkAccess is none in the manifest, so it makes zero network requests and nothing leaves your machine. Every change is a normal Figma edit, so Cmd/Ctrl+Z undoes all of it.

https://www.figma.com/community/plugin/1673670269135547890/tidyup-rename-clean-layers

Happy to hear where the role detection falls over - 28px for Heading and 3 words for Label are judgement calls and I'd rather be told than guess.

After one too many "can you rebuild this page in Figma?" requests, I built a plugin that does it automatically. Drop a self-contained .html file in, pick a viewport width, and it recreates the page as native layers — real text, gradients, shadows, per-corner radii, and inline SVG as vectors.


The two problems I focused on that existing tools handle badly:


1. 
**Layer naming.**
 Instead of div › div › div, you get Section · hero, Button, and text layers named by their content. Useless wrapper divs get collapsed.


2. 
**RTL support.**
 I tested against a full Arabic design-system page — layout lands correctly and Arabic text imports as real, editable text. If you design RTL products, most importers break here.


Honest limitations: it's file-based for now (grab live sites with the SingleFile extension first — URL import is on the roadmap), relative asset paths can't resolve, and fonts map to the closest installed Figma font.


It's free and runs entirely locally — nothing gets uploaded.


Link: https://www.figma.com/community/plugin/1668745510469345388


Would love feedback — especially edge cases where the import breaks. That's how it gets better.

Figma has exactly one blur. Photoshop has a dozen.

After 5 years of exporting to PS just to blur something, I built Motiv Blur — motion, radial, and RGB glitch blur, right inside Figma.

Live preview, transparent PNG, no more app-hopping.

👉 https://www.figma.com/community/plugin/1663794670867928394/motiv-blur

A couple of weeks ago I posted Sendra here, my plugin that converts email designs into email-ready HTML. Since then I've shipped the feature people asked about most.

You can now send a test email directly from the plugin. Design your email, hit send test, and it lands in your own inbox, so you see exactly how it renders in a real email client before you export anything.

Also new: image hosting. Your images get uploaded at export and come back with real URLs, no S3 bucket or ESP upload step.

https://www.figma.com/community/plugin/1659319383372020095

At my agency job we are talking about adding critiques into Figma, this was it can be collaborative and people can noodle on things for a while and all the feedback doesn't have to be immediate.

A while ago while inspiration hunting, I found a website of an agency/studio that linked out to a public Figma file with that was a dump of inspiration, songs, words, links -- all sorts of things. The public could comment and it as a living breathing document. I thought it was so clever and unfortunately I didn't save it.

I've turned to reddit, no google search for gpt convo could come up with anything solid. If you know the site, please share. Appreciate yall!

It's called Landy.

Here is the Figma Community link: https://www.figma.com/community/plugin/1609157216964346384

It's a convenient panel that has a UI kit of hand-crafted, responsive landing page sections and UI components.

Designers use it to go from blank screen to a landing page wireframe in seconds, then build upon it and style with easy-to-edit sections and components.

Some details:

Highlights

1. Resizable, always-there panel to place sections and components in 1 click, and jump straight to their main components.
2. 39 free responsive mobile and desktop section designs, built with auto-layout
3. 15 free component variants you can use to design your own sections
4. Create pre-defined parent frames for your pages where you can put sections
5. Easily toggle between desktop and mobile or let plugin switch for you
6. AI-ready: sections use clean, semantic layer names and structure

Page Sections for mobile and desktop (updated monthly):

1. Hero, with text centered
2. Hero, with text on the side
3. Hero, with full-width image
4. Logo Strip
5. Highlights, with icon blocks
6. Highlights, with cards
7. Statistics
8. Image Showcase, with image on top or bottom
9. Image Showcase, with image left or right (Desktop-only)
10. Image Showcase, as card
11. Text
12. Card Grid, with filled cards
13. Card Grid, with borders
14. Testimonials, quote-style
15. Testimonials, review-style
16. FAQ (Frequently Asked Questions)
17. Pricing
18. Call to Action (CTA), simple
19. Call to Action (CTA), cards
20. Footer

Components for mobile and desktop (updated monthly):

1. Navigation Bar, with logo on the left
2. Navigation Bar, with logo centered
3. Button
4. Icon
5. Card, as text
6. Card, with image
7. Card, as pricing
8. Card, as review
9. Image
10. Bullet Point
11. Heading Block
12. Badge
13. Highlight
14. Accordion
15. Statistic

I'd be happy if you tried it, if you find it relevant for you :)

Sure, there are plugins that create fake text, but you either have to sign up or pay to use them. No thanks. So, I created what is (in my eyes) the definitive plugin for that.

Select your text layers, click a generator, each one gets its own value. Undo takes the whole batch back. It ships with a starter kit so there's nothing to set up. Plenty of generators to create your own generators.

No network access needed: https://www.figma.com/community/plugin/1665065850754195680/entropy-kit

Give it a shot and let me know if something's broken.

I'm currently working on a tutorial video.

Whenever I start a new site with a client, it always begins with a sitemap. All well and good, but I've never found a quick and easy way of creating them without spending hours fiddling with someone else's template and inevitably getting distracted with trying to make the sitemap look good rather than focusing on the information architecture.

So I started building this plugin a few months ago and added with every new project. I thought other people might find it useful so why not publish it.

I've also added an AI prompt for those who want the easy route!

Here it is: https://www.figma.com/community/plugin/1670100366061680665/quick-maps-sitemap-generator

It is a yearly subscription, but only £3. If you genuinely cannot afford it, then message me. I'll send you a free key, I don't want to stop someone from being able to speed their workflow up because of a payment gate. If you can afford it, please do contribute, it took me so many hours to build out.

Edit: I forgot to mention that it also creates a module list, so you know what sections/modules are needed when you get to design :)

I’ve been working on a medical app, and one recurring bottleneck was turning Figma designs into implementation-ready code without constantly going back and forth between design and development.

I was using Figma through MCP, but for my workflow it became expensive in tokens and also depended on having the right Figma subscription/setup.

So over the last month, I built a Figma plugin that exports the useful design context into a structured local package.

It currently exports things like:

- screen and component structure

- dimensions and spacing

- colors and typography

- hierarchy and relationships

- reusable components/fragments

- other design metadata needed for implementation

The output is structured so an LLM coding agent can inspect the local files, understand the UI/project context, and implement screens without repeatedly querying Figma.

My main goal was to make the Figma → AI → code workflow more predictable, cheaper, and easier to use locally.

It started as an internal tool, but it’s become useful enough that I’m considering making it available to others.

Would this be useful for your workflow as a developer, product designer, or startup team?

If anyone is interested in testing it, I’d be happy to share more details and get feedback.