A developer builds a Figma plugin and wants the name to make the Figma connection obvious, since that is exactly what the plugin works inside of. The instinct is to call it something like Figdesigns, folding the word Figma into the brand directly. Every developer tool platform carries the same kind of platform specific restriction, one that only becomes obvious once you read the actual guidelines. Figma's own Community Guidelines address this instinct directly, with a real approved example and a real rejected example shown side by side in their own documentation, making this one of the few platforms where you do not have to guess where the line is. Knowing where that line sits before building saves a rename later, once the plugin already has real users attached to whatever name shipped first.
The rule, and the two examples Figma gives you directly
Figma's Community Guidelines state this rule precisely: “Don't include our name (or part of our name) in your company name, resource names, domain name, or social media handle. For example: Figdesigns.” But unlike most platform trademark policies, Figma does not leave developers guessing about where the line sits. The same guidelines give an approved example right alongside it: “You can refer to Figma or our products in your resource's title. For example: Tom's plugin for Figma Design.” Allowed: Tom's plugin for Figma Design, where Figma's name appears clearly as a compatibility reference alongside a distinct plugin identity. Not allowed: Figdesigns, where part of Figma's name is absorbed directly into the plugin's own brand identity. This is the clearest version of a rule that most platforms only imply. The difference is not whether Figma's name appears at all, it is whether it functions as a reference to compatibility or gets folded into your own name as if it were part of your brand. Google draws the identical line for Chrome extensions, where “Tab Organizer for Google Chrome” passes review while a name built around the word Chrome itself does not, just with Google's trademark standing in for Figma's. That single distinction is worth internalizing before naming anything, since it applies well beyond Figma alone. Most developer platforms leave that judgment call entirely up to you, which is what makes Figma's own worked examples such a useful anchor point when a candidate name sits somewhere in between.
What this means in practice for your plugin name
Once the rule is clear, translating it into an actual naming decision comes down to three separate questions, each one worth checking on its own before a name gets locked in, since a plugin name can pass one of these checks and still fail another entirely.
Safe pattern, following Figma's own approved example
A structure like "[Your Plugin Name] for Figma" or "[Your Plugin Name], a Figma plugin" mirrors Figma's own sanctioned example directly. The plugin's actual identity stands on its own, and Figma is referenced as context, not as a piece fused into the brand itself. This is the lowest risk pattern precisely because Figma has already confirmed it in writing. A developer who defaults to this structure is not guessing at a boundary, they are copying language Figma itself published as acceptable. That confirmation is worth more than any general naming instinct, since it removes the ambiguity most trademark policies leave in place for every other platform a plugin might eventually target.
Risky pattern, following Figma's own rejected example
Any name that blends part of the word Figma into your own brand, similar to how Figdesigns merges Fig into a new compound word, falls into the category Figma has explicitly rejected in their own documentation. Even variations that only borrow a syllable or a sound rather than the full word can read as an attempt to associate directly with Figma's identity rather than simply stating compatibility. A reviewer does not need the entire word present to flag this pattern, since the actual concern is implied affiliation, not literal spelling. Treating this as a spelling checklist misses the intent behind Figma's guideline, which is about avoiding any name that reads as though Figma made it.
The plugin name still needs to work as a search term
Beyond the trademark question, Figma does not prescribe a specific naming formula once that restriction is satisfied, leaving plugin names free to be as descriptive or as creative as a developer wants. But users still search the Community directly using this name, so that freedom is also a risk. A name that clears the trademark check but is too abstract to match what a designer would actually type into Figma's plugin search creates the same discoverability problem covered across other developer tool naming decisions. Passing the trademark rule is necessary, but it is not the same as being findable. A clever, fully compliant name that nobody can guess or search for still fails at the one job a name is actually meant to do, which is getting found by the person who needs it.
A pre-publish naming check for a Figma plugin
Before publishing a Figma plugin to the Community, run through this list once, since most of these checks are easier to handle before submission than after a rejection.
- 01Compare your candidate name directly against Figma's own two examples, checking whether Figma's name functions as a separate compatibility reference or gets absorbed into your own brand identity.
- 02If in doubt, default to the safer "for Figma" or "a Figma plugin" pattern, since Figma has already confirmed this structure in their own guidelines.
- 03Search the Figma Community directly for your candidate name and close variants, since a crowded marketplace of similar plugin names creates the same search visibility problem covered on other platforms.
- 04Write your one sentence plugin description alongside the name, since Figma's own publishing flow indexes both together for Community search.
- 05Confirm the name reads clearly to someone unfamiliar with your plugin, since Figma explicitly allows creative naming, which only helps if the name is still functionally clear enough to search for.
Running through all five before submitting takes a few minutes and catches the kind of naming problem that is otherwise easy to miss until a reviewer, or a confused user, points it out after the fact.
Reference the platform, do not become part of it
Figma is one of the few platforms that hands developers a real approved and a real rejected example directly in their own documentation, which removes most of the guesswork other platforms leave in naming decisions. A name that clears Figma's trademark bar but still blends into every other plugin in the Community has only solved half the problem. Starting from a strong pool of candidate names makes it easier to test each one against Figma's specific examples before committing. Generate that starting pool with NameKit's Project Name Generator, then check each candidate against Figma's two worked examples above before you submit anything for review.
Frequently asked questions
Can I use the word Figma in my plugin's name?
Yes, but only as a clear compatibility reference, not absorbed into your own brand. Figma's own guidelines show "Tom's plugin for Figma Design" as an approved example, where Figma's name sits alongside a distinct plugin identity rather than being merged into a new combined name. Sticking close to that structure is the safest default for most plugin names.
Why is a name like Figdesigns not allowed for a Figma plugin?
Figma's Community Guidelines specifically list this as a rejected example, since it absorbs part of Figma's name directly into a new brand identity rather than referencing Figma as a separate, clear compatibility statement. The distinction is reference versus absorption, not simply whether the word appears at all, and that same test applies to any candidate name you are considering.
Does my Figma plugin name need to describe what it does?
Not strictly. Figma's naming rules focus on the trademark restriction, not on requiring a descriptive name. However, since users search the Figma Community directly using this name, a name with no functional connection to what the plugin does can still create a discoverability problem separate from any trademark concern. A fully compliant name can still be difficult for anyone to actually find.
What happens if my Figma plugin name violates the naming guidelines?
Figma's review team evaluates plugins before they are listed publicly in the Community, and a name that violates their trademark guidelines can affect approval. Addressing naming concerns before submission is faster than resolving them after a rejection, since a maintainer who catches this early avoids a delay that a quick rename would have prevented entirely.
Are Figma's naming rules stricter than other developer platforms?
Not necessarily stricter, but unusually clear. Many platforms state a general trademark restriction without concrete examples, leaving developers to guess where the line sits. Figma provides both an approved and a rejected example directly in their own documentation, which is a rare level of clarity worth taking advantage of before you finalize a name.