Hey all 👋

After a lot of feedback on my previous icon workflow post, I kept iterating on the idea.

What started as:
scan → organize → export
is slowly turning into something closer to a reusable icon system inside Figma.

Some of the recent improvements:
• Favorites now sync locally across Figma projects
• Smarter icon naming and organization
• Better handling for large icon sets
• Reusable icon libraries via import/export
• Cleaner, ready-to-use outputs
• Keeping the whole flow inside Figma without jumping between tools

The interesting challenge stopped being “exporting icons” and became more about:
consistency, reuse, and keeping things manageable at scale.

Curious:
How are you currently managing icon systems across projects?

What does your icon workflow usually rely on today?
libraries manual?
organization inside Figma?
or custom workflows?

You can:
• Turn your Figma prototypes into Lottie animations
• Edit timing & easing for the entire flow inside the plugin
• Use the compressor for production-ready files

Export and compress Lottie in one workflow:
https://figma.com/community/plugin/1630333167443650772

Would love to hear your feedback ✌️

Hello designers!  
Many times, I have to visually upgrade some old pptx files in Figma, but the need to rebuild them every time is very tedious, so I wrote this plugin to import .pptx files into Figma with one click while maintaining the visual effects. If you're tired of rebuilding in Figma, you can try this plugin and happy to see you feedback!
https://www.figma.com/community/plugin/1611637977064559630/pptf-google-slides-powerpoint-importer-pptx-to-figma

🚀 Core Features: As of Update(2026-04-29)

1. 100% Editable Figma Layers: Convert PPTX text boxes, shapes, and photos into native editable Figma nodes. Edit typos, extract copy, or restructure layouts instantly.
2. [NEW] Smart Table Engine: Transform complex PowerPoint tables into perfectly aligned Figma objects. No more drawing lines and grids manually.
3. [NEW] Advanced Chart Extraction: Extract and convert native PPT data charts into editable vector layers in Figma without losing proportions.
4. [NEW] Auto-Font Mapping: Intelligently map desktop Microsoft fonts to local Web/Google fonts in Figma, eliminating the dreaded "Missing Font" warning.
5. [NEW] Multi-Slide Import to Frames: Import a single slide or an entire 100-page deck at once. Every slide automatically converts to a clean, sequentially named Figma frame.
6. Theme & Color Sync: Automatically extract the PPTX Theme color palette to jumpstart your Figma Design System.
7. Vector & Shape Preservation: Import complex presentation elements and SVG icons as individual, scalable vector paths. Stop settling for pixelated images.
8. High-Fidelity Rendering: Support for shadows, blurs, opacities, and high-res image crops straight from the deck right to your Figma canvas.

I built FigSpecs out of challenges experienced.

I kept watching the same thing happen, design approved, engineer picks up the ticket, opens Figma, clicks through 40 layers trying to find padding values and token names. Meanwhile the AI agent they're using is guessing layout from a screenshot.

The problem isn't the model. It's that there's no machine-readable file bridging design and code.

FigSpecs fixes that. Select any Figma component and it generates:

→ Detailed Token audit that identifies layers not connected to variables

→ Anatomy diagrams with numbered callouts

→ Accessibility audit (WCAG-aligned, Voiceover, Talkback)

→ component.rules.md: full structural hierarchy, token paths, flex direction, alignment, your Cursor/Claude Code agent reads it directly.

→ Tailwind v4 block CSS custom properties, correct namespaces, pixel values

→ specs.json for token pipelines and CI validation

→ 1-click Jira ticket with everything attached

If you are a Designer, Design system Manager, Product manager, Developer or Architect, this product is for you.

Try for free: https://www.figma.com/community/plugin/1612756059828219731

Hey all 👋

I’ve been working on improving an icon workflow inside Figma, and put together a quick video showing the full flow.

The idea is to keep things simple:
scan → organize → save → export → use

What I’m trying to improve:
• More reliable icon detection (smart scan)
• Saving icons to a favorites list for reuse
• Smoother selection and organization
• Cleaner SVG output
• A demo page to preview icons and copy code

The goal is to reduce friction and make the process feel more natural.

Curious:
Does this flow make sense to you?
Where would you expect friction or confusion?

Happy to hear any thoughts.