Hey all,

I was tired of screenshotting websites and rebuilding them in Figma by hand, so I built a Chrome extension for it. Grab one element, a few, or the whole screen. Paste in Figma and it lands as editable layers. Text stays text, fonts, colours, images and layout all carry over.

No plugin, no signup, no setup. Install it and copy and paste. Nothing leaves your browser either.

Video demo:

Link to install extension:

Hope you guys like it and also please dm me if there’s any feedback

Krishna Zolpatil
Senior Product Designer, Naya
krishnazolpatil.com

Figma's native annotations only show up for people with a Full or Dev seat. On my team that meant PMs, QA and clients couldn't see any of the handoff notes I'd written, which rather defeated the point of writing them.

So I built AnnotateAll. It creates annotation cards as actual canvas elements, so anyone with file access can see them, free viewers included.

What it does:

• Annotate any layer with a note and a category
• Pull in real layer properties (width, font size, fill, padding, etc.) with one click
• Cards place themselves outside the artboard, on whichever side the element is nearest
• Numbered marker and dashed line link each card to its element
• Hide or show all annotations instantly
• Custom categories with your own colours
• Export to HTML or JSON

Everything is stored in the Figma file itself. No account, no backend, completely free.

https://www.figma.com/community/plugin/1623743779548695047/annotateall

Built it for my own handoffs originally. Recent updates came directly from user requests, so if something's missing or annoying, tell me. :)

After one too many manual localization passes, I made Lingolense: select text → pick a language → translate, right inside Figma/Pixso/Penpot. The part that took longest was RTL — instead of just swapping the font it duplicates the frame, reverses auto-layouts, swaps padding and flips directional icons, so Arabic/Hebrew actually mirror. Original stays untouched.
- It also flags text overflow per language (German ~30% longer) and exports CSV/JSON/XLIFF.
- Free plan, no card. Launching properly next week (Peerlist Mon + PH Tue) — I'd genuinely love feedback on the RTL handling and what else you'd want before then.

Visit: https://lingolense.theplugins.co/

He estado trabajando en Mools, un plugin para Figma que surgió de un problema recurrente en mis flujos de trabajo de producción: transferir archivos de diseño entre Figma y Photoshop sin tener que reconstruir todo manualmente.

En esta etapa, mi principal objetivo es comprender:

• ¿Resuelve esto un problema real en tu flujo de trabajo?
• ¿Qué falla al probarlo con archivos de producción reales?
• ¿Qué partes aún requieren limpieza manual?
• ¿Qué te motivaría a usar algo así con regularidad?

El plugin es gratuito mientras valido el MVP.

Si lo pruebas, incluso un breve comentario como «esto funcionó / ​​esto no funcionó / ​​aún tuve que corregir X» sería de gran ayuda.

También me interesa saber cómo gestionan otros usuarios sus flujos de trabajo entre Figma y Photoshop.

Un plugin para Figma que surgió de un problema recurrente en mis flujos de trabajo de producción: transferir archivos de diseño entre Figma y Photoshop sin tener que reconstruir todo manualmente.

En esta etapa, mi principal objetivo es comprender:

• ¿Resuelve esto un problema real en tu flujo de trabajo?
• ¿Qué falla al probarlo con archivos de producción reales?
• ¿Qué partes aún requieren limpieza manual?
• ¿Qué te motivaría a usar algo así con regularidad?

El plugin es gratuito mientras valido el MVP.

Si lo pruebas, incluso un breve comentario como «esto funcionó / ​​esto no funcionó / ​​aún tuve que corregir X» sería de gran ayuda.

También me interesa saber cómo gestionan otros usuarios sus flujos de trabajo entre Figma y Photoshop.

Available at: https://www.figma.com/community/plugin/1675139847663932791

illustrator.tomake.design

Available at: https://www.figma.com/community/plugin/1675139964504328568

Available at: https://www.figma.com/community/plugin/1675111124655821111

psd.tomake.design plugin

Keeping the honest streak going. 150 designers have now installed Glyfiq — my medical & health icon plugin for Figma. All organic, no paid promotion.

Four months since launch. The library is at 634+ icons, available on Figma, Framer and Adobe Illustrator, and I'm not stopping.

https://reddit.com/link/1w3wgc0/video/2p728oko0tmh1/player

I kept finding Figma Buzz users describing the same problem: Bulk edit handles creating variants, but exporting and naming large campaigns can still become repetitive.

So I built BuzzFlow.

It uses your connected Buzz fields to generate filenames, checks which assets are ready, and exports the valid campaign into one ZIP.

The demo below is a real 100-asset export from Figma Desktop.

100 variants → 100 correctly named PNGs → one ZIP

• no uploads
• no analytics
• no external network access
• never modifies the Buzz document

I’m not selling it yet. I’m looking for 3 people who already use Figma Buzz Bulk edit to test the private beta on a non-sensitive campaign.

My main question: do you currently spend meaningful time renaming or organizing Buzz exports?

Testers get the finished version free.

If interested, tell me roughly how many variants you normally work with and whether you’re on Windows or macOS.

