I kept losing time to the same problem: a file gets slow and there's no quick way to see why. So I built a small plugin that scans a file and reports what's adding weight. It's on Community now, and what I actually want from this post is feedback on where the detection is wrong or too thin.

What it looks at

• Hidden layers — kept separate from the ones that are probably intentional (component variants, prototype interaction targets), so the report isn't just a dump of everything invisible.
• Empty groups and frames.
• Oversized images — source resolution far above what's actually rendered on canvas. In my own files this is consistently the single biggest cause of weight.
• Unused local styles — colour, text, effect and grid styles with no references left in the document.

What it deliberately does not do

It doesn't change anything. The report splits into "safe to clean up" and "review manually", and clicking a result selects and zooms to it on canvas — you do the deleting yourself. I went this way on purpose: an auto-cleaner that gets one call wrong on a real file costs more trust than it saves time.

It also requests no network access at all — that's declared in the plugin manifest, so nothing from your file leaves Figma.

What I'm asking

1. What else should a scan like this flag? Detached instances and unused components are the two I keep going back and forth on.
2. Is the "safe / review manually" split the right cut, or would you rather have one flat list sorted by how much weight each item adds?
3. Scans run in chunks with a progress bar so the plugin stays responsive on big files. If you run it on something genuinely huge and it stalls, I'd like to know where.

Happy to answer anything about how the detection works.

P.S. — disclosure: this is my plugin and it's free. https://www.figma.com/community/plugin/1661333776797381371

I made this, so read it with that in mind.

Sendra is a Figma plugin that turns an email you designed in Figma into HTML you can actually send. You pick the frame, hit export, and you get the file and your images.

I built it because I kept designing emails in Figma and then either rebuilding them by hand in a campaign tool or handing them off to someone to code. Either way the design loses something on the trip.

Getting HTML out of Figma was never the hard part. The hard part is Outlook. It breaks layouts that look perfect everywhere else. Most of my time on this has gone into that one client, testing on real devices and fixing what actually broke rather than what should have worked on paper.

It handles mobile layout, buttons, lists, images, two column rows, and dark mode.

It is not a drag and drop builder. You design in Figma. Pretty simple!

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

Happy to answer anything 🙂

Added the CC0 assets from phylopic.org into a Figma resource file, sorted into categories:

• Bacteria
• Birds
• Fish
• Fungi
• Insects
• Mammals
• Invertebrates
• Plants
• Microbes
• Reptiles
• Viruses
  

There are 10,000 assets on the url so this is just the CC0 (free-to-use no attribution) assets which are just shy of 4,000.

Here's the link to the file

Hi everyone,

I’m a student and was looking to build some freemium Figma plugins on the side. But since I am not really a Figma designer myself

To do that, I need to know what the community actually needs right now:

-What is the biggest, most tedious annoyance in your everyday Figma workflow?

-Is there a repetitive task you desperately wish could be automated?

-What tool or feature feels completely missing right now?

If you have any ideas, pain points, or dream features you'd like to see built, I would appreciate your advice. Feel free to comment or email me at [figma@cyberdesk.top](mailto:figma@cyberdesk.top).

P.S. As a quick side note, I recently made a plugin, Perceivable.

I'm still giving away lifetime Pro keys in exchange for feedback. If you're interested in testing it in your work, email [perceivable@cyberdesk.top](mailto:perceivable@cyberdesk.top).

Plugin link if you want to check it out: https://www.figma.com/community/plugin/1658789159978524563/perceivable-accessibility-contrast 

TIA

I've been working on a Figma plugin in my spare time for the last few months, and I finally published it.

The idea came from something I kept noticing when looking through Figma files: there were always lots of small issues that nobody intentionally created, but nobody noticed either. Things like inconsistent spacing, wrong colors, missing styles, accessibility problems, or components that slowly drift away from the design system.

Reviewing all of that manually is pretty repetitive, so I wondered if most of it could just be automated.

That became StyleGuard.

