Select your Figma images, hit one button, and a vision model reads each one and generates a clean file name slug — so Rectangle 482 becomes golden-gate-bridge-sunset on export. Great for dev handoff, SEO, and CMS uploads where file names become URLs. Uses your own Anthropic or OpenAI key — fraction of a cent per image. Free 15-image trial included, no card needed.
Hey PH 👋 I built this after getting tired of exporting assets from Figma and spending time renaming everything before handing off to developers. The rename tools that already exist look at layer names and hierarchy — useful for file organization but not for what the image actually shows.
Would love feedback on the trial flow, the naming quality, or anything else. Happy to answer questions here all day.
Report
honestly this looks super useful, the dev handoff thing is a real pain point. one thing that would help though is letting us set custom naming rules or prefixes per project, like so all blog post images get a "blog-" prefix or follow a specific slug format our CMS wants. would make it fit into existing workflows way better than just the auto-generated names.
Thanks! That's exactly the kind of workflow I had in mind.
It already follows a slug format, and you can inject custom keywords (for example, blog), although they're currently incorporated naturally into the generated filename rather than forced as a prefix.
That said, support for project-specific naming conventions is definitely something I'm considering. I know different CMSs' and teams have their own standards, so having configurable naming rules could make the plugin fit into more workflows.
Report
Love that it uses your own API key instead of forcing a subscription — makes the cost completely transparent and the trial without a card is a really thoughtful touch.
Report
No reviews yetBe the first to leave a review for SEO Image Renamer - Figma Plugin
honestly this looks super useful, the dev handoff thing is a real pain point. one thing that would help though is letting us set custom naming rules or prefixes per project, like so all blog post images get a "blog-" prefix or follow a specific slug format our CMS wants. would make it fit into existing workflows way better than just the auto-generated names.
@jsonjake
Thanks! That's exactly the kind of workflow I had in mind.
It already follows a slug format, and you can inject custom keywords (for example, blog), although they're currently incorporated naturally into the generated filename rather than forced as a prefix.
That said, support for project-specific naming conventions is definitely something I'm considering. I know different CMSs' and teams have their own standards, so having configurable naming rules could make the plugin fit into more workflows.
Love that it uses your own API key instead of forcing a subscription — makes the cost completely transparent and the trial without a card is a really thoughtful touch.