Design Tools

Bring-Your-Own-Key Translation in Figma: Why Designers Are Switching

Updated April 2026 · 10 min read

For years, the default approach to translating Figma designs was to use a plugin that calls the vendor's hosted API. You install the plugin, it works — until you hit a quota limit mid-project, the translation quality drops because the vendor switched models, or the free tier disappears in a pricing update you didn't notice.

There's a better model: bring your own key (BYOK). You connect a plugin directly to your own OpenAI, Anthropic, or Gemini API key. You control the model. You pay the AI provider directly at cost. The plugin vendor charges nothing for translation — they just provide the interface.

Here's why this matters, and when it's the right choice.

The Problem with Hosted Translation Plugins

Hosted API plugins

  • Quota limits that pause mid-project
  • Vendor chooses the model — you don't
  • Opaque per-character pricing
  • Quality tied to vendor's cost-cutting
  • Vendor data retention policies
  • Free tiers that disappear

BYOK plugins (Lokali)

  • No quotas — pay your AI provider directly
  • You choose the model (GPT-4o, Claude, Gemini)
  • Pay-per-token at cost, no markup
  • Model quality under your control
  • API key stored locally, never on plugin servers
  • Plugin is free forever

The cost difference is significant for heavy users. Translating 10,000 characters through a hosted plugin at $0.10/1K characters costs $1.00. Translating the same text via GPT-4o directly costs roughly $0.05–0.10 total — and you get a faster, more capable model.

What BYOK Actually Means in Practice

BYOK sounds technical but the setup is one step:

  1. Get an API key from OpenAI, Anthropic, or Google AI Studio.
  2. Install Lokali from Figma Community.
  3. Open the plugin, paste your API key. It's stored in your browser's local storage — it's never sent to Lokali's servers.
  4. Translate. Done.

You never have to think about the key again unless you rotate it or switch models.

Which AI Model Should You Use for UI Translation?

ModelBest forNotes
GPT-4oArabic, French, German, Spanish, JapaneseStrongest multilingual coverage overall; good at preserving UI tone
Claude 3.5 SonnetTone-sensitive copy, marketing textExcellent at natural-sounding translations; slightly slower than GPT-4o
Gemini 2.0 FlashHigh-volume, cost-sensitive projectsVery fast; best cost/token ratio; strong European language support
GPT-4o miniBulk UI strings, quick iterationsLower cost; slightly lower quality on complex sentences; good for labels/buttons

For MENA-focused work (Arabic, Hebrew, Persian), GPT-4o is the current recommendation. It handles Arabic glyph ordering, right-to-left script nuances, and dialect variations better than any other generally available model as of 2026.

BYOK and Data Privacy

This is where BYOK has a structural advantage that matters for design teams with NDAs or client confidentiality requirements.

With a hosted plugin, your design copy flows through the plugin vendor's infrastructure before reaching the AI provider. That's two parties who see your content: the plugin vendor and the AI provider. With BYOK, it's one: your API calls go directly to OpenAI, Anthropic, or Google. Lokali never receives your translation requests — it just provides the Figma interface that makes the API call from your browser.

For enterprise and agency designers: If your client requires that unreleased product copy stays within a defined set of vendors, BYOK lets you point to your existing AI provider agreement rather than a separate plugin vendor's terms of service. That's a meaningful compliance simplification.

BYOK + RTL: Lokali's Specific Advantage

Most BYOK translation tools stop at text replacement. Lokali combines two things in one pass:

  1. AI translation using your API key (any supported model)
  2. RTL layout swap — mirroring the frame's spatial layout for Arabic, Hebrew, Persian, and Urdu

No other free Figma plugin combines both. RTL Layout (9.5k+ installs) does the layout flip but uses its own hosted API for translation. Paid TMS plugins like Lokalise handle translation but charge $120+/month and don't flip layouts. Lokali does both, free, with your key.

This is Lokali's specific wedge: designers shipping to MENA markets get both problems solved in one plugin, for free, with no vendor dependency on the translation side.

Objections Addressed

"I don't want to manage another API key"

You likely already have one if you use any AI tool. If not, OpenAI signup takes 3 minutes and GPT-4o mini costs fractions of a cent per design screen translated. The setup burden is genuinely low.

"What if my API key is compromised?"

Lokali stores your key in browser local storage — the same place your Figma session token lives. It's not stored on any server. A key leak would require an attacker to have access to your browser profile. Rotate your key in OpenAI's dashboard if you ever have concerns; Lokali picks up the new one immediately.

"The free tier on [hosted plugin] is enough for my use"

Until it isn't. Free tiers on hosted translation plugins are acquisition mechanisms. They compress or disappear when the vendor needs revenue. BYOK plugins have no free-tier economics — the plugin is genuinely free, the translation cost is your AI provider bill. That's a more stable arrangement for a core workflow tool.

Who BYOK Is Right For

BYOK is not ideal if you have no existing relationship with an AI provider and no interest in managing one, or if your company has a strict AI vendor approved list that doesn't include OpenAI/Anthropic/Gemini. For those cases, a TMS-integrated plugin or a negotiated enterprise agreement with a hosted vendor may be better.

Lokali — BYOK translation + RTL flip, free

The only free Figma plugin that combines AI translation (your key, your model) with one-click RTL layout mirroring. 289+ installs, zero pricing risk.

Install Lokali Free →

Related Guides