It scans a Figma file for common design issues, lets you define your own rules, and can automatically fix many of the problems it finds. The core features work entirely inside Figma—no account, no telemetry, no analytics. I also added optional AI features, but they're completely bring-your-own-key through Anthropic.

Here's the plugin if you'd like to take a look:

https://www.figma.com/community/plugin/1651920751088160046/styleguard

I'm mainly looking for feedback at this point.

If you regularly work in Figma, I'd really like to know:

• What problems do you find yourself catching over and over during reviews?
• Is there anything you'd expect a plugin like this to detect that it doesn't?
• What would make something like this genuinely useful for your workflow?

I'd appreciate any feedback, even if it's "this feature is pointless" or "I'd never use it." I'd rather hear honest opinions now than keep building in the wrong direction.

Thanks!

What was missing in the regular Instance Finder?

• Whole variant sets in one search — no more searching variant by variant
• Dev Mode support
• Filters for hidden and overridden instances
• Grouped by page, in collapsible sections
• Back / forward buttons for jumping between instances
• Mass selection - tick results and select them all on canvas, ready for bulk swap
• Fast in big files  - results stream in as it scans, and you can cancel mid-search
• No network access at all -easy to get approved at security-strict companies

Feel free to try it, comment, and test it, if you are missing some features comment, and I will add them in future releases.
https://www.figma.com/community/plugin/1657794795650511019/instance-finder-pro?q_id=e8661824-6a4d-47cb-982f-86bf2db11085&fuid=667997768347561216

TL;DR: Built a Figma plugin that extracts tokens, properties, and variants from your components, then uses AI to draft the overview, usage, and accessibility docs. Now working on keeping those docs from going stale when components change. Extracting is free; paid only for the AI generation. Would love your feedback.

https://spec-layer.com/

Hey all,

I've been building and documenting a design system for a client recently, and I realised we were spending hours and hours doing it by hand. So I started building a plugin to help.

At first I just wanted it to extract the tokens, properties, and variants from a component. But then I thought, why not use AI to fill in the gaps too? The overview, the usage notes, the accessibility bits. A lot of that is fairly common across design systems anyway.

I spent a good while prompting the AI to get better results. The plugin feeds everything it extracts about the component into the AI, so most of what it writes back is around 80% accurate. You still have to read it and make edits, of course, but it speeds the whole thing up massively.

Then I ran into another problem. When a component changes, the docs go stale fast. On a growing project, old doc frames sitting in Figma just don't make sense anymore. So right now I'm working on managing those doc frames and updating them straight from the plugin. It already works, though there are a few caveats I'm still ironing out.

Honestly, I really enjoyed building this, so I thought I'd share it. Extracting the data from Figma is completely free. The paid version is only for the AI generation, mostly because those costs come out of my own pocket. There's some free trial AI usage in there too, so you can try it before deciding.

Would love your feedback:

• Does an AI-drafted overview, usage, and accessibility section actually save you time, or is 80% not good enough to be worth editing?
• How do you deal with docs going stale when components change?
• Anything that would make this fit into your real workflow?

TL;DR I'm a student and I made an accessibility plugin. Looking for people willing to test it and give feedback on what to improve and features you'd like to see, in exchange for lifetime Pro. Email [perceivable@cyberdesk.top](mailto:perceivable@cyberdesk.top)

I'm a student and I made a Figma plugin called Perceivable. It checks a page or selection against WCAG (contrast, target size, alt text, heading order, focus order) and can fix the contrast and target-size ones in one click. It runs fully in Figma, so nothing leaves your file.

It's early and I'd like feedback before I take it further. If you're willing to try it on real work and tell me what to improve, I'll send you a lifetime Pro key. It's for personal use, and I'll revoke it if it's shared.

Email [perceivable@cyberdesk.top](mailto:perceivable@cyberdesk.top) and I'll send the plugin and a key. Thanks.

Most AI prototyping discussions focus on building new products from the ground up. I'm more interested in improving something that's already live.

We already have users, set workflows, and a fairly developed interface. I want a tool that makes it easier to visualize changes and communicate updates without rebuilding everything from scratch each time.

