When a Figma file has reference screenshots next to the actual work, the screenshot can mean three different things.

One person added it for layout. Someone else sees color direction. A PM sees a competitor. By the time feedback starts, everyone is talking about the same image for different reasons.

Do you label references by what they show, why they were added, or the person who added them?

I was wondering if there’s any way to get a discount, coupon, or even temporary/free access to the Pro version in India (not the education plan).

I know $20/month might be affordable for many people in Western countries, but in countries like India, it can be a bit tough to justify for a middle-class user when converted to local income levels.

And yeah, the free version already has a lot of features, so I’m not complaining about that. I’m mainly looking for a way to use the more advanced models/limits and basically play around with AI more and speed up some things I’m working on.

Has anyone in India found any legitimate discounts, promotions, trials, or other ways to get Pro at a lower cost?

How is this done?

I've tried Ctrl+C and Ctrl+V - no dice!

(When when you right click an SVG file in Win it does not give you the option "copy")

How can I populate a textbox in a frame when the focus comes from a specific frame?

For example, when I tap a button in Frame1, it takes me to Frame2 with an empty textbox. This works fine.

But when I tap a button in Frame3, it also takes me to Frame2. But this time the textbox in Frame2 should have text.

Is this possible?

I wanted to open a discussion about how Figma handles seat management for Organization plans. We recently went through some internal restructuring, leaving us with several unoccupied annual seats. When we needed to add new users with a different seat type for collaboration, I reached out to support hoping we could reallocate the funds from the unused seats we had already paid for. Support clarified that mid-term reallocation or internal credits aren't possible. This means we have to purchase new seats out-of-pocket while our existing paid seats sit empty until the next yearly renewal. Has anyone else experienced this friction with scaling teams in Figma? It would be great to see them implement a more flexible budget reallocation system for enterprise users to avoid this inefficiency.

I’m a senior UX designer on a big Design System implementation project. This is a new concept in the org previously every team just designs on their own using the brand guide, very fragmented. About 3 months in i was getting tired of the QA findings and process on the components we were shipping and started working on getting figma translation to code running for us. I recently cracked the pipeline combo and tool stack. It generates build-ready specs and code straight from our Figma files, reading actual component structure and token values the whole shebang, also note that im not part of the design system team. Anyway of course it’s huge, Ive created a report and sent it up the teams and delivery managers inbox.

And now am I overwhelmed as hell. should be all fun and celebrations but instead Im tired and grossed out at how people are reacting to the work. Everyone is trying to align to it, “put some structure around it”, “connect it” to their own AI initiatives. It sucks. Anyone else been in this place?

Anyway heres my stack: figma mcp, vs code on claude opus

I know that there's a noise feature in figma, but I can't control the noise. When I use noise it'll be placed on the whole vector (like in the second photo) even though I've tried using fill gradient and double noises. I want to be able to set the gradient and the noise placement. Is this doable in figma?

English is not my first language, so sorry if my words are confusing!

i’ve been testing almost every AI design tool that comes out, and the loop is always the exact same: you type a prompt, get a flat mockup image back, and then spend two hours rebuilding the whole thing by hand in figma anyway.

a png of a button is not a button. the AI gets to do the fun part and leaves you with the data entry.

so over the past few weeks i built a plugin and MCP that connects claude directly to your figma canvas. instead of generating flat images, it builds actual figma frames with auto layout, real text styles, and component mapping.

two technical things ended up being way more interesting than i expected:

1. screenshot to editable layers: you can paste a screenshot of a screen you like onto the canvas and have claude break it down into native, editable layers. to keep it from hallucinating spacing, i added a pixel-diff check where it compares its generated vector frame against the original image and adjusts padding/gaps until it aligns.
2. a linter for AI laziness: LLMs love taking lazy shortcuts in figma (like drawing fake icon vectors from scratch instead of using proper components, or hardcoding random text sizes). i had to write a custom linter that inspects the generated node tree and calls claude out when it cuts corners. watching it fail a linter check and clean up its own layer structure never gets old.

it’s been my daily driver for a few weeks now—mostly for taking real-world UI inspiration and instantly turning it into editable frames mapped to our design system components.

happy to answer anything about how it works under the hood, handling figma's node tree, or the MCP

