Before We Begin
If you haven’t had the chance to try it yet, we invite you to download the Gleef plugin.

‍

How do exports work in Gleef?

Exporting in Gleef is simple, flexible, and compatible with your tools. Once your keys and translations are generated or edited, you can export files directly from the interface.

Choose your format – JSON, CSV, XML (with YAML coming soon) – and Gleef will generate a structured file, ready to integrate into your localization platform or codebase. This saves you from manual copy-pasting, structural errors, or misnamed files.

Can the plugin be used just for managing keys, without translations? What about only translations and no keys?

Absolutely. The plugin is modular. You can use it solely for generating and managing localization keys, without triggering translations – ideal if you’re working with external translators or a Translation Management System (TMS).

Conversely, if you already have your keys and want to import translations to visualize them in Figma, that’s also possible. Gleef doesn’t enforce a rigid workflow – it adapts to where you are in your process.

How does Gleef integrate with Figma?

Gleef is a plugin directly usable within Figma. Once installed, you can:

• Import localization files
• Select screens or frames
• Generate keys
• Link existing text

You can visualize keys in your designs, modify them, view translations (or missing ones), and export. No need to switch tools – localization becomes as visible as design, right in your workspace.

How do you handle complex languages or special layouts?

Gleef lets you preview translations directly in Figma. This helps you anticipate layout issues related to text length (e.g., in German) or reading direction (e.g., RTL languages like Arabic or Hebrew).

What you see in Figma is exactly what your users will see. Supporting complex cases is a priority, and enhanced RTL previews are already in development.

How do you avoid duplicates or incorrectly named keys?

When you import a file, Gleef analyzes your existing keys and suggests automatic key generation aligned with your project’s naming conventions.

You maintain full control to adjust or validate them, but Gleef helps you avoid classic issues:

• Overly long names
• Accidental duplicates
• Confusing suffix cascades

This keeps your keybase clean and consistent, which helps both developers and translators.

How do you ensure translations remain brand-accurate and contextual?

The main advantage of localizing within Figma is visual context. Translations aren’t isolated in a spreadsheet – they’re embedded directly in the design.

This improves accuracy and relevance. We’re also developing features like:

• Glossary integration
• Tone-of-voice settings
• Smart suggestions for consistency at scale

What concrete benefits do teams gain?

The biggest win? Time.

Gleef helps you cut in half (or more) the time spent managing keys, exporting files, coordinating with translators, and fixing structural errors.

But it’s not just about speed – it’s also about quality.

By localizing directly within Figma, translators can see the exact context of each string. This dramatically reduces misunderstandings and awkward phrasing. The result is higher-quality translations that feel native, not just correct.

You also gain visibility: every team member can see what’s translated, what’s not, and what’s blocked.

The result?

• Less stress before international releases
• Fewer copy-paste errors
• Higher-quality, more brand-consistent translations
• A better overall user experience for global audiences

What is the pricing model?

Currently, Gleef is in open beta and is available for free. We are working on defining a fair pricing model based on usage (number of projects, active users, translation volume). There will always be a free version for small teams or one-off projects. And, of course, we will communicate transparently as soon as the pricing structure is finalized.

What are the upcoming features?

We’re actively working on:

• YAML format support
• Brand glossary and tone assistant
• Even smoother Figma-to-code sync
• A collaborative interface for designers, developers, and translators

Conclusion

At Gleef, we’re building a better localization process – one that’s seamless, visual, and built for global product teams.

From solving common pain points to integrating directly into your workflow, Gleef supports your product’s growth in a global market.

We’ll keep listening to your feedback and innovating – because localization isn’t a burden, it’s an opportunity.

Ready to take your localization game to the next level? We’re here to help.