Showcase Your Work

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 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

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? 

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

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

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!

Hi everyone 👋I’m Hà, a graphic designer who works in Figma every day.Whenever I wanted to add a real sense of speed to a poster, product visual, typography piece, or social graphic, a regular layer blur was rarely enough. I needed a trail with a clear direction—sometimes straight, sometimes curved—and usually ended up switching to another tool just to create it.So I built Motiv Blur.Motiv Blur lets you turn almost any layer, group, or frame into a customizable motion trail without leaving Figma.How it worksSelect a layer, open the plugin, then drag the TAIL and HEAD handles to control the direction and length. Bend the path using Bézier handles, adjust the look of the trail, and click Apply.What you can control Straight or curved trails — shape the motion using an editable Bézier path Direction and distance — drag the endpoints or enter exact values Tail and head size — scale the trail from 10% to 200% Tail and head clarity — create an even trail or gradually fade either end T

Hi everyone. After months of building I published Flow Pro, a plugin that wires user flows directly in Design files. What it does:- Select screens, press Connect: every arrow is drawn at once, no crossings.- Arrows keep right angles and one of four shapes (straight, L, Z, U), so the diagram reads like a schematic, not spaghetti.- Move a frame and the wires follow live. Ports stay where you put them.- One style for the whole diagram: colour, thickness, corner radius, caps, dashes, labels.- Sections, components and instances work as nodes; hidden layers are ignored. Free to try (30 connectors). I would love feedback from people who map flows daily: what is missing, what feels wrong. https://www.figma.com/community/plugin/1666194024247251759/flow-pro-arrows-connectors-user-flows

Large PDFs exported from Figma can quickly become difficult to email, upload or share with clients. I built BatchPDF to create polished, highly compressed multipage PDFs directly from Figma.We have tested BatchPDF in a live, high volume marketing production studio where teams produce large photography and campaign production briefs.In one real production test, the same 52 page Figma document exported at around 90 MB using another well known PDF plugin. With BatchPDF, the result was approximately 15 MB while maintaining perfectly usable image quality. That is roughly an 83% reduction.BatchPDF includes simple presets for Print, Balanced and Small File. If you need an even smaller PDF, Custom settings give you direct control over image resolution in PPI and JPEG compression. This makes it possible to balance file size and image quality for each document.BatchPDF is built for designs that use your own custom fonts. Supported text can remain selectable and searchable, while vector elements

🚀 Invitation for Collaboration — Ruty Architect Project We are building the future of AI-assisted architecture. Ruty Architect was born to be an open and modular platform that unites Architecture, Engineering, BIM, GIS, Artificial Intelligence, Digital Twin and technical documentation in a single work environment.  Our goal is not to create just one more CAD or BIM software.  We want to develop an intelligent co-pilot for construction professionals, capable of analyzing projects, identifying inconsistencies, organizing documentation, collaborating with multidisciplinary teams and supporting technical decisions throughout the life cycle of a building. We are looking for people passionate about technology, design, engineering and innovation to participate in the construction of this ecosystem.  Engineering Intelligence for the Real World

Figma's export dialog stops at PNG, JPG, SVG and PDF — so getting web-ready assets usually means a chain of extra tools: convert to WebP elsewhere, compress, rename to a convention, sort into folders, zip. Featherlight does that whole post-export pipeline inside Figma, in one pass, entirely offline (zero network access, verified by the badge on the listing). - WebP / JPG / PNG (lossless or lossy) / SVG with a live before/after size preview- Every selected frame at 0.5x–4x in one run, automatic @2x suffixes- Rename patterns, kebab/snake case, slashes become real ZIP folders- Bundle as ZIP or one multi-page vector PDF Real run from the demo video: 9 frames to 18 WebP files, 9.12 MB down to 1.15 MB (-87%). 7-day free trial with every feature unlocked, then a one-time purchase — no subscription. It's a one-person indie project: I read every comment, and feedback and feature requests directly shape what gets built next. https://www.figma.com/community/plugin/1665932150476150859/featherlight

I found this amazing free, you just need page url and it will convert the website to editable figma design.You can see the detail in video guidehere you can find to website: https://page2figma.com/

Figma has no native way to apply opacity to an aliased colour variable without breaking the link and forcing you back to hardcoded hex values. To handle hover states, alert tints, or Material Design elevations, you are forced to bloat your library with dozens of duplicate variables.I built Sheer to solve this exact architectural bottleneck. It adds an automated, non-destructive opacity modifier layer to your workflow, here are its key features:  Token Mode: Type target steps (such as 8, 12, 20, 50) and instantly batch-generate clean, linked opacity scales directly from a base primitive variable. Quick Apply: Drop transparency onto individual component fills or strokes right on the canvas without polluting your library or breaking the core reference link. Smart Sync: If a master brand primitive changes, Sheer audits the file and repairs all dependent opacity tokens in a single click. Dev Mode: Automatically outputs production-ready CSS variables using native color-mix() syntax dir

I wanted to share a project I’ve been building solo over the last 4 months: TokenIgnite. It started with a simple question I asked myself: What if changes to Figma variables were visible in a running web app just as directly as tweaking CSS variables in browser DevTools? I built a proof of concept, but then had to ask myself an honest question: With Figma Code Connect, MCP servers, and Code Layers, who actually needs this? The Shift: Making Design Decisions in the Runtime FirstWith AI-driven workflows, layout code is generated faster than ever—yet LLMs lack visual awareness of the running app, causing design drift. At the same time, traditional token pipelines force teams to wait on builds just to validate minor tweaks. TokenIgnite introduces a paradigm shift: What if we make design decisions in the live runtime first before committing anything to a single source of truth? And what if we—and our AI agents—collaborate without any pipeline boundaries? How TokenIgnite works:TokenIgnite re

I work on Arabic and multilingual product interfaces, and I kept running into the same problem: converting an LTR design to RTL was rarely just a visual flip.Horizontal Auto Layout with Wrap is a good example. Reversing the child order can align the first row, but it does not reliably fix the direction of every wrapped row. It can also make responsive components harder to maintain.I built RTLAuto to handle this workflow inside Figma.Who RTLAuto is for:- Product designers maintaining Arabic and English versions- Design-system teams working with reusable components and variants- UX and UI agencies delivering multilingual products- Product teams building for Arabic, Hebrew, Persian, or Urdu markets- Anyone spending too much time rebuilding RTL screens manuallyIn version 1.3.1, the current conversion path has dedicated support for:- Horizontal Auto Layout with Wrap- Nested Auto Layout- Reusable components and direction variants- Responsive wrapping without absolute positioning- Directional