Connect with other community members, share your work and get inspired.
Recently active
Convert public or private pages from web to Figma designs.Get the official Chrome Extension:https://chromewebstore.google.com/detail/lcbapmgigajdpechghjnkbaidfhenbhlUse the browser extension to capture pages you can access in your browser, import them into Figma, and rebuild them as an organized design foundation withstyles variables auto layout high resolution imagesIf you encounter issues or want to share feedback use my public issue tracker:https://github.com/evgeniiarts/web-import-masterDemo: https://youtu.be/Ms3HrUkAosc
Hi Figma Community — I’m building Layer3D, a free Figma plugin that turns selected frames into editable 3D scenes in the browser.Below is a direct before-and-after example using the same UI kit.BEFORE — flat UI kit in FigmaAFTER — editable 3D scene in Layer3DHOW LAYER3D COMPARES JITTERJitter is a strong choice for fast, polished 2D motion design. It imports Figma layers, offers animation presets plus timing and easing controls, and exports formats such as MP4, WebM, GIF and Lottie. I would choose Jitter when the goal is a UI animation, social post, product demo or motion graphic and I do not need a real 3D scene. Layer3D focuses on a different step: converting the visual hierarchy of an existing Figma design into a spatial composition. I would choose Layer3D when I want to separate interface layers in depth, move a camera around them, add lighting and materials, and create a dimensional product visual without rebuilding the design in a traditional 3D tool. FIGMA MOTIONFigma Motion is t
Hello everyone,I would like to share a thought about how we build value around a design tool today: shipping a plugin, or driving the tool with an agent (MCP server, skills, a local or hosted LLM).This is a subject I am directly concerned about. I build plugins, and I spend most of my time trying to make plugin building reachable for more people, so that anyone can cover one precise use case and keep control over what it costs. I would welcome your feedback.TL;DRA plugin is an act of service: the load is carried once, by its author, for everyone who installs it, and the cost sits at the start. An agent is a way to build through your own prism: immediate, personal, shaped exactly as you think, and billed every time you run it. My working hypothesis is agents to explore, plugins to produce. What I would like to discuss is where each of us draws that line, and what it changes for Figma.If you want the longer version, here are the slides of the 10 minute talk.ContextFor years, packaging va
Update rather than a second launch: BatchPDF now supports Figma Buzz in the same plugin used for Figma Design.The current workflow can export selected frames, components, instances and Buzz assets. Before export, the page organizer lets you review the selection and drag pages into the order needed for the final PDF.The latest version also improves font handling. BatchPDF can detect installed fonts and Adobe Creative Cloud fonts where licensing permits embedding. When a font cannot be embedded safely, Smart fallback protects the visual result instead of making a universal text-preservation promise.Current highlights:- Figma Design and Figma Buzz in one plugin- Drag-to-reorder page organizer- Print, Balanced, Small File and Custom export controls- Acrobat viewing-mode options- Selectable/searchable text where supported- Clean vector artwork can remain PDF objects- Smart appearance fallback for unsupported fontsThe free plan includes five successful exports, with up to 100 pages in each e
If you have a PSD/Figma file that usually gives converters trouble, I’d love to know what breaks.
AI-assisted product UI often fails before styling: the primary task is unclear, every region becomes an equal-weight card, important interaction states disappear, decorative visuals have no product role, and mobile becomes a compressed desktop layout.I built Product Design Director, a free and open-source Custom Skill for the Figma agent. Invoke it with /figma-product-design-director.It asks the agent to work through product context, hierarchy, task-led layout, visual-system decisions, component states, responsive priority, interaction, motion, accessibility review, and a final critique.The critique format is intentionally practical:Observed condition → user impact → smallest reasonable revision → recheck the complete flow.I also ran one controlled paired example using the same starting frame, brief, target frames, and visible runtime configuration, with Skill invocation as the planned variable.The result was mixed: the Skill-assisted desktop preserved the supplied content more faithfu
Hi everyone! I just released my first plugin and wanted to share it here.Web Behavior Preview opens a Figma page as a real scrolling webpage: sticky headers pin and stack under each other, sidebars ride along with the content (the Airbnb-style pattern that native sticky can't do), bottom bars push each other up, and the clicks, hovers and overlays you already wired in the Prototype tab come along. One button exports the whole thing as a single self-contained HTML file you can send to a client instead of explaining the behavior in words.Free, no network access, nothing to configure.Plugin: https://www.figma.com/community/plugin/1676379978276045790/web-behavior-previewPlayground file to try it on: https://www.figma.com/community/file/1676368484360559450Would love feedback — especially if you hit a layout where it guesses the behavior wrong.
Hi everyone 👋I’m a solo developer looking for 3 people who already use Figma Buzz Bulk edit for campaign variants.I built BuzzFlow, a private-beta plugin that:checks campaign assets for obvious missing fields creates clean filenames from connected Buzz fields exports every valid asset into one ZIP runs locally with no external network access never uploads campaign data never modifies the Buzz documentIt has been manually tested on Figma Desktop for Windows with a campaign containing 100 Ready 1080×1080 assets.The beta currently installs as a development plugin from a local manifest, so it has not yet gone through the public Figma Community review process.I’m mainly looking for honest feedback about:installation filename patterns ZIP export reliability confusing parts of the interface how much manual work it savesPlease start with a non-sensitive campaign.Beta testers will receive the finished version free. Reply interested and mention approximately how many variants you normally creat
Hi everyone,I recently published a Figma plugin called DesignPorter.The idea came from a problem I kept running into while working with design systems: exporting variables is useful, but a real design system is more than a list of raw values. It also includes modes, aliases, styles, bindings, and the relationships between them.So I built DesignPorter to make design systems more portable.It can currently:Export Figma variables and supported styles as structured DTCG JSON Preserve supported modes, aliases, and bindings Import a DesignPorter JSON into another Figma file and rebuild the supported structure Export an AI-ready design.md containing tokens, styles, modes, relationships, and usage guidance for coding/design agents Run locally without sending design-system data to an external serverI’m a Product & Brand Designer working in DesignOps, not a traditional software engineer. The original concept, product direction, UX, and brand were created by me, and I used AI as a development
Need TRC and NO-PE document for compliance. Please help
Hi guys now i’m working on built the plugin for documentation design system, so you can just select component and click generate and voila!!, design system now is documented. I want to know do you guys want to try the plugin?, Or perhaps you have any suggestions?
貴社サポートチームよりダウングレード通知を受け取りました。指示によると、ダウングレードを進める前に複数のチームを1つに統合する必要があるとのことです。しかしながら、このプロセスには追加の時間が必要となり、8月30日の更新日までに完了できない可能性があります。更新日までにダウングレードが完了しない場合、ビジネスプランの料金は請求されますか?この点についてご説明いただければ幸いです。ご協力ありがとうございます。
Figma native export: 22.7MB → Featherweight: 4MB I’m a frontend developer based in Korea, and I work closely with designers who use Figma every day.I also use Figma myself for things like portfolios and other document-heavy layouts, and one thing that kept bothering me was PDF export. Even relatively simple, text-heavy files could end up surprisingly large.Since I’m a developer, I got curious and took a closer look at the exported PDFs. I found that a lot of the file size came from image handling and from Figma converting text into vector outlines instead of embedding the actual fonts.I tried a few existing PDF export and compression plugins, but many of them were paid, subscription-based, or had limitations that didn’t quite fit what I wanted.So I ended up building my own.Featherweight exports PDFs with real embedded and subsetted fonts where possible, keeping text selectable and searchable instead of turning everything into outlines. It also compresses images along the way to reduce
I've been designing in Figma for about ten years and I still don't name my layers. Last week I opened a file I made myself and the panel was Frame 234, Group 12, Text 4, Rectangle 89. So I built a plugin instead of fixing my habits, and I've just published it. It's free. It does three things. 1. Renaming. Text layers become "Role: Content" - Heading: Authentic BBQ Experience, Button: View Portfolio, Link: Privacy Policy. The role is not parsed from the existing name, it comes from structure: Link from Figma's own hyperlink property, Button from sitting inside a small rounded auto-layout parent, Heading from 28px or larger, Subheading from 20-27px, Label from three words or fewer, Body for 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. Scopes are selection, page
What if your Figma file was the actual source of truth and the codebase just auto-followed?I am Alexander and I created a plugin to test this idea after our team spent three weeks arguing about spacing tokens. Someone kept using 16px in the React components while the design system clearly said our spacing-md was 12px. The manual translation between our local variables and the GitHub repository was causing constant friction.So I made a tool that just pushes Figma variables straight to a pull request.That one change deleted an entire Slack channel dedicated to UI bugs. It also saved us roughly four hours of manual code reviews every single week.You can grab Design System Sync on Figma Community: https://www.figma.com/community/plugin/1561389071519901700?utm_source=figma-forum&utm_medium=post&utm_campaign=botCheck out the website here: https://ds-sync.netlify.app?utm_source=figma-forum&utm_medium=post&utm_campaign=botHow do you currently spot drift between your Figma varia
So I took the absence of figpals into my own hands and gave one of them a facelift.Dis Dennis.
Hi Figma community,I’m a product designer and I built Source → Design after repeatedly running into the same workflow problem:AI tools and frontend teams can create a working interface in HTML or React very quickly, but bringing that result back into Figma usually means rebuilding it manually.Source → Design converts HTML and frontend project files into clean, editable Figma designs with structured layers, text, colors, typography and layout preserved.It supports HTML, React, Next.js, Vue and Svelte projects.The goal is simple: make it easier to keep iterating in Figma when the interface already exists in code or the original Figma file is missing.I’d genuinely love feedback from designers and frontend teams using real projects.→ Try it here:https://www.figma.com/community/plugin/1671982756700161071→ More details:https://sourcetodesign.com
hy fellow designers, I've recently started working on figma, and right now i am on my first heuristic project. would appreciate some insights from you guys and it would be lovely to connect and learn and maybe work together..If you're learning and in for the same,, drop me a heyo <3.
Hey, I’m Rishabh, founder at Waysorted.We are making a design Ops toolkit that kills the repetitive, unglamorous parts of design work. We’re small, so the Discord is where requests actually turn into shipped features.Join our Discord to share work, swap workflows, and connect with top designers using the same tools.→ https://discord.com/invite/U2XF76WxNv
Hey everyone — I’m the developer behind Shape Forge 3D, a local 3D design studio built directly into Figma.It started with a simple frustration: I wanted to turn an SVG, logo or a piece of type into a polished 3D visual without opening Blender, sending assets to a renderer or rebuilding the same thing in another app.With Shape Forge 3D, you can start from a built-in shape, icon, your own SVG or custom text — then turn it into an art-directed 3D object right on the canvas.You can create:• extruded SVG logos and symbols• chrome, glass, gummy, clay and holographic 3D icons• 3D typography, Y2K titles and dimensional lettering• custom 3D objects from your own vector shapes• 4K transparent PNG renders for presentations, campaigns and social visualsThe latest update adds 2,929 curated SVGs across 11 libraries, including Y2K+, Brutalism, Retro Future, Blobs and Line Art — plus your own persistent SVG library and direct vector import from the Figma canvas.Everything is processed locally: no clo
Right now, it contains five utilities I originally built to solve problems I kept encountering in my own design work:Normalize inconsistent property values Add controlled variation Build components and variants Distribute layers along paths Save and restore selectionsIt’s meant for the small jobs that shouldn’t eat an afternoon. I’d really appreciate any feedback re: what feels useful, what feels confusing, what just doesn’t seem to be working, or what repetitive Figma tasks I should tackle next.[ Aaron's Toolbox in the Plugin Store ]Playground:
Hi everyone — I just published my first plugin and would love your feedback. **html2figma** converts a dropped .html file into native Figma layers: - Real text layers with font family, weight, size, line-height, letter-spacing and alignment- Fills, linear/radial gradients, borders, per-corner radii, shadows and blur- Inline SVG imported as editable vectors- Pixel-faithful positions read from the browser's rendered layout — flex, grid, floats all land exactly- A tidy layer tree: wrapper divs collapsed, layers named semantically (Section, Button, or by text content)- Full RTL support — tested on complete Arabic pages Privacy: everything runs locally in the plugin; your file is never uploaded. Tip: to import a live site, save it with the SingleFile browser extension first, then drop the file. Direct URL import is on my roadmap, along with batch import. Install: https://www.figma.com/community/plugin/1668745510469345388Site: https://html2figma.com I'll be in the comments — bug reports and
Hi everyone,I’m working on the UX/UI of a mobile app called KertApp, designed to help pet professionals keep health information organized in one place.The main challenge I’m exploring is how to make health information easy to manage for people such as breeders, veterinarians, farriers, horse professionals, and other pet-care providers.The app needs to handle different types of information, including:Vaccination and treatment records Health reminders and upcoming appointments Growth and activity tracking Reproduction-related information Pet and owner contact details Sharing relevant health records with other people involved in the animal’s careFrom a UX perspective, I’m particularly interested in the balance between having enough information available and keeping the interface simple. A professional may manage information for multiple animals, but they still need to find an individual animal’s important health information quickly.I’m currently thinking about questions such as:Should the
I’ve been exploring how digital content can make everyday personal care decisions easier for parents, and choosing a first deodorant for a tween is an interesting example.There are many products available, but the information parents need is often scattered across ingredient lists, product descriptions, reviews, and marketing claims. From a UX perspective, this can create a lot of decision fatigue.For a content experience about deodorants for tweens, I think the interface should focus on helping parents make a decision rather than pushing them toward a particular product.A few design ideas I found useful:1. Start with the questions parents actually askInstead of beginning with a long product list, the experience could answer questions such as:• When might a child need deodorant?• What should parents look for in a deodorant?• What ingredients may be worth paying attention to?• How should parents approach sensitive skin?• What is the difference between deodorant and antiperspirant?2. Use
Lately, I've been pushing myself to explore what's possible with Figma Motion and see just how far I can take animations without leaving Figma.I recently came across a really smooth WhatsApp animation and thought, why not recreate it? So I challenged myself to build it from scratch, paying close attention to the timing, easing, and micro-interactions.It's been a fun way to learn, experiment, and sharpen my motion design skills.How do you think it turned out? 👀Check it out!I'd love to hear your feedback!
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.