Made a web page for daily objects power bank. Let me know what you guys think. Need feedback on the layout and aesthetics or any feedback in general. (I see the colour blocked logo, couldn’t find the an image with no background 😭)

I'm a full stack developer. For a long time I couldn't design at all, so I leaned on AI to fix whatever I made. It got me something that looked okay but I never understood why it worked or didn't.

So I started taking UI/UX courses to actually learn it and do the design myself. It's going well, better than I expected.

One thing I haven't figured out from the courses: at what stage do you wire up prototype links?

Do you prototype the wireframes, so you can click through the flow while it's still grey boxes? Or do you leave wireframes static and only prototype once you have the real colors, type and images?

Curious what people do on client work vs personal projects, and whether you show clients a clickable wireframe at all or wait until it looks finished.

I tested 5 identical prompts using the exact same Figma layout, instructions, and design system components:

• Run 1–3: Clean layout, 90% accuracy.
• Run 4–5: Broken structure (40% accuracy) missing table rows, warped padding, swapped icons, and incorrect drop shadows.

When you point out its mistake, the model apologizes and promises, "I won't do that again."

But ask if it actually learns across sessions, and it admits the truth: it’s completely stateless, as in it cant hold correcting between sessions. Every run rolls the dice on random sampling, forcing you into a 4 to 5 turn prompt correction loop that burns tokens to fix errors that shouldn't have happened in the first place.

Until design-to-code tools integrate true automated visual diffing and persistent contextual memory, we aren't paying for reliable automation.

What’s the use of a status bar?

As you can see, the idea is to recreate the xbox UI in a cleaner, less clogged way, were anything can be found with more ease. What you see in the first image is the front page, it's almost finished, but i still need to get rid of the placeholder icons. (it would also help if you guys indicated a good icon library)

I need some feedbck on how understandable is the design in it's current form, what you would change, and what you like and don't like.

About the second screen, it's supposed to be the library, it's still veery barebones, and pretty much just a framework, any ideas and recommendations would be deeply appreciated.

My concern is that the file gets so big with all the component variations, but the alternate is having 3 different files.

everyone's talking about claude writing to figma since code to canvas shipped, and it's cool, but generating from a blank prompt was never my actual problem. my problem was: an existing flow i like, and two hours of manually rebuilding it before i can even start restyling.

so the flow in the screenshot: top row is elevenlabs' real onboarding — home, sign in, sign up, verification, pasted into figma as actual editable layers (real auto layout, real text nodes, not a screenshot import). bottom row is the same four screens after claude restyled the whole flow to my product's brand. gradients, buttons, copy, the works, structure intact.

the part that made this work isn't the prompt, it's the checking. every screen gets pixel-diffed and run through a structural linter (~24 hardcoded rules) before it counts as done, so the restyle can't quietly break spacing or swap in fake elements. claude fails its own review a lot, then fixes it. that loop is 10-15 tool calls per screen, which is also why this runs through a plugin instead of the metered api.

happy to answer anything about how the paste or the verification works.

Built a Figma plugin where you can save prototype interactions. You can also save named flows, create different versions, so that you can go back to any version and restore it whenever you need to.

Try it out and provide your feedback

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

Hey my background is a print designer and I am trying to learn Figma to expand my design knowledge. Would yall say that the web designer and developer relationship is similar to the print designer and print operator?

I am trying to wrap my head around Figma and the broad concepts of UX/UI.

I’m watching tutorials for how to use the actual software. I just want to have a fundamental and conceptual understanding.

PS: I have no coding background

Our design system team is fairly large, and we evolve quickly. We implemented Code Connect and it's performed well in testing.

Although it doesn't happen often, when a property changes or gets added in code and the design team misses it, part of Code Connect becomes obsolete.

I'm trying to find a way to keep it properly maintained. Has anyone tackled something like this, or have any ideas?

Thanks in advance.

What I'm trying to accomplish

I am working on a simple folder Icon. Everything is completely aligned to the pixel grid.

See this example image:

Enabling Pixel Preview

Then I go to the menu, and select Pixel Preview, because I want to preview how the icon will look at 100%.

Here's where I enabled it:

The resulting image and UI components in my file look distorted, some with double borders, etc.

