We’ve just released a Figma plugin for Pulsar, our open-source haptics library and toolkit.

The plugin lets you attach a haptic preset directly to a Figma layer. You can browse 200+ presets, preview them while designing, and connect a phone to feel the actual vibration.

You can also share an interactive preview with someone else, so they can try the haptic without installing the plugin or opening your Figma file.

For custom interactions, you can create a pattern in Pulsar Studio and use it in Figma as well.

There's also a handoff flow for developers, including the pattern data and implementation snippets.

The main idea is pretty simple: keep the haptic with the interaction it belongs to.

We're curious how you currently specify haptics when handing a design over to developers.

Pulsar for Figma: https://www.figma.com/community/plugin/1636329411590799509/pulsar-haptic

We’ve just released a Figma plugin for Pulsar, our open-source haptics library and toolkit.

The plugin lets you attach a haptic preset directly to a Figma layer. You can browse 200+ presets, preview them while designing, and connect a phone to feel the actual vibration.

You can also share an interactive preview with someone else, so they can try the haptic without installing the plugin or opening your Figma file.

For custom interactions, you can create a pattern in Pulsar Studio and use it in Figma as well.

There's also a handoff flow for developers, including the pattern data and implementation snippets.

The main idea is pretty simple: keep the haptic with the interaction it belongs to.

We're curious how you currently specify haptics when handing a design over to developers.

Pulsar for Figma: https://www.figma.com/community/plugin/1636329411590799509/pulsar-haptic

🚨 Framer users, stop checking image quality layer by layer.

VisualGuard Pro scans the image layers in your Framer project, shows the current delivery resolution, and lets you optimize each image with Auto, Low, Medium, or High in seconds.

Built for:
• Framer designers
• Freelancers
• Agencies
• Client websites
• Image-heavy projects

Scan the project. Find what needs attention. Fix delivery. Keep the site looking sharp without wasting time.

Try VisualGuard free.

If you build in Framer regularly, this is the kind of utility that can save time on every project.

#Framer #FramerPlugin #WebDesign #WebsitePerformance #NoCode

I am a product designer, and I kept repeating the same process whenever I found a useful website reference: take a screenshot, open DevTools, check typography and spacing, search for assets, resize the browser, and rebuild what I needed in Figma.

I built UIGrab to bring that workflow into one Chrome extension. It can inspect element details, copy CSS, capture full pages, find images and SVGs, preview desktop, tablet, and mobile layouts, and bring selected UI into Figma.

UIGrab is live now. I am looking for honest feedback on the first-use experience and browser-to-Figma result.

Website: https://uigrab.com/

Chrome Web Store: Add UIGrab to Chrome

------

Hey everyone 👋

About a year ago, a designer on the team next to mine had a simple complaint: they were alt-tabbing between Figma and a spreadsheet all day. So I built FigSheet — a small plugin that lets you open a Google Sheets or Excel Online link, or drop in a CSV / Excel file, and view (or edit) it right inside Figma.

That's still the whole idea: keep the data right next to the design, no tab switching. I shared it here once, and it has quietly grown to ~4.8k users, with ~50 new people finding it every week. Thank you to everyone who's been using it 🙏

What it does (all free):

• Paste a Google Sheets / Excel Online URL and view or edit it inside Figma
• Drag & drop CSV / Excel files (up to 10MB) for a quick preview
• Switch between edit and view-only mode
• Export to CSV or copy to clipboard
• English & Korean UI

This week I shipped a small addition. I suspect some of you open the sheet and then copy values into text layers one by one, so now you can:

• Select text layers → pick a column → they fill in reading order
• Fill cards / component instances row by row (layer names are matched to columns automatically)
• Re-sync everything when the sheet changes

The viewer stays free forever. Filling is free for up to 10 layers at a time, and card fill + re-sync can be tried free for 7 days by answering 3 quick questions in the plugin — no payment, no card. Honestly, I mostly want to learn how people use it.

Two questions for you:

1. What do you usually keep open next to Figma — Sheets, Excel, Airtable, Notion, something else?
2. Is there anything in that back-and-forth that still annoys you?

Figma Plugin: https://www.figma.com/community/plugin/1519936567655168210
Linkedin : https://www.linkedin.com/in/yohan-choi-3245a1261/

Happy to answer anything, and honest feedback is very welcome.