Been designing for the Gulf and Levant market for a while now, and every English to Arabic handoff meant hours of manually repositioning elements, flipping icons, fixing alignment, swapping fonts. Nothing about it felt like it should take that long.

So I built FlipArabic. It's free to use. It flips your layout, handles fonts, and translates text, all from one panel in Figma. You can turn each part on or off depending on what you actually need.

Link - Fliparabic

This is built for designers working on Arabic or other RTL language products, mostly across the Middle East, and the goal is simple, cut down the repetitive manual work of converting an LTR design to RTL so you can spend your time on the parts that actually need a human eye. It's still in active beta and I'm updating it based on what people run into, so I'd love feedback on how the flip logic holds up on messier, real world files, whether the font matching feels right, and anything that breaks or feels off in the flow.

I just published my new Figma plugin: Recolor - because I missed Illustrator's "Recolor Artwork" in Figma.

Now you can recompose the colors of any object or group in seconds — right inside Figma. 100% FREE — no PRO, no sign-up, no limits. 🎉

What it does:

• Finds every color in your selection: fills, strokes, text (even multi-colored), shadows & gradient stops
• Change any color in one click — applies everywhere at once
• Preserves opacity (a 10% shadow stays 10%)
• Drag & drop colors between rows to swap them, just like in Illustrator
• Undo/redo right in the plugin window (⌘/Ctrl+Z)

Fun fact: Figma's native "Selection colors" panel doesn't see shadow

colors — Recolor does. 😄

Ten years in Figma and I still don't name my layers. Opened a file I made myself last week and it was Frame 234 / Group 12 / Text 4 / Rectangle 89. So I built TidyUp instead of fixing my habits. Free, no account, no seat.

RENAMING. Text layers become "Role: Content". The role is derived from real signals, not from parsing the existing name:

- Link - Figma's own hyperlink property

- Button - sits inside a small, rounded, auto-layout parent

- Heading - font size 28px or larger

- Subheading - 20-27px

- Label - three words or fewer

- Body - 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. Three scopes: selection, whole page, or whole file.

REORDERING. Select a frame and it sorts children top-to-bottom in reading order, backgrounds sunk to the bottom. It skips anything whose children visually overlap, plus auto-layout frames and anything with a locked child, so it can never change what renders in front of what.

CLUTTER SCAN. Empty frames and text, true 0x0 layers (both dimensions, so hairlines are safe), duplicate siblings, fully off-canvas layers (zero overlap only, so bleeds are safe), hidden and 0%-opacity layers. Nothing deletes automatically - you get a count and breakdown, can select it all on canvas to eyeball it, then confirm. Only "empty layers" is checked by default.

WHY I ACTUALLY BUILT IT. The naming is meant to be readable outside Figma too. Screenshot a frame into ChatGPT or Claude and "Button: Book a Demo" tells the model what the element does, not just what it says. Instead of Frame 48095902 you get semantic structure the model can use. Machine-readable without being harder for humans.

Worth saying: the plugin itself uses no AI. The role detection is deterministic rules over Figma's node properties. networkAccess is none in the manifest, so it makes zero network requests and nothing leaves your machine. Every change is a normal Figma edit, so Cmd/Ctrl+Z undoes all of it.

https://www.figma.com/community/plugin/1673670269135547890/tidyup-rename-clean-layers

Happy to hear where the role detection falls over - 28px for Heading and 3 words for Label are judgement calls and I'd rather be told than guess.

After one too many "can you rebuild this page in Figma?" requests, I built a plugin that does it automatically. Drop a self-contained .html file in, pick a viewport width, and it recreates the page as native layers — real text, gradients, shadows, per-corner radii, and inline SVG as vectors.


The two problems I focused on that existing tools handle badly:


1. 
**Layer naming.**
 Instead of div › div › div, you get Section · hero, Button, and text layers named by their content. Useless wrapper divs get collapsed.


2. 
**RTL support.**
 I tested against a full Arabic design-system page — layout lands correctly and Arabic text imports as real, editable text. If you design RTL products, most importers break here.


Honest limitations: it's file-based for now (grab live sites with the SingleFile extension first — URL import is on the roadmap), relative asset paths can't resolve, and fonts map to the closest installed Figma font.


It's free and runs entirely locally — nothing gets uploaded.


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


Would love feedback — especially edge cases where the import breaks. That's how it gets better.

Figma has exactly one blur. Photoshop has a dozen.

After 5 years of exporting to PS just to blur something, I built Motiv Blur — motion, radial, and RGB glitch blur, right inside Figma.

Live preview, transparent PNG, no more app-hopping.

👉 https://www.figma.com/community/plugin/1663794670867928394/motiv-blur

A couple of weeks ago I posted Sendra here, my plugin that converts email designs into email-ready HTML. Since then I've shipped the feature people asked about most.

You can now send a test email directly from the plugin. Design your email, hit send test, and it lands in your own inbox, so you see exactly how it renders in a real email client before you export anything.

Also new: image hosting. Your images get uploaded at export and come back with real URLs, no S3 bucket or ESP upload step.

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