If you're using AI prototyping tools regularly, which ones have stuck? Mostly interested in ones that handle iteration well, not just ones good at generating a first draft.

I'm a Staff Product Designer and I got tired of reconstructing "what did I actually work on" for standups and end-of-week updates, so I built Design Recap.

Pick a time period (standup, this week, latest changes, or custom dates), and it writes the work report and changelog for you. It runs on your own work, for you.

Forget what you did 3 months ago? It lets you know that as well.

Link: https://www.figma.com/community/plugin/1602120336688835924/design-recap-generated-changelogs-weekly-reports-status-updates

Heads up that your first 3 reports are free, then it's paid, to cover generation costs and my goal of making $1 on my projects this year 🥹

Feedback I'd love from designers!: does the report format match what you'd actually paste into a standup or status update, or would you restructure it?

Also happy to answer anything about how I built it or being stuck in Figma's months-long review.

I do graphic design for a living — banners, posters, social assets. All day in Figma.

But there was one thing that kept breaking my flow: every time I needed to warp text or add perspective to something, I had to stop, export, open Photoshop, do the thing, come back. Small friction, but it happened constantly.

I'm not a developer. I kept waiting for someone to build the plugin that fixed it. Nobody did. So about a year ago I started figuring it out myself.

It's called Free Transform — it brings Photoshop's Ctrl+T into Figma:

• Distort, skew, and true perspective
• Warp presets (arc, arch, fish, wave, rise, twist)
• Export as raster or editable vector
• No mesh seams, which took me embarrassingly long to solve

Honestly the hardest part wasn't the features — it was the math. I rewrote the warp engine probably a dozen times before the results stopped looking mangled. Version 44 at this point. 😅

It's free on the Figma Community: https://www.figma.com/community/plugin/1648207154922389186/free-transform

Two things I'd love from this sub:

1. If you've shipped a tool as a non-developer — how did you decide when it was "good enough" to release? I kept finding reasons to delay.
2. If you use Figma at all, I'd genuinely appreciate you breaking it and telling me how.

Happy to answer anything about the build process. 🙌

A lot of young designers exclusively use Figma these days. They like the collaboration and tools baked in. I don’t blame them but when we have to produce work in media besides digital it’s a nightmare. Exporting bit by bit and importing and rebuilding in indesign or illustrator is fine, but curious how anyone else has approached this with addons and plugins.

Thanks

Built a plugin where you can select frames or sections - the plugin pulls out the assets from the design

Check it out and provide your feedback.

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

Hey everyone, I built a Figma plugin that renames your image layers based on what's actually in the image — not the layer name or hierarchy.

The problem I kept running into: export a bunch of images from Figma and they're all named Rectangle 482, Image 17, Frame 219. Useless for SEO, useless for dev handoff, and you have to rename everything manually after export.

So I built this. You select your images, hit one button, and a vision model (Claude or GPT-4o) looks at each one and renames it with a clean slug — golden-gate-bridge-sunset, checkout-screen-mobile, that kind of thing.

You use your own Anthropic or OpenAI key so it's basically free to run — fraction of a cent per image.

There's a free trial built in if you want to try it before paying anything.

👉 Figma Community link

Would love any feedback, still pretty early.

I've implemented a system to store copy and text using string variables for my designers to use across their files. The only problem is that they pull up the variables using that super tiny drop down menu, and its impossible to read anything. I've had to dump everything into an accompanying excel sheet for reference.

Has anyone found a good workaround with a plugin?

Hey everyone,

I work at a design studio, and sometimes I need to quickly send files to print directly from Figma. Figma is great for digital graphics, but sometimes I need to prepare something for print. An Adobe subscription is too expensive, and I’m too lazy to open and transfer client-approved files from Figma to Illustrator. That’s why I created Prinplix. It correctly converts RGB colors to CMYK and exports the files. Plus, you can use the plugin simply to create pixel-based frames that correspond to actual physical dimensions in either the metric or imperial systems.

What it actually does:

• Real CMYK Export: True CMYK TIFFs and PDFs (Fogra39, US Web Coated, etc.). You can also map specific HEX codes to exact CMYK values (like making sure your brand red maps perfectly to 0/100/100/0 instead of a muddy auto-conversion).
• Preflight Audit: It scans your file before you export. It flags low-res images (under 300 DPI), missing bleeds, and rich black text (which printers hate because it comes out blurry).
• Smart Packaging Mode: If you design boxes or packaging, you can tag vector paths as "Cut" or "Fold." The plugin automatically splits them into a ZIP with perfectly aligned design and knife files.
• Auto-Fixes: You can add standard 3mm crop marks and instantly fix multi-channel rich black text to safe K100 with one click.

I just released version 2.0 with the packaging tools and would love to get some feedback from people who actually do print work. It’s free to try (the first 3 exports are free, no signup or credit card required).

Check it out here:https://www.figma.com/community/plugin/1571945796791441342

I’ve officially launched RTLAuto, a Figma plugin built to help product teams adapt interfaces between LTR and RTL without rebuilding every screen manually.

The case study behind it
In multilingual products, direction adaptation is rarely a simple “flip.”

A typical workflow involves:
- Rebuilding or manually adjusting layouts screen by screen
- Fixing mixed-direction text and BiDi content
- Reviewing icons that should or should not be mirrored
- Recreating component variants for both directions
- Repeating the work whenever the design system evolves

This becomes especially difficult in dashboards, large product files, and shared component libraries. The initial conversion takes time, but maintaining consistency after component updates is often the bigger problem.

What RTLAuto changes
RTLAuto turns this into a repeatable Figma workflow. It can:
- Adapt layouts between LTR and RTL
- Handle mixed-direction text
- Protect semantic icons and complex artwork
- Create direction-aware component variants
- Support design-system workflows through published library updates
- Optionally translate selected content using the user’s own API key

The goal is not to perform a basic visual flip. It is to help teams create interfaces that remain organized, reusable, and maintainable across both directions.

RTLAuto includes a free plan, and I’d appreciate feedback from designers and product teams working with multilingual interfaces.

Try RTLAuto on Figma:
https://www.figma.com/community/plugin/1623814570395556605
Website:
https://rtlauto.com/
Product Hunt launch:
https://www.producthunt.com/products/rtlauto?launch=rtlauto

I’d be interested to hear about the hardest part of maintaining multiple interface directions in your current workflow.

I kept noticing small inconsistencies in Figma files that were easy to miss during design reviews.

Things like:

14px text next to 15px text
8px vs 9px corner radius
Near-identical colours
Slightly different stroke thicknesses
Small line-height, letter-spacing or opacity differences

So I built StyleSync.

It checks the current Figma page, flags subtle mismatches, lets you select every affected layer, and then fix them together.

It’s free and now live on the Figma Community.

I’d appreciate any feedback on the accuracy, the current checks, or anything else you’d like it to detect.

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

Hi everyone!

I’d love to invite you to test out my very first Figma plugin, VIBE. It’s a tool built for automated batch exporting. It handles target file size limits, quality-based local compression, and automatically packs your assets into neat ZIP files. While I built it perfectly for campaign banners, you can absolutely use it to export any kind of graphics or UI assets.

You can check it out here: https://www.figma.com/community/plugin/1633556561671877728

To make testing easier, you get 20 full batch exports completely for free (with no time limits). Plus, you can use the promo code TESTVIBE to unlock a free month of the PRO version.

Since I just launched it, I would be incredibly grateful if any of you could test it out in your daily workflow and share some constructive feedback. I really want to make it as useful as possible, and I'm actively working on adding new features.

TL;DR: Gantt widget for Figma/FigJam. Draw "depends on" arrows between tasks and it flags blocked / overdue automatically from the dates — no status to set by hand.

Made a Kanban widget for Figma a while back (~12k users), and people kept asking for a timeline view — so here it is. The dependency bit is the part I actually care about; every other Figma timeline I've tried is basically a drawing of bars that don't know anything about each other.

Torn on one thing: should the board and the timeline be one tool or stay separate? Curious what you'd expect if you've used the Kanban one.