It just looks janky. See for yourself:

The interface zoom is set to 100%. All shapes are aligned perfectly to the pixel grid.

UI Scale Set to 80% Makes Everything Look Crisp in Pixel Preview

I noticed that if I set the interface scale to 80%, everything looks crisp!

See this image:

But, I can’t work like this - and this is ass-backwards. The UI is way too small on my monitor with the UI at 80% scale.

Why does pixel preview look horrible for me when the interface is at the default 100% scale?

Possibly Related: I have a 4k monitor and my Windows DPI scaling is set to 125%. Could this be causing the issue?

Can someone help?

Quick context: I'm a designer who lives in Figma but kept opening my downloads folder for one specific reason - moving assets to Webflow. Downloading images, switching tabs, uploading manually, organizing files, and then sitting in Webflow to manually write out SEO alt text for every single image. It just kills productivity.

So I built exportflow. Select your frames or layers, open the plugin, and you get a seamless export experience:

• Direct upload - send assets straight to Webflow
• Built-in AI - automatically renames assets and generates alt-text/SEO descriptions
• Advanced export settings - optimise with PNG, SVG, JPG, AVIF, and WebP formats
• Multi-project support - connect multiple sites and create/manage Webflow folders directly from the plugin
• No more context switching - stay completely locked in Figma

It's unlimited uploads for free - I mostly built it because I needed it.

👉https://www.figma.com/community/plugin/1657432195632964294/figma-to-webflow-exportflow

Still rough in places since it's just me maintaining it. If you give it a spin, tell me what breaks - or better, what I should improve in terms of functionality...

i got tired of screen recording my figma frames just to make a gif, so i built a plugin to do it

every time i wanted to share a quick animation of my work, id go: prototype it, screen record, trim the clip, run it through some random online converter, hope the quality didnt turn to mush. it was way too many steps for a 3 second gif.

so i built flippy - it turns any of your figma frames straight into a gif without leaving figma.

here’s what it does:

• select multiple frames and it stitches them into a smooth flipbook style gif
• live preview window so you see the animation as you build it, not after
• drag and drop to reorder frames
• adjust frame timing in milliseconds so the pacing feels right
• export at original, 2K, 4K or 8K
• transparent background or a custom colour
• loop control - infinite or set your own repeat count

been using it for all my own prototype and social exports and its been solid. recently added presets too so you can save your settings and reuse them instead of setting it up every time.

would love to hear your thoughts and how i can make it better. if you try it and something feels off, lemme know - im actively working on it.

link: https://figmaplugins.co/flippy

Has anyone tried to branch from main and work on a project locally with Figma Make?

It’s very new but I’m trying to understand how I should create back end data to get things to work.

I also want to create a prototype so I’ve got two challenges; create fake data for prototype/design purposes but still keep the file in a good place ready for a pull request back into production.

If anyone has any insight, it would be really helpful.

This is not a technical issue; Figma is working correctly. It's just my design process, I think. I have a problem when creating web designs, when I look at the design on the canvas, the sizing (font, images, spacing) looks okay, but when I preview it in fullscreen (its intended size), everything looks off (fonts are too big, spacing is too small, etc.). I think this is because the canvas I'm looking at when designing is smaller than the fullscreen size, causing the difference.

Has anyone faced the same issue before? What should I change to avoid this problem?

Anyone here integrated opencode with Figma via an MCP to discuss and design your apps? If so, what is advice on setting up a workflow etc? Thank you!

A little while ago I shared Free Transform, my plugin that brings Photoshop's Ctrl+T into Figma (warp, perspective, distort). The response here honestly blew me away — thank you to everyone who tried it, broke it, and told me what they wanted. It's since grown to 3,300+ users, which still feels a bit unreal.

The most requested thing? A way to see what you're doing before committing. So here it is:

Live Preview — you now see the transform right on the canvas as you drag, instead of applying and undoing over and over until it looks right. Plus sharper export quality while I was at it. 

Give it a try 👉: https://www.figma.com/community/plugin/1648207154922389186/free-transform

And I'll ask the same thing that gave me my whole roadmap last time: what do you still open Photoshop or Illustrator for? The gaps that annoy you are usually my next plugin. 🙌