Why this partnership?

1. Gleef: Smart generation of localization keys

At Gleef, we create tools that simplify localization management starting from the early stages of product design. Too often, translation is handled late in the development cycle, using tools disconnected from design, code, and teams. However, a successful localization strategy begins long before development. That’s why we believe it’s essential to rely on an open and complementary ecosystem of specialized tools, each an expert in its domain.

Our Figma plugin, the Gleef Localization Key Generator, automates the analysis and creation of translation keys directly from design files. It ensures consistent naming conventions, avoids duplication, and provides a clear overview of what has been translated and what hasn't. For more details about our plugin, read our article: Automatically translate your localization keys.

2. Inlang: An open-source infrastructure for managing localized content

Inlang is an open-source, file-based infrastructure that simplifies and modernizes the management of localized content in software projects. It provides a complete, centralized solution for handling language files, while integrating seamlessly with modern development environments.

At the core of Inlang is its SDK, which allows developers to read, write, and validate translation files, ensuring structural consistency across multilingual content. Built-in linting tools automatically catch common issues such as missing keys, inconsistent interpolations, and formatting errors helping maintain the quality of language files and preventing production bugs.

The ecosystem is designed to be file-based, meaning all localization data remains under the user's control in a single file format. This approach enables smooth interoperability between various Inlang tools without requiring custom integrations.

Inlang’s modular, plugin-based architecture supports a wide range of file formats (JSON, YAML, i18next, etc.) and works effortlessly with frameworks like Next.js, SvelteKit, and Astro. Optimized for collaboration, it fits naturally into Git-based and CI/CD workflows, making it easy for developers and translators to work together. Additionally, it offers user-friendly tools tailored for non-technical contributors, while keeping translation efforts in sync with the source code.

3. Parrot: real-time translations in Figma, to which Gleef is making contextual

Within the Inlang ecosystem, Parrot plays a crucial role for design teams. This Figma plugin enables product and design teams to work on translations directly within their designs, without ever leaving the Figma environment. Parrot displays localized content in context, helping teams spot mistranslations or tone issues early on, and provides a clear interface to collaborate with translators during the design phase.

By integrating Parrot into their workflow, teams can take language-specific constraints into account early (text length, alignment, local punctuation) while maintaining a direct link with the translation files used in development via Inlang.

This is where Gleef steps in: our Figma plugin, the Gleef Localization Key Generator, automates the extraction of textual content from designs and generates structured, normalized translation keys, ready for implementation in code.

But Gleef offers more than simple key generation: its greatest value lies in providing contextualized translations directly within the design. By linking each string to its visual context, Gleef helps ensure translation accuracy, reduces misunderstandings, and improves collaboration between designers, developers, and translators.

The result? Fewer human errors, consistent naming, no duplicate keys, and improved traceability of localized content.

Gleef helps designers and developers save time by eliminating manual key creation, while laying the foundation for well-structured and maintainable localization. Combined with Parrot and Inlang, it becomes a crucial link in a seamless, automated localization chain.

Shared goal: creating a smooth localization loop

Our belief is simple: localization should not be siloed, nor pushed to the end of the product cycle. It should be integrated into the workflow from the design phase, with close collaboration between designers, developers, and translators.

By connecting Gleef and Parrot, we’re building a solution where:

• Keys are generated automatically
• Texts are translated and previewed in context
• Files are intelligently managed and synchronized

What we’re building

At Gleef, our ambition is clear: to improve the localization experience directly within Figma, building on what Parrot started and going even further. Parrot demonstrated that translation management within Figma is both possible and effective: contextual preview, multilingual switching, export to standard formats… The tool is still functional today but is no longer under active development. That’s where we step in: our goal is to pick up where it left off, building a more powerful, better integrated version, supported by a dedicated team.

This partnership is based on tangible integrations that we are developing step by step to streamline the workflow between design, translation, and development. These include: synchronizing keys generated by Gleef with the content translated in Parrot, to ensure continuity between creation, localization, and implementation; direct access to the Inlang file, enabling centralized management of translation files on the development side, with no data loss or rework; and enriched translation status views within Figma, including suggestions, errors, and missing content all in context, close to the design. We’re currently collaborating with several design and tech teams to test these flows in real-world projects. If you’d like to better understand our journey and vision from the beginning, we invite you to read our article: Revolutionizing Localization: From Vision to Product

What this changes in practice

• Less manual work
• Fewer errors due to duplicates or inconsistent naming
• Full visibility into the localization status of a screen
• An integrated workflow, without leaving Figma
• Massive time savings for product, tech, and localization teams

Conclusion

This partnership is only the beginning. Our ambition is to go further in building a continuous localization pipeline one that’s accessible to all teams, regardless of size.

We firmly believe the future of localization relies on tools that are simple, open, and seamlessly integrate into modern workflows.