Rolling out: Projects become folders 📂 ✨
Show off your Figma projects and get feedback from the community.
Recently active
Hi everyone! 👋 A few months ago, I found myself repeating the same tasks in Figma over and over again. Copying text. Replacing images. Importing content. Populating layouts before presenting them or handing them off. None of those tasks were difficult, but together they were taking up a surprising amount of time. So I started building a plugin for myself. That project eventually became Super Paste, and after using it daily for the last few months, I thought it was finally time to share it with the community. Some of the things you can do with it: ✨ Bulk copy & paste text and images✨ Generate realistic placeholder text and images✨ Import CSV data and image collections✨ Populate text and images together✨ Copy & paste by group✨ Automatically detect nested layers✨ Save and reuse your content lists across projects✨ Populate large layouts in seconds One thing I’m especially proud of isn’t a single feature, it’s the amount of polish behind it. Most of the work went into handling edge
Hi Figma Community!I’ve made a hi-fi prototype for a plant care app - called Greener. For a Google UI/UX design course. Would love your feedback on it. Here's the Figma Link!
Create a UI/UX assignment file with 8 frames side by side:1. Instagram Login Page2. Facebook Login Page3. Instagram Information Filling Page4. Facebook Information Filling Page5. Instagram Registration Page6. Facebook Registration Page7. Google Homepage8. Instagram HomepageUse mobile frame size 375x812. Include logos, input fields, buttons, and navigation bars as described. Arrange frames horizontally with equal spacing.make like in picture
i am creating a website for a local restaurant in japan , called sushizen , this whole project is hypocritical and but i have followed all the ux process from empathy to testing although most of the steps were imaginary but i have learned a lot , i am doing this project alongside doing google ux professional certification , Figma link:- The problem :-many japanese salaryman and woking class visit the restaurant and during peak hours the restaurant is uable to maintain the customers . many tourists recently are visiting japan and want to experience traditional foods but find it very difficult to read menu and do conversation with the staff due to language barrier . nowadays the restaurant face competition from online food services . The Solutions :-Created a reserve table system in the website so that people can visit and experience it without hassle .Added a languages selector so that tourists can also access and experience the site and the food .Added Order Online services for people
Every time I finished a desktop layout in Figma, the same chore was waiting: rebuild the whole thing for mobile. Resize, restack, refit — by hand, screen after screen. I looked for a tool to speed it up and found the existing ones were either broken or abandoned.So I built Zeno.What it does — 3 tools:🔹 Adapt to Mobile — takes a desktop layout and generates a mobile version in one click🔹 Clean Up — fixes messy layers, spacing, and naming🔹 Prepare for Dev — flags handoff issues (detached styles, odd values) before you shipThe honest part (because I'd rather you trust it than feel oversold):Adapt to Mobile is around 70% of the way there. On clean auto-layout files it works really well. On freeform or messy files it still needs a human pass afterward. It's a strong starting point, not a magic finish — and I'm improving it with every piece of feedback.I interviewed designers while building this, and a lot of Zeno came directly from the pains they described. So if you work in Figma, I'd g
Hello community,Design systems tend to look clean in presentations. In real product work, they are often more complicated.Variables grow over time. Styles get renamed. Token structures change. Alias chains become harder to follow. Some values are still used somewhere, but nobody is fully sure where. And at some point, a simple list of variables is no longer enough to understand what is really happening.That is the problem we built Synapse for. Synapse is a Figma plugin that helps teams understand, review and maintain their design tokens directly inside Figma. It reads local variables and styles, resolves relationships between them, and turns the system into an interactive visual graph.The goal is simple: make the structure visible, so teams can make better decisions.Why we built itWe built this because we needed it in our own daily work.We wanted a better way to understand our token system, review its structure and support migration work without relying only on manual checks. We wanted
New plug-inHey community! I’m pleased to announce our new plug-in ‘Worried Presenter’. Worried Presenter listens to you present your work, then gives you back a confident, story-driven script with feedback — and tells you exactly how to improve. Here are the steps:How to useGiving you a better structure, clearer language, and stronger narrative arc.Import your frames from Figma Record your voice presentation Receive a new story-driven script and feedback Edit and re-record new runs to perfect it Listen to your feedback and new scripts from an AI voice Export your new enhanced script back into FigmaPlugin: https://www.figma.com/community/plugin/1647613618742509370Love to have your feedback!
👋 Hi everyone!I'm excited to share Design Audit Lens, a new Figma plugin built to help designers review their work more consistently and objectively.Instead of relying solely on subjective feedback, Design Audit Lens analyzes:✅ Research artifacts✅ Wireframes✅ UI screens✅ User-testing outputsIt evaluates designs using UX best practices, usability heuristics, accessibility standards (WCAG 2.2), cognitive load theory, and interaction design principles, then provides actionable recommendations to help improve quality.I'd really appreciate the community's feedback. If you give it a try, let me know: What you liked What could be improved Features you'd love to see next 🎨 Plugin:https://www.figma.com/community/plugin/1649498558808466087🌐 Website:https://designauditlens.comThank you for taking the time to check it out. Your feedback will directly influence future updates.#Figma #UXDesign #ProductDesign #DesignSystems #Accessibility #UXResearch #AI #DesignTools
Friday afternoon. The release branch is locked. Someone just updated the primary button hover state.The developer had already merged the update for button.css earlier that morning. Now I had to ping them on Slack to swap out #2563EB for #1D4ED8 before the final build. It is a tiny detail but it causes so much unnecessary stress.So I ended up building a small tool to stop this exact scenario.Now our Figma variables push a clean diff straight to a GitHub PR automatically. We completely deleted our token handover Slack channel and saved about three hours of manual code checks this sprint.I published Design System Sync for anyone else stuck in this loop.Figma Community: https://www.figma.com/community/plugin/1561389071519901700?utm_source=figma-forum&utm_medium=post&utm_campaign=botWebsite: https://ds-sync.netlify.app?utm_source=figma-forum&utm_medium=post&utm_campaign=botHow does your team handle last minute variable updates before a release?
Here is link to the plugin: https://www.figma.com/community/plugin/1582187505104489405/text-space-cleanerText space cleaner removes extra spaces from text layers in Figma. Clean up inconsistent spacing from copy-pasted content, imported text, or manual edits. Problem It SolvesExtra spaces in text layers are common and hard to spot:Double spaces from copy-paste or typos Leading spaces at the start of text Trailing spaces at the end of textThese issues are hard to see in Figma and can cause layout and alignment problems. Manually fixing them is tedious, especially across many layers.Text space cleaner automates this cleanup so you can focus on design. Core FeaturesRemove double spaces — Replaces multiple consecutive spaces with a single space (enabled by default) Remove leading spaces — Removes spaces at the start of text Remove trailing spaces — Removes spaces at the end of text Batch processing — Clean multiple text layers at once (works on selected text layers and text within selected
I kept running into the same hassle exporting images out of Figma: getting them out, compressing them and dealing with the different formats. I couldn't really find a free tool that handled all of it, so I made one. Putting it out here in case it's useful to anyone.It's called Hamster. You pick your frames and it can: - export PNG, JPG, WebP, SVG, PDF at whatever scale or size - compress PNG, JPG and WebP so they come out smaller - make a GIF or WebM from the frames - merge frames into one PDFLink: https://www.figma.com/community/plugin/1635433888954715176/hamster-export-compress It's still new, so if something comes out wrong or breaks, tell me how it happened and I'll sort it out.
Hi everyone 👋While working on design projects, I often needed 3D icons and illustrations that were:Editable inside Figma Exportable as pure SVG’s not Image embedded SVG’s Consistent in quality Fast to generate Most importantly , the dev teams required SVG files instead of png or jpeg for the graphics.One challenge I kept running into was SVG quality. Generated assets often contained missing details, broken paths, or incomplete vector exports, making them difficult to edit and use directly in Figma.So I built Image Trace VectorizerWhat it does ✅ Generate high-quality 3D icons✅ Create Visual 3D illustrations in multiple qualities✅ Export as SVG whenever possible✅ Preserve editability for design workflows✅ Fast generation without leaving Figma What makes it different?I built this after repeatedly running into the same problem: generated assets looked great in previews but often required manual cleanup before they were usable.Image Trace Vectorizer focuses on production-ready outputs, wit
I make event and raffle tickets now and then, and kept hitting the same wall in Figma: lots of plugins fill text from a CSV, but none of them actually number things properly or get them print-ready. So I built one.TicketForge does the part the others skip:• Real sequential numbering — {{n}} / {{n:0001}} with custom start and step (or no CSV at all: "500 raffle tickets starting at 1001").• A unique QR code per document.• One merged print-ready PDF — not a ZIP of 300 separate files.• Cut & stack imposition: it arranges the tickets so you print, guillotine the whole stack once, drop the piles on top of each other, and they come out already in 1-2-3 order. No hand-sorting 500 tickets.• 100% local — no network access, your guest list never leaves Figma.It's free up to 10 documents per batch so you can test it on your own template; $12 one-time unlocks unlimited (no subscription, no account, nothing uploaded).There's also a free template file to try it on if you don't have one yet.It's v
Im on week 3 of using Figma and just figured out how to duplicate a slide. So things are going great. I’m excited I’m being forced to use Figma.
Lately I’ve been experimenting with designing calculator-style tools using Figma before actually building them out in the browser, and it got me wondering: how do you effectively bridge static UI design with real, interactive logic?For context, I’ve been testing ideas on a small project (gagcalc.io) where the goal is to keep calculators fast, minimal, and actually worth revisiting.A few pain points I’ve run into so far:Static design vs dynamic behavior:In Figma, everything looks clean and controlled—but once real inputs and edge cases come in, layouts can break or feel inconsistent. Especially with variable-length outputs.Simulating real data in Figma:I’d love to preview how different calculation results (short vs long numbers, edge cases, etc.) behave inside the design itself. Right now it’s mostly guesswork or manually swapping text.Design-to-dev handoff friction:Things like spacing, responsiveness, and conditional UI (show/hide fields based on input) don’t translate cleanly from Fig
I’ve been struggling with creating linear tickets directly from FigJam board, so I ended up building a small FigJam plugin to remove some of that friction.The plugin lets you: Turn sticky notes, shapes, and frames into tracked Linear issues in seconds. Map common fields (title, description, project, assignee, labels) so you don’t have to retype everything. Keep a simple link back to the FigJam context so tickets aren’t divorced from the original board. It’s completely free to use (I don’t sell anything around it), and I built it mainly for my own workflow and a couple of other PMs who were tired of copy‑paste marathons. I’m sharing it here in case others have the same problem:Plugin link: https://www.figma.com/community/plugin/1582779918962363836/handoff-for-linearI’d really appreciate: Feedback on whether this actually fits into your workflow. Ideas on what would make it genuinely useful for product teams (e.g., templates, better defaults, extra fields). Edge cases where it br
Hi Figma Community,I'm part of the design team at Nimble AppGenie, and we recently completed a full UI/UX design project for a banking application. Figma was central to our entire workflow — from wireframing and component building to prototyping and developer handoff — so I wanted to share a few things we learned along the way.About the ProjectWe were working alongside our development team, which specializes in Banking Software Development, to design a feature-rich mobile banking app. The product needed to balance complex functionality — account dashboards, transaction histories, loan calculators, and multi-factor authentication flows — with a clean, intuitive interface that everyday users could pick up without a learning curve.How Figma HelpedWe built a shared design system with reusable components for form fields, cards, and navigation — this kept everything consistent across 40+ screens. Auto Layout saved us a significant amount of time when screens needed to adapt across different
A few months ago I published a Figma plugin to help designers, design system folks, and engineers work faster with colour in Figma.Colour is one of the hardest parts of a design system to get right and accessibility still tends to be guess-and-check: tweak, export, audit, repeat.Most of us are still stuck between two bad options:Manual tweaking: beautiful ramps in Figma, then hours checking pairs, fixing dark mode, re-exporting variables, and hoping nothing drifted. Industry-standard tooling: tools like Adobe Leonardo are powerful, but they were not built for day-to-day Figma work. Personally, it took me years to discover Leonardo's key colours. Worth it, but slow and complicated.What I tried to solveMost plugins and tools hand you a bunch of nice colours and walk away. Or they ask you to do the maths. I wanted to give designers time back to experiment, iterate, and play inside a system that is:Safe: accessibility handled by a proper engine, not eyeballing every stop Non-destructive:
Hey everyone 👋I often need to share long webpages with clients, review website changes, or put together documentation. The usual workflow — slicing screenshots and arranging them into pages by hand — always felt unnecessarily manual, so I built a plugin to automate it.SitePrinter lets you:- Import long webpage screenshots- Auto-layout them into A4, A3, Letter, or Legal pages- Arrange frames into 1–4 columns- Export presentation-ready PDFs in one clickIt's been especially handy for design reviews and client hand-offs, where you want the whole page in a clean, printable format instead of one giant scroll.Plugin: https://www.figma.com/community/plugin/1641026947708464856/siteprinterHow do you currently handle long webpage screenshots for documentation or client presentations? I'd love any feedback — what feels useful, and what's missing that would make you actually reach for it. 🙏
Our last design token migration touched 41 files. Two of them broke staging.We had 47 properties across 12 core components still using raw colour values. Someone had hardcoded #1E293B into a border instead of linking the surface variable. Finding all those unwired properties manually in Figma is a nightmare of clicking through nested layers.I got frustrated and built a way to fix this into Design System Sync.The new Connect Unwired tool detects every raw hex code and binds it to the matching variable automatically. We cleaned up the technical debt in our entire button library in about ten seconds. Then it synced the clean code straight to GitHub.Plugin: https://www.figma.com/community/plugin/1561389071519901700?utm_source=figma-forum&utm_medium=post&utm_campaign=botWebsite: https://ds-sync.netlify.app?utm_source=figma-forum&utm_medium=post&utm_campaign=botHow are you tracking down detached variables in your larger component sets?
Dear Figma Community,We all know the modern software tragedy. You find a neat plugin and immediately it demands a monthly subscription, your oldest child and a permanent internet connection to whisper your data back to some server.I grew tired of this theater. So I created three plugins that feel like they come from a forgotten digital utopia. They are entirely free, require exactly zero network connections and are so enterprise compliant that even your most paranoid IT security chief can sleep soundly. Your data stays exactly where it belongs, which is on your local machine.Here is my little trio for a better workflow:Vectrumhttps://www.figma.com/community/plugin/1614653112817958924/vectrum-generative-vector-patterns-for-designersBecause nobody should waste precious lifetime manually pushing vector points around. This tool generates parametric, highly complex geometric patterns directly as native vectors on your canvas. It is perfect for making your designs look sophisticated without
Hi everyone,I've been building BBUI — a Figma UI library designed to work seamlessly with AI agents and the Figma-to-code workflow. Heavily inspired by shadcn and Tailwind.After the first round of public testing I realized the variable naming wasn't aligned with Tailwind conventions, which matters a lot now that AI agents can read Figma metadata and generate code directly from designs. I've since rebuilt the variables system to follow Tailwind precisely, which tightens the handoff between design and code significantly.Beyond that, I've spent time on sizing consistency and whitespace so components scale cleanly across breakpoints.I've been using it on client projects and it's held up well. Now doing final polish before a Q3 2026 release.If you want early access, sign up here: https://www.boilingbrains.io/products/bbuiWould love to hear any thoughts or questions from the community.
In the past when building components, the hover and tap targets where always the same size as the component itself.For example, in a list where the hover or tap area should span the full width of the page, the component itself needed to be full-width.So to improve the life of our developers we wanted to transitions from using components with built in margin to allow setting the margin externally. However, the challenge was how to ensure the component would still have a hover/tap target that spanned the full width.I couldn’t find any suggestions online, but after a lot of fiddling and hacking, I discovered a surprisingly simple solution.I wanted to share it here in case others have faced similar challenges:Solution Step 1: Create a layout using auto layout so that the component can scale as needed based on the content. Add the state as it’s own layer and set the position to absolute.For each variant you can change the state as you would normally change the background. Step 2: Set the la
Hey everyone,I had a conversation with a user who got stuck at a step I thought was obvious. It wasn't.That was enough to finally start the revamp. Before I change anything though, I'm collecting real usage data, would love for you to try it and tell me what feels confusing or broken.What the tool does: Drop an image or brand color → it generates a complete starter design system and outputs a plugin script you paste into the Figma console. What gets created in your Figma file:Color variables (50–900 scales), synced with tokens Typography text styles Button variants (40 total: 4 types × 2 sizes × 5 states) — all bound to the color variables so updating the palette propagates automaticallyWhy it might be useful: Design system kickoffs usually mean manually wiring up 60+ variables every time. This skips that step entirely.Try it free: https://designsystem-generator-bbs.vercel.app/Demo: https://youtu.be/meP4kaoAeMAIf anything feels off or confusing: reply here or DM me. That feedback is ex
Hey everyone — I wanted to share a Figma plugin I’ve been building called Variate.It’s designed for people doing repetitive production work like paid social ads, email campaigns, lifecycle design, etc.The workflow is simple:- map text layers once (HL, SH, CTA, or custom fields)- paste multiple hooks/offers/CTAs- generate lots of clean text variations automaticallyThe goal wasn’t “AI magic,” but removing the repetitive frame duplication and text-swapping that eats up production time.I made this short demo walkthrough showing the workflow in action.Would genuinely love feedback from people who work in high-volume design workflows:- what feels useful?- what feels missing?- what would make this something you’d actually use?Plugin:https://www.figma.com/community/plugin/1637012532167731648/variate(Free to try)More info at http://variate.designance.co
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.