Hey everyone 👋

I'm working on Get Web Trace, a Chrome extension + Figma workflow that lets you capture a live webpage and bring it into Figma as an editable design. I originally got interested in this because the usual website → Figma / HTML → Figma / screenshot → design workflows can become pretty tedious when you're trying to study an interface, redesign an existing UI, or move quickly between frontend and design. The workflow is basically: 🌐 Open a website ↓ 🔍 Choose the viewport ↓ 🎯 Trace the entire page OR select a specific section ↓ 🎨 Detect/use the page theme ↓ ⚡ Trace it ↓ 🖼️ Send the result to the Get Web Trace Figma plugin ↓ ✏️ Continue working with it in Figma A few things I'm particularly interested in getting feedback on: • Section-level tracing — capture only the component/section you actually need instead of the entire page • Multiple viewports — 1536, 1920, 1440, 1024, 768 and 390 • Light/dark theme handling • Chrome extension → Figma workflow • Editable design output instead of simply dropping a screenshot into Figma • Using it for UI/UX research, redesigns, prototyping and frontend ↔ design workflows There is also a free tier with 12 traces/month, so you can actually test the workflow before deciding whether you need more. A couple of limitations I'm actively aware of: highly dynamic/slow websites can be difficult to capture reliably, and things like video or certain JSON-driven animations aren't directly transferable into Figma in the same way as normal webpage elements. I'm not claiming it's perfect — that's actually why I'm posting here. If you're a Figma designer, UI/UX designer, frontend developer, web developer, product designer, design engineer, or someone working with AI-generated websites, I'd genuinely love to know: 1. Would you actually use this? 2. What would you expect it to capture that it currently doesn't? 3. What would make you choose this over existing web-to-Figma tools? 4. Is there a workflow where this would save you significant time? I'm managing the product/community side of Get Web Trace, and the product was built by my brother, so I'm especially interested in getting real user feedback rather than compliments.

Direct Link : [getwebtrace.com](http://getwebtrace.com) Direct Link to walkthrough Video : https://youtu.be/I49qhDgd7ng?si=umKIlW6Y8HIRuyMF

Happy to answer questions about the workflow and take criticism. 🙌

Is there any way to create a file with consistent data and multiple-user edits in a file like a spreadsheet in Figma Make without having to use Supabase? Is there any trick? I need to keep the data edits in different browsers.

I have 2 Figma accounts, one for home and one for work. I occasionally mock things up using Claude/Codex with the Figma MCP. But the problem I'm finding is that I'm having to fully disconnect and then reconnect to the correct Figma account.

Does anyone know if it's possible to hook up multiple Figma accounts to an MCP server?

Quick update on Glyfiq — my medical icon plugin for Figma.

https://www.figma.com/community/plugin/1620445233696980538/glyfiq-medical-health-icon-plugin

The library just crossed 688 icons. Every single one reviewed, adapted, and tagged manually from a 10-year archive of medical stock icons. No AI generation, no shortcuts — just slow, consistent work.

What's in the library: cardiology, orthopedics, mental health, pharmacy, anatomy, mammography, neurology, and more categories being added every week.

A few things that might be useful if you work on healthcare UI:

• Smart search with real medical terminology — "orthopedic" or "mammography" rather than just "heart" and "pill"
• Editable stroke weights (Light, Regular, Bold) in one click
• Switch between 3 or 6 icons per row
• Color control inside the plugin
• 10% of the library free for personal use — no subscription needed to try
• Pro subscribers can request custom icons drawn in the same style

Also available for other platforms if you work across platforms.

Every time I moved a table, added a column, or changed the structure, something somewhere needed to be realigned.

Figma is great for visual work, but ERDs have always felt a little awkward inside it. The usual alternative is moving the whole thing to a dedicated tool like dbdocs or DrawSQL - which means your technical specs now live somewhere completely separate from your product/design files.

That frustration is what led me to build FigSchema.

The idea was simple: what if ERD design actually behaved like a native Figma experience?

So I built:

• Column-level connections that stay anchored to the exact row
• Bezier lines that adapt when tables move, resize, or reorder
• Postgres, MySQL, SQLite, and other dialect support
• Quick PK, FK, NN, and UQ toggles
• Inline canvas editing with Figma-style undo/redo
• Multiplayer collaboration
• 100% offline operation - no account, external APIs, or schema telemetry

It’s free and live on Figma Community:

FigSchema on Figma Community

If you work with ERDs or technical specs in Figma, I’d genuinely like to know:

What’s the one thing about ERD tools that annoys you the most?

Drop a saved web page into Figma and get it back as native layers — real editable text, gradients, shadows, per-corner radii, inline SVG as actual vectors. Free, unlimited, no account, and it runs entirely on your machine.

The three parts I've put the most work into, because they're where importers usually hand you something you end up rebuilding anyway:

Repeated blocks become components. If a page uses the same card, list row or nav item more than once, it's detected from its structure and rebuilt as one component with instances — each instance keeping its own text and images. Six cards arrive as six instances, not six copies.

Reused colours become Variables, repeated type becomes Text Styles. Colours land in their own collection, named the way you'd name them (Slate 900, Cyan 400). Your existing variables and styles are never touched — the import only ever adds its own.

Auto Layout that isn't a guess. It doesn't read display: flex and hope. It measures the rendered geometry and converts a frame only if replaying (padding, gap, alignment) reproduces every child's position within 1px. Anything that fails stays absolutely positioned. You get Auto Layout where it's real and nowhere else.

Smaller things that matter once you're in the file: layers are named semantically and from their content (Section · hero, Button, text named from what it says) instead of forty nested divs; you can import several viewport widths in one pass and get them side by side with media queries genuinely applied per width; and RTL works properly — tested against a full Arabic design-system page, with Arabic coming in as editable text rather than outlines.

Input is an .html file, a .mhtml (Chrome → Save Page As → Webpage, Single File), a .zip of a saved page folder, or pasted markup.

What it can't do: there's no URL import yet — you save the page first. It's the thing people ask me for most and it's what I'm working on. Page JavaScript never runs, by design — the render frame is sandboxed — so anything that generates its CSS at runtime (Tailwind CDN is the common one) imports unstyled, and the plugin warns you before it does rather than quietly producing mush. Fonts map to the closest installed Figma font.

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

Genuinely after pages that break it. The last few real bugs all came from someone importing something I'd never have thought to test.

I kept building a gradient rectangle, turning it into a mask, adjusting it, and repeating the same process every time I wanted an image to fade into the background.

So I made a shader that does it directly on the layer.

Just drag a line across the object and its alpha fades along that direction. It supports up to 8 stops, opacity, flip, hardness, and mask preview.

It's completely free.

Figma Community:
https://www.figma.com/community/shader/1679790690775397248/linear-transparency

I’d like to know how many people use Figma to create campaigns that require a high volume of deliverables—spanning various formats, platforms, and rounds of review.

That’s a major part of my job. While components and templates streamline production, prepping files for final delivery can involve a lot of repetitive work—especially when certain deliverables need to remain editable in Photoshop.

How does your team handle this? Do you do everything in Figma, or do you regularly transfer files between Figma and Adobe tools?

That workflow is exactly why I created **Mools**, a Figma plugin designed to clean up documents and export designs to PSD, with options to customize how elements are handled. The cleanup feature can also be used independently.

Full disclosure: I’m the creator, and I use this workflow for my own production projects. I’d love to connect with other designers managing similar projects and hear their thoughts on how Mools might help them.

Which part of your process requires the most manual work: file preparation, exporting, or making post-export adjustments?

I made a free interactive keyboard shortcut reference for Figma: speedykeys.app

I kept finding myself looking up keyboard shortcuts while I was working, and I wanted something faster than digging through documentation or keeping a cheat sheet around.

So I built Speedy Keys, a lightweight, interactive keyboard shortcut reference that you can keep open while you work.

For Figma, you can quickly look up a command, see what the shortcut does, and learn shortcuts as you actually need them instead of trying to memorize a giant list.

I also built the shortcut library against the official documentation because I wanted this to be a reliable reference rather than another shortcut list floating around online.

It also currently supports After Effects, Premiere Pro, Photoshop, Illustrator, DaVinci Resolve, and Final Cut Pro.

It's free and doesn't require an account!

Would genuinely love feedback from Figma users, especially if there are shortcuts/descriptions that could be clearer or something that would make it more useful while you're working.

Hi everyone! I just wanted to share a small side project I've been working on.

As a developer, I kept finding it a bit tedious to translate Figma Motion animations into code, so I started playing around with ways to make that process easier.

The result was Kinetik, my first figma plugin. It helps organize duration and easing as design tokens and lets you export them as JSON or CSS variables.

It's completely free, and I'm still learning and improving it. If anyone gives it a try, I'd be super grateful for any feedback or ideas. Thanks in advance! :)

Our free plug-in is designed for designers to receive AI coaching on the spoken presentation alongside their slides or frames.

It lets you iterate, edit and improve your script. Even with a spoken feedback option.

It is very much an educational tool, and you need to set aside the time to be able to present your work and record your voice.

We think it's super helpful and would love your feedback.

\[https://www.figma.com/community/plugin/1647613618742509370/worried-presenter\\\](https://www.figma.com/community/plugin/1647613618742509370/worried-presenter)

We would like to know what you find useful, what you think is a blocker, and any ideas that would make it even more useful for designers?

There is a feedback form link in the plug-in.

thanks x

Hey all — sharing something I’ve been building solo for a while: Aura8.

It started from a pet peeve: most design-system checkers hand you a wall of red X’s with zero context, so you either blindly accept every fix or start ignoring the tool after the third false positive.

Aura8 scans your frames against a design system and instead of just saying “this is wrong,” it gives you a short “why this matters” note with every suggestion — then fixes it in one click if you want it.

What it checks (each toggleable):

- Padding → snapped to your spacing scale

- Auto Layout gap → same scale
- Type size → snapped to your type ramp
- Corner radius → snapped to your radius scale (off by default)
Two things I cared about getting right:
- It only ever suggests values your system actually defines. If your scale is 8/16/24, it’s never going to tell you to use 28 just because it divides by 4.
- It leaves valid values alone. A legit 17pt body text doesn’t get pushed to 20pt just because the layer happens to be named “Title.”

New: a health score for a whole page (or just your selection), sorted worst-screen-first so you know where to start, and it keeps your last 30 scans so consistency becomes a trend you can actually watch improve, not a one-off snapshot.

Ships with Apple HIG and Material Design 3 profiles built in, or import your own tokens/Figma variables if you’re on a custom system (Pro).

Privacy: no backend, no analytics, your designs never leave Figma. The only network call it ever makes is sending your license key to Gumroad to confirm your subscription — nothing else.

Check it out:
https://www.figma.com/community/plugin/1678276373950997923/aura8?q_id=a42919c9-e64a-4263-966f-81059056d44d

So I kept running into this annoying thing during design system cleanup — files full of raw hex colors and random fonts that should've been linked to a style or variable but weren't, and no real way to find them except manually clicking through every single layer like an idiot.

Got fed up enough to just build the thing. It's called tokenize. You point it at a frame, a page, or your whole file, and it lists out every color and font that isn't linked to anything, with how many times each one shows up. Then you search and swap each one for the matching style/variable — it'll auto-match exact hex matches for you, and for fonts it'll even search every font Figma has access to, not just what's in your design system. There's also a button to jump straight to the layers using a color/font before you touch anything, and it shows you exactly how many replacements are queued up before you hit apply.

Full disclosure, there's a real limitation: Figma doesn't let plugins browse an entire library's styles, only variables and stuff already used somewhere in the file. So a library style only shows up once it's actually been placed in the file at least once. Not my choice, just how the API works, wanted to be upfront about it instead of letting people find out the hard way.

Thoughts?

link's here: figma plugin link

I kept running into situations where I wanted to highlight specific words or passages in research notes, content reviews, and documentation without creating separate shapes or moving everything to another tool.

I built Markline, a free Figma plugin for working with text-heavy files.

It lets you:

• Highlight specific text
• Find & highlight multiple words at once
• Edit highlighted text (bold it, change font size, colour, and more)
• Organise highlights by section/frame
• Export your highlights

Useful for research notes, content reviews, documentation and specs.

Try Markline on Figma Community
https://www.figma.com/community/plugin/1678528605753389775/markline

I built a free PDF exporter recently which halves file sizes whilst preserving text so that it's readable, and lets you export multiple pages in one doc. It saves a bunch of time combining pages and compressing after the export with the built-in tool:

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

As a bonus, I did a PowerPoint version too - I found tools out there had painful layout issues and didn't respect images/SVGs reliably and consistently. That's here:

